I wonder how different the outcome would be if the idiom used was not help but "instructions", as in, what portion of users did not want to admit they needed assistance?
I'm not refuting the fact that people seldom read, but this seems like an interesting additional vector to explore.
Right, and often the tested depth isnt maximum. So you slowly acclimate to worse and worse code practices if the effort needed to undo it is the same as doing.
sure, but undo isn't the only path to a newer better version of the code
it's easy to see how the product (claude code) could be abstracted to spec form and then a future version built from that without inheriting previous iterations tech debt
If Russia's economy is kept afloat after 4 years of full-scale war... Why would one year of Trump 2.0 do us in? Don't get me wrong, a whole lot of problematic actions have been taken in that time-frame but that pales in comparison to 1.25 million casualties and about the same number having left the country (and our population is almost triple theirs) on top of infrastructure destruction.
Entirely different cases. Russia never relied on the strong rouble for its economy to function. Or having unfettered access to most of the world's markets. So it had some know-how on weathering the storm.
But OTOH, if Trump is erratic enough to trigger a world-wide de-dollarization trend, and close down markets that were traditionaly open (e.g. Europe), then US would be facing an unprecedented storm that would be much harder to navigate.
Hi, I'm an embedded systems engineer/architect bridging the full compute spectrum of ultra-low power IoT, edge systems, and HPC.
My latest projects have been in full-stack edge ML R&D, memory controller firmware dev for POWER servers, and chip bringup/testing for Z mainframes.
I'm passionate about modular synthesis and tinkering with all sorts of analog circuits and DSP. Currently upskilling in analog PCB design and refining my abilities in FPGA development. Also WIP on a 3D-printed robot arm to practice control systems and actuation.
I was never in webdev, per se. I switched from "fullstack" (which included backend+frontend as well as mobile/firmware/ML) to hardware eng at IBM, and then widened back out again to R&D Engineering at a startup to work on a patent. I had always wanted to be closer to hardware/embedded and anything that involves sensor-laden and/or RF-enabled systems so it was a natural progression for me.
I was a proponent initially of CLI when Claude integration with VSCode required a WSL instance, but now that it is integrated directly into VSCode I feel one grouping of tooling hiccups is now ruled out in my workflow. The only (major) nitpick I have is that it wont let you finish typing and cuts you off when asking whether/how to proceed.
I'm not refuting the fact that people seldom read, but this seems like an interesting additional vector to explore.
reply