I read
Still trying to figure out the boundaries of these tools' strengths without outsourcing important thinking, problem-solving, and the collective building-up of a mental model of the systems we're developing.
The shape of LLM tools as toolsโfit for a purpose, ergonomicโis becoming clearer, and human patterns of behavior with them that do more harm than good are also becoming easier to recognize.
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Sharing a great read today:
Some of the takes are on the extreme end, but like most IT decisions, you can dial the pain to exactly what you want.
^C
textlog runs on a 2.5โฌ/mo vps 1 core/2gb ram, using just one instance of Bun with its embedded SQLite. Works perfect and I run a few other apps as well on that machine.
Sunk cost fallacy is no longer applicable in the age of . Now you can do broad changes without second thought, u can always revert back, without incurring the cost of doing so, since itโs all done so quickly and effortlessly.
I think it will still apply, just perhaps to a lesser degree. Kind of related to I wrote recently (not to shamelessly plug my stuff ๐ซฃ)