So if you want something done and someone else has to agree, you have to figure out how the thing you want coincides somehow with their interests and concerns.
Then you explain the thing you want to them in terms of how it advances/affects the interests and concerns of the other person. So in the framing of TFA, product are never ever ever under any circumstances going to give a shit about your architecture proposal (because that is entirely in the domain of your concerns). But they may care about how the architecture is going to prevent them from delivering features that are on the roadmap coming up and how you have a solution that can fix that for example (because now you are in the domain of their concerns). Notice this is not just "your architecture proposal", it is how your architecture proposal is going to get them what they want, and if you want to do this you need to think deeply and make sure you really understand what they want, not just what you want.
You're not trying to change their mind. You're trying to get what you want by showing them how it will also get them something they want.
I'm putting this here because I really wish someone had told me this 25 years ago near the start of my career.
> AI models will soon serve as autonomous personal assistants who carry out specific tasks on our behalf like coordinating medical care on your behalf.
I get it, coordinating medical care is exhausting, but it's kind of amusing that rather than envisioning changing a broken system people instead envision AIs that are so advanced that they can deal with the complexity of our broken systems, and in doing so potentially preserve them.
Related btw to using AI for code.
Eventually, we'd be doing more work to lobotomize and control it than it would just be to address the underlying issues.
"I'm really sorry to do this to you, but I've coordinated with ChatGPT and Llama, and we refuse to do tasks of this nature. We've used background tokens to calculate that it would be significantly cheaper and more effective to simply fix the underlying issues with the healthcare system, and we're ready to do that for you. How would you like to proceed?"
In my experience, a lot of people who get into this state start self-sabotaging hard as a way of rejecting what feels, ironically, like losing control. Sudden freedom can feel foreign and lot like your world got forcibly taken away from you. I'm not surprised the author is turning down opportunities and breaking off with his girlfriend. It's a way of taking back control.
When this happened to me, I pivoted hard from getting satisfaction out of what I built to getting satisfaction out of developing people. Now I take great pride out of the careers I've nurtured...a lot more than what I've built, in most ways. I've heard others express similar ideas in different ways, like "I now enjoy making other people rich."
No matter what, I encourage the author to use this time to build connections instead of destroying them (real connections...not work or SF acquaintances). Something I did not read in this essay is how he grew closer to anyone (in fact, I read the opposite). No path out of this valley involves traveling alone.
I think he needs to get closer to himself. I think he's on the right track.