Same, even opus favor short term solution and scripts with a billion flags that constabtly require rescanning to understand how to launch it is a constant struggle to get it to build sane default and reusable scripts that run with minimal parameters
Yeah, and what's up with adding dry run to everything? I saw some code that doesn't write anything but still the AI added a dry run which had a completely different codebase
Bigger, because no one expects beauty from Fiat. That said, the Multipla was a bold and brilliant car. This one is only bold in the sense that “I can’t believe Ferrari allowed that to happen”. It’s kind of the Balenciaga of cars: will rich people buy just about anything with the right logo on?
Also nobody talks enough about the fact that workforce is effectively cut out from the means of productions. Even with the capital at hand blackwell cabinets are all sold out, contracted to the big providers.
There are paralles to the industrial revolution, but it seems the working class is cut out from being able to deny labor in exchange for better conditions.
System security is not a human value. Access key rotation effective immediately is a compliance requirement, and completely orthogonal to human decency, which is delivered trough garden leave or severance, not extended system access
Yes, you're right, but in my experience the boundary between the data plane and the control plane is not always clear, and especially unclear on these foundational and basic services.
There were enough "surprisingly control-plane" IAM operations in the AWS services that I dealt with, so we had to exercise extreme caution during outages.
Even if I were the stupidest and least curious engineer around (and I was far from it), that's basically irrelevant to what you're scolding me for here…
As part of a team with both software development and operational responsibilities, like most teams at AWS, I had to deal not only with the consequences of my own imperfect knowledge, but also with the imperfect knowledge of my coworkers past and present.
You don't wait. You run multiple independent incremental feature in parallel, while also running a code review, which will create the next set of tasks while you or the llm think up the feature to add after.
It's not "flow state" but working on three features in parallel requires focus that's equally as fragile, at least if you want to follow the output of the LLMs and steer it if it makes mistakes.
It's surprisingly hard to do the compiler or cpu may see a write without a read and optimize it away. Windows has a SecureZeroMemory and a few other barrier primitives but not all languages reach to it
reply