I am a Software Architect by title, but most of my work is finding the right people and pulling the right strings to get the job done.

I force myself into coding at least 25% of time because I do not want to become one of those non-coding architects that everyone including themselves despises.

You really can't just draw diagrams, write Software Architecture Documents and assume that you what you do makes sense.

Our minds have a tendency to wander off and need constant reality checks to operate properly.

All comparisons to construction business are flawed, because Architects in the construction business have to navigate an entangled reality of regulatory work, client desires, supply chain considerations and all other real-world constraints.

In contrast, Software Architects mostly work in a digital world where almost everything is possible, their perception of the reality will drift unless they fight the sensory deprivation with hands-on coding.

You seem to contradict yourself. You start off by noting all the non-technical constraints on a software architect and then say it's nothing like a construction architect by noting all their non-technical constraints.

They seem to be very similar - balancing client desires vs. real-world constraints, because no, it is not the case that everything is possible with regards to software architecture. Software architects have to contend with processing constraints, memory constraints, networking constraints, process management and coordination constraints, and organizational constraints. Depending on the industry vertical you're in you may even have to contend with regulatory constraints.

Sure, there are real-world constraints in construction and in software, but the perception of constrants in software is different.

One can totally skip reality checks in software, because there is more variety, more options, crazy amounts of money and general immaturity.

She’s the CTO and cofounder of a dev ops product company so I don’t think she’s who you’re imagining she is.

I don't think that excuses the poor attitude. Honestly, that job sounds like burnout city.

I'm aware of who she is.

Then you should be quite aware she doesn’t believe half the random shit she spouts on twitter, including this. It’s greatly exaggerated for clout chasing.

Most of her twitter seems sincere, where does she indicate most of it isn't?

Or is this one of those convenient excuses people make, like "it's just a joke bro!"

Nuance doesn’t work on twitter. It’s part of the game. She’s on there to get clicks to spread her personal and company brand.

“I take you more seriously on matters of architecture if you’re committing code on a regular basis and on the pager duty rotation. Some architects are really good and many are bad or detrimental.”

Is not a take that gets quote tweeted or posted on hacker news.

This more or less describes a lot of how I view software industry Twitter.

Tweet threads on topics like this are rarely deep and thoughtfully considered, and when they are, an article or blog post would always be a better format.

That's not what i expect when i see someone on twitter linking the CTO role in their bio.

You have your assumptions inverted my friend

i don't think that's true, given that these are the same things she says on her blog and on the honeycomb blog

The consistency indicates preparedness, not candor.

Yeah, when you start to describe your daily work with words like "burden", you're usually not in a good mental state.

> And the beeper that goes off when it stops working most likely belongs to a different person than wrote the code

There's your problem.

> When I see this kind of attitude I know that this person is burned out and needs to find something new to do.

When I see this kind of absolutist statement - where someone presumes to have a complete picture of someone & have absolute certainty about what it means - from a brief snapshot like this - I know better than to trust the claims or take them seriously.

> So, no offense, but get the fuck over yourself or find a new job.

Counterproposal: ease the fuck up. Step back. Couch your terms in at some least modicum of hesitancy & humility, that you maybe don't know 100% everything & might not be 100% accurate & correct. You're having their own reaction here: it has only somewhat to do with the post.

I can't tell if you're talking about the "architects" here or the person saying that "architect" is a bullshit job.