HNHacker News
TopNewBestAskShowJobs

mateuszserafin

36 karma · joined May 12, 2020

[ my public key: https://keybase.io/wendigo; my proof: https://keybase.io/wendigo/sigs/-Joz5FGqPhDdN6qhBj959gLGWzrCwhWfRBQnRke3QWQ ]
submissionscomments
mateuszserafin··on Boeing CEO warns of possible industry bankruptcy
I'd like to see more innovation/players as an outcome of Boeing's and Airbus' problems :)
mateuszserafin··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
I think that it's both actually as architecture as a process produces some artefacts (diagrams, decisions, PoCs, guidelines, policies, structure, knowledge, roadmaps, etc)
mateuszserafin··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Or putting in other words - keeping technical debt in check (as it comes mostly to non functional requirements)
mateuszserafin··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Oh I forgot one thing. It's ok to make mistakes and change your decisions. Sunk cost fallacy is a bitch and you have to be aware of that (sometimes it's cheaper to fail than do everything to be right)
mateuszserafin··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Congratulations. I've been in exactly the same position many years ago so I can share with you some of my insights.

I've proceeded with my career keeping those on mind:

- listen to what people say, you can't and won't be an expert on everything

- when you listen to them - verify and deepen your knowledge on topic, it's good to be able to connect dots

- be a practitioner - there's nothing worse than an architect that doesn't know how to code/configure server etc ;)

- attend both developer teams' demos, plannings and product teams' meetings - context is king and as an architect you have to see things both broad and narrow connecting technology with business needs

- be realistic - most businesses don't need super-high-tech-microservices-based-kubernetes-mesh-powered architectures ;)

- remember that architecture is about structure, guidelines, policies and order that aligns with business needs (so this is the starting point - understanding what business tries to achieve). Technologies really don't matter - they are just a tool

- always assume that you don't know everything - challenge your own assumptions

- be authentic and polite - people don't like super-star-asshole-know-it-all-architects (been one, don't recommend that :))

Good luck!