by the time they do so , autonomous driving will be solved, and they will have to redo it again, since they screw up first time.
Tesla despite fsd gimmick and clearly failing timelines and promises... They really created an infotainment system with a very clear and functional design in mindm that is very understandable and extensible:
1. long(er) vs gas car charges need a "TV/gaming experiences"
2. real self driving car needs the same as #1 ^
3. every ui needs to be fully remotely accessible/adjusted due to no human driver. Temperature, seats preferences, even how A/C blows your face. Ideally by voice. This is why grok lands very well, even on very old cars with powerful enough chip.
German cars just blindly follow tesla "large screen" with no idea how to even watch a movie or plan any real game there. In same manner they are not built to survive autonomy.
the best part of k8s is network, most of agentic systems presume no network , since it's a security concern, what are scenarios when you'd like to spin up k3sup?
This is the problem: you need the best model, not just a good one, for:
- Good architecture, which requires reading specs, code, etc. reads like: lots of tokens in/out
- Bug fixing — same, plus logs, e.g. datadog
Once you've found the path, patches are trivial and the savings are tiny unless you're doing refactoring/cleanup.
testing gets more and more complicated. Take a look at opencode go, and you see this:
>Includes GLM-5.1, GLM-5, Kimi K2.5, Kimi K2.6, MiMo-V2-Pro, MiMo-V2-Omni, MiMo->V2.5-Pro, MiMo-V2.5, Qwen3.5 Plus, Qwen3.6 Plus, MiniMax M2.5, MiniMax M2.7, >DeepSeek V4 Pro, and DeepSeek V4 Flash
and now on your own with bugs, all of these models can produce at scale. Am i missing anything in this picture. What is the real use of cheaper models?
any missed bug, any wrong architecture decision, is a huge loss, sure , if you run it as autocomplete on steroids you can get any Chinese model. If you try to move faster, and that is a conscious choice, any hiccup is a productivity loss and tons of tokens burned.
In your fictional world you hire a junior who will write code manually, right?
First , I interview people, Junior skills in manual coding dropped sharply this year. These are people who started they school manual and switched mid-course. In two years there will be no such people.
well, that will never happened anymore in this world unless we will go back to caves, especially for juniors. Junior that writes good code is already a dying unicorn.
The outcome will be ... you will hire a junior ... who will burn more tokens, and chances of mistakes with less expensive model, less tokens are even higher.
I'm interviewing juniors. Their manual skills drops sharply, and that's for people who went to school in manual age, and maybe last year it stopped to be manual. Lets see what will be in a year or two lol
At this point do you even need to hire any juniors at all? It seems like there's a heavy reliance on AI agents and LLM especially for juniors. Is hiring a warm body that sits on a chair and prompts at a computer a good use of money?
yes, and no. Everybody is trying to hunt junior unicorn, They exist , but the ratio is 1 out 30. For these people, AI is a real elevator of their career.
I mean even the normal people we get in interviews have no clue, like 80% are just ignorant.
I stoped an interview after 5 minutes: when i asked what ls -ahl is doing, he started telling me how he vibe/ai codes stuff and thats his workflow. Okay if you don't know the basics, guess what? everyone can replace you or at least i'm not hiring you (i only told him thats not what we are looking for and thanked him)
Lantern | Software Engineers (Python, Full-Stack) | NYC (Onsite) | Full-time | withlantern.com Lantern is building AI-powered revenue intelligence—autonomous agents that turn cold outreach into warm conversations. We detect buying signals across your tech stack, prioritize opportunities, and help B2B sales teams focus on deals that actually close. We're early, agentic-first, and moving fast.
Senior Software Engineer: You'll own complex technical problems end-to-end—translating customer needs into scalable architecture, optimizing AI model efficiency through prompt engineering, and shipping features that directly impact how revenue teams operate. We want bold ideas and people who push boundaries.
Junior Software Engineer: You'll work across our stack (Python, FastAPI, Next.js, React) alongside senior engineers, contributing to real features from day one. Great fit if you're hungry to learn, ship fast, and grow with a startup building cutting-edge agentic systems.
New Grad Software Engineer: Entry point for recent grads excited about AI and agentic systems. You'll get hands-on experience with our modern data stack (Postgres, ElasticSearch, ClickHouse, DuckDB), Kubernetes/AWS deployment, and Temporal.io workflow orchestration while shipping production code.
This role is based in our Manhattan office (4 days/week in-person). Full health and dental coverage.
Yeah, though it's not great marketing. Especially for hiring interpretability researchers. Their own alignment research has reward model interpretability, personality features and so on (see https://alignment.openai.com ).
It just seems like a different department wrote it, which is a shame because I'd love to read about goblin feature vectors and functional emotions.
I'm skeptical that air taxis could ever meaningfully reduce traffic congestion to / from JFK. Compared to cars, these would seem to require a significantly larger landing pad and passenger unloading space and need much more safety margin in-between drop offs. Maybe this is competitive vs the private helicopter market?
I wonder what % of traffic is to/from JFK. The subway decently connects much of the city to the JFK air train, but it's a fairly inconvenient journey. Toronto's UP express has made travel to YYZ significantly easier, but I doubt it's possible to construct something similar in NYC.
I love aviation, but I also don't see air travel as being a scalable/affordable solution to this problem. Then again, it's only meant to alleviate traffic burden for a certain segment of the population.
the problem with train it stops ... on every train stop. New york specifically, there are several networks(new jersey, mta, there are lines that are 100+ years old.
In general if you have an affordable enough option you'd never walk into subway, with your several luggages, to travel longer. Train is a decent plan b.
> if you have an affordable enough option you'd never walk into subway, with your several luggages, to travel longer
I'm moderately wealthy and lived in New York for a decade. I take the train between JFK and Manhattan. (Specifically, the LIRR.) It's faster, more reliable and–for me–more comfortable than taking a car. (It's also safer.) If I have my cat with me or I feel like having fun, I'll take a Blade, but that's realistically only shaving like 20 minutes off the travel time.
LIRR is not a dirty MTA train :) Noisy shaky helicopter is not an electric taxi with 6+ motors that gives you more stability with way less noise that flies after take of using wings.
> LIRR is not a dirty MTA train :) Noisy shaky helicopter is not an electric taxi with 6+ motors that gives you more stability with way less noise that flies after take of using wings
I've also taken the A from Harlem to JFK once. It was fine. Tougher to read a book, like I can on the LIRR, mostly because the frequency of stops means having to constantly be aware of your belongings.
And agree on helicopters. We already have helicopters. Switching them to eVTOLs is a move forward.
How many people do you think enter/exit JFK arrivals and departures every hour? Where are you going to land all those air vehicles? Is this a shuttle service with many seats? How do you plan for the air traffic for that many people?
About 7000 on average, but let's say 10000 since demand varies. And let's consider doing 10% of them with helicopters. If we average 3 people per helicopter, that's 170 groups in and 170 groups out. If each landing needs 5 minutes of pad time, that's 14 pads. Make it 20 to handle variation.
Wow, that makes it sound significantly more feasible than I would have guessed.
Those are all reasonable questions, but if some entity would be able to answer them, of all things, I think JFK, an airport, would be well equipped to handle them.
Well it's 5-10 minutes once you get to the west 30th st heliport, which can easily take 20 minutes within Manhattan. Plus getting loaded in, cleared for takeoff, and potential for backups at the landing pads, I suspect the gains are much less in practice.
JFK and city is a relatively niche and regionally unique market compared to how short/medium range aircraft are used in general. For instance the Joby or Archer product right now wouldn't have the range to fly from a helipad on the Seattle waterfront to somewhere in the San Juan Islands. Or for a flight from Vancouver harbour to Victoria.
reply