"If you treat a prompt as an algorithm, this tracks. Vague prompts expand the solution space and force corrective passes. Precise prompts narrow it and converge faster. Over time, the difference shows up in total token consumption.My suspicion is that companies will eventually care less about raw vibe-coding speed and more about something like speed divided by tokens. Not explicitly at first, but implicitly through cost limits, internal tooling, and expectations."
Readit Newsaworks commented on The Big-O Complexity of Vibe Coders shiveesh.com/thoughts-and... · Posted by u/shiveeshfotedar
Deleted Comment
Good discussion of tactical vs. strategic firefighting
He also designed a Facebook’s office in Menlo Park. The roof was literally a park, seemingly blending with the bay and you could go for a nice nature stroll mid-day by just going up a flight of stairs.
https://arquitecturaviva.com/works/facebook-campus-in-menlo-...
Did he design the yellow pedestrian/biker bridge connecting Facebook to the the Bayfront? I recently drove underneath it and it's quite interesting.
aworks commented on Google, Nvidia, and OpenAI stratechery.com/2025/goog... · Posted by u/tambourine_man
"the naive approach to moats focuses on the cost of switching; in fact, however, the more important correlation to the strength of a moat is the number of unique purchasers/users."
aworks commented on The axis: the left-right spectrum has a non-ideology problem gelliottmorris.com/p/not-... · Posted by u/aworks
Technical point: "While LLMs/AI fall short of many promises made by enthusiasts over the last couple years, we are relying on them for the one thing they are good at: summarizing and analyzing text...The full prompt used in this analysis is given in the footnotes.1"
Likely air New Zealand flight 901 which crashed into mount Erebus in Antarctica (not in New Zealand proper) in 1979. https://en.wikipedia.org/wiki/Mount_Erebus_disaster
Yes, thanks for the identification.
aworks commented on How good engineers write bad code at big companies seangoedecke.com/bad-code... · Posted by u/gfysfm
I can find an experienced doctor, plumber, musician or mechanical engineer that was doing it 50 years ago.
I’m not going to find someone that was doing software 50 years ago. And if I do, their experience is completely unrelatable.
I worked on compilers and tools starting in 1981. Proprietary compiler technology has disappeared over the decades and the development tools/language/process/compute have changed considerably. But the skills and role of a compiler developer seem similar, although maybe it just means this sub-field of software has matured.
As software developers, we should perhaps refrain from criticizing aeronautical engineers' QA standards.
Early in my career, I worked for a subcontractor to Boeing Commericial Airplanes. I've worked in Silicon Valley ever since. As a swag, the % of budget spent on verification/validation for flight-critical software was 5x versus my later jobs.
Early in the job, we watched a video about some plane that navigated into a mountain in New Zealand. That got my attention.
On the other hand, the software development practices were slow to modernize in many cases e.g. FORTRAN 66 (but eventually with a preprocessor).