Glad you pointed this out… kinda hilarious someone looks at these musicians, their output, and their fans and thinks that “being from the west coast” is the primary factor here.
So true — this thing is designed to go on our streets; I expect an attitude of maximum compliance. This shit can literally kill you if something goes wrong?
The testing is solely about emissions, it's an electric powertrain dolly and they want it to be proven it doesn't increase emissions rather than decrease them. It has nothing to do with safety as far as on road safety is concerned.
The weird thing is they want to test it against all the different trucks it can be towed behind, which doesn't make any sense. If it works it works, doesn't matter which specific truck it's behind so long as the already verified specifications of the truck engine and electric dolly align.
They should verify the electric dolly does what it says it does, compare that to the configurations of trucks they already have on file. Do the math. Does that cost $100,000 per configuration?
I really disagree with this too, especially given the article's next line:
> ...You’ll be forever tweaking individual lines of code, asking for a .reduce instead of a .map.filter, bikeshedding function names, and so on. At the same time, you’ll miss the opportunity to guide the AI away from architectural dead ends.
I think a good review will often do both, and understand that code happens at the line level and also the structural level. It implies a philosophy of coding that I have seen be incredibly destructive firsthand — committing a bunch of shit that no one on a team understands and no one knows how to reuse.
This is distinctly not the api, but an implementation detail.
Personally, i can ask colleagues to change function names, rework hierarchy, etc. But leave this exact example be, as it does not have any material difference difference - regardless of my personal preference.
> The remaining developers seem to implement things primarily client side, to the extent I even wonder if they have lost their ability to safely roll out backend changes.
Thanks for putting this into words — I have also noticed this and felt that product decisions have been shaped by this force of institutional rot.
Seriously agree — try using something like Sonnet 3.7 and then switching to Gemini 2.5 Pro. The code that both output is fine enough — especially given that I mostly use LLMs as a fancy autocomplete. Generally a better prompt is going to get me closer to what I want than a more robust model. The speed hit with Gemini 2.5 Pro is just too substantial for me to use it as a daily driver.
I imagine the speed difference might not matter so much if you are performing seismic updates across a codebase though.
yeah speed and flow state are for sure linked. People love to say Cursor is a Claude wrapper but they miss the reality that Cursor is a fast apply wrapper.
Death spiral is unfortunately a very correct term for this. I really can't express how different the conditions of public transit in SF and Philly are. Riding the L in Philly is unbelievably sketchy at night (passes through K&A) and I would not ride it alone if I were a woman. This is one of the main intra-city commuter rail lines in Philly. At this point, there are so few viable options that I can't really recommend public transit in Philly to anyone. Compare that to SF, where I literally take public transit everywhere, every day.
