HN user

kledru

200 karma
Posts1
Comments78
View on HN

"the part of the profession that attracted them in the first place is being removed or fundamentally altered"

Personally, I experienced something different. Before AI, it was the managers who gradually took away the joy and tried to fundamentally alter the profession... AI brought much of the joy back. Until some upstream roles discovered AI and used it as leverage to send larger volumes of bullshit downstream. I got away, sadly some people could not.

"You don’t learn to recognize good code by reading about it in a textbook, or a PR. You learn by writing bad code, getting it torn apart, and building intuition through years of practice."

I'd like to point out though, that you also learn by AI producing bad outcomes you are responsible for, and building intuition how it might fail through practice... You also might experience more lessons than you would have if you would have coded manually.

Sorry, despite the public statements of some sort of solidarity with Anthropic by sama this looks like a plot to take over from losing position.

Sadly it would be very difficult for Anthropic to relocate to another country with their IP, models, and infrastructure.

(Guess I need to build everything I intended this year in a weekend.)

yeah, no problem, I made a lame joke in frustrating situation. I would very much like the petition to have en effect.

I agree that Brooks's Law applies here, but I think it bites at a different level than suggested.

An engineer coordinating AI agents can achieve coherent architecture. The bottleneck is less about human-AI coordination; it's that the inert organizational structures won't adapt.

The engineer now has to coordinate with AI agents and all the legacy coordinating roles that were designed for a different era. All these roles still demand their slice of attention, except now there are more coordination points, not fewer - AI agents themselves, new AI governance roles, AI policy committees, compliance officers, security assessments...

I was about to argue, and then I suddenly remembered some past situations where a project manager clearly considered the code I wrote to be his achievement and proudly accepted the company's thanks.

Can't rule out Leopold's Congo scenario, as the first comments do not look good:

* resource extraction focus

* dismissal of local leadership (Machado "does not have the following or respect" -- Nobel hurting?)

* no transition plan to self-governance (perhaps it is early)

* military occupation ("not afraid of boots on the ground", "military will protect oil operations")

Not only the region... A worry is the step will encourage other regimes that feel they have might to remove leaders they do not like and replace them with marionette-like figures. Also, here we have another permanent member of UN Security Council making decisions to intervene without consulting the UN or even their own constitutional bodies...

(My opinion of Maduro is that he was not a legitimate leader.)

the number of comments indicates that MANY OF US crave for some wise words about burnout... but the text we are presented with feels strangely empty of substance -- as if the author just wants to make some money with a book on a hot topic...

"change management problem". We can forget AI specifically for a second -- there are teams and organizations that can adapt to change and there are those that cannot. Some orgs have invested heavily in rigid structures and processes and it probably made a lot of sense that time, but these were never going to survive paradigm shifts.