Live data from Hacker News

Behaviours to avoid in a software architecture role

danielwatts.info

171–174 of 174 posts

Re: Behaviours to avoid in a software architecture role

#171

Earlier quoted context omitted.

Principal at Amazon is the first level above senior software engineer, so closer to staff than principal at Google/Facebook. It isn't a particularly uncommon level to reach at Facebook or Google.

Principals at Amazon are 1.8% of the SDE population, so no, the comparison to "Staff" engineer is unfounded.

Amazon is just more stingy with promotions.

Re: Behaviours to avoid in a software architecture role

#172

Earlier quoted context omitted.

This isn't specifically the job of the architect. Any idiot can explain how the tool they built works. So the software engineer or the product manager can do this as well. Explaining how something works is not a magical skill reserved for software architects. What is a skill reserved for architects? If you find yourself spending 100% of your time creating a powerpoint to explain things in a way that makes you sound s…

The architect is the only idiot, who knows the tool as a whole and, more importantly, its role in the bigger world. Other idiots know only how bits are fiddled in a small corner of the tool on which they worked during their probation, they don't know the big picture, at all. In any case documentation in big companies today is outsourced to people with zero programming experience, and they obviously can generate only…

So literally you’re saying the architect is the only person who can write good documentation.

Also the architect is the only person who did not write a line of code yet understands the tool better than engineers who work, code and solve problems across the entire stack.

That’s not only arrogant. It’s delusional.

Re: Behaviours to avoid in a software architecture role

#173

Earlier quoted context omitted.

The architect is the only idiot, who knows the tool as a whole and, more importantly, its role in the bigger world. Other idiots know only how bits are fiddled in a small corner of the tool on which they worked during their probation, they don't know the big picture, at all. In any case documentation in big companies today is outsourced to people with zero programming experience, and they obviously can generate only…

So literally you’re saying the architect is the only person who can write good documentation. Also the architect is the only person who did not write a line of code yet understands the tool better than engineers who work, code and solve problems across the entire stack. That’s not only arrogant. It’s delusional.

He doesn't know how local variables are named, but what's needed for documentation is purpose and nature of the tool, and that's what engineers often don't know, because it doesn't help with bit fiddling. And a coding architect is an architect too.

Re: Behaviours to avoid in a software architecture role

#174

Earlier quoted context omitted.

Principals at Amazon are 1.8% of the SDE population, so no, the comparison to "Staff" engineer is unfounded.

Amazon is just more stingy with promotions.

Yes, and so their "staff" engineers stay Sr. Engineers. Isn't that the same point I made?
Post reply on HN