I'd like to read (in my opinion) high quality and not much biased critique, like this one.
And especially from someone who is an expert (unlike me) for this programming stuff.
So lets explore some Vervaekeism (had to use Kagi search as it's a novelty to me) about how getting dirty with code can reveal us that the syntax is not mere ceremony; boilerplate is meaningful.
*the part about the domestication of us humans (with the example of wood-burning stoves) really reminds me of how it took me almost 3 yrs to learn how to operate the downdraft gasification boiler that replaced the old 'just burn the pile of wood somehow'.
Not to mention that one tiny broken part in the mechanism responsible for dealing with the pressure difference between building heating and long-distance hot water pipeline for the heat distribution.
Spend 4 days with no heat and hot water in lowest temperatures this winter.
Undisclosed and thus not well understood complexity that can't be explained correctly by the AI can be hard to fix.
(Despite the manuals, years of the forum posts and entire FAQ knowledge being available basically online for AI to digest.)
And that is easier with hardware as it offers quite direct feedback, with the hot stuff, if done wrong.
View Article →