Building new, coherent architecture that your team will be willing to follow for years or decades is non-trivial and not something you can learn by going to college and/or consuming a bunch of bullshit tutorials from the internet. Architecture cannot be forked or cloned. It must be applied uniquely to the problem at hand.
To continue the analogy - You simply have to have tried to make that pasta dish so many fucking times that you become god of pasta dishes. You need to have customers (and employees) complain at you for 2 decades about various aspects of your cooking for you to truly understand what works and what doesnt.
> Consistency in architecture is more important than genius in architecture in most cases
Absolutely agree. This is why suggestions like "just use 1 big database for everything" are automatically a leap in the right direction for all involved. Only when this starts to get yucky should you turn on the clever bits of your brain.
The specific code arrangement is not that important, as long as the team understands some common domain model (types, properties & relations). The most successful architecture is one that the entire team can understand and communicate about without a senior developer babysitting them.
If you make one of those people the "God of architecture" you're not only going to piss off the other one you will probably lose the benefit of their experience. If theyre not responsible for architecture they'll pay commensurately less attention to it. Thats a waste of a salary.
The only scenario I can think of where it to promote one above all others would really be worth it would be if you otherwise cant stop the team from bickering.
As for juniors - if anything I tend to feel like theyre too deferent even when encouraged to speak up and take ownership. The only exception is when they dont realize they are making an architectural decision.
If a developer, especially a senior developer throws a hissy fit, they’re a Diva and toxic, not a Senior Developer.
Don't even get me started on Conway's Law. I'm so tired of people proposing "fixes" to architecture that simply can't be supported by the existing organization. Your architecture is crap if your organization can't support it, period end.
Your architecture is also crap if it doesn't meet the expectations of the stakeholders. So architects have to manage those expectations as well. Then there's always the developer who wants to use the latest shiny and new technology so they can put it on their CV. Architects have to manage all that and then some.
Yet the agilists preach that architecture is going to simply "emerge." Ha! The only architecture I've ever seen emerge is of the same nature of what emerges from one's rear end!
At the end of the day you need one person responsible for the architecture and design of the system. You just need to make sure that person isn't a diva and seeks and listens to feedback and concerns from the development team. Good architects are worth their weight in gold.
In tech, there’s often many right answers and a leader’s job is to ensure the team lands on one of them, not necessarily the leader’s favorite one. You’ll end up with far more inconsistencies if you have high employee turnover. Team cohesion is often more important than getting all the technical details perfect.
You can keep your _feelings_ ... takes a few iterations to spot this toxic bullshit. Be explicit. Not everyone needs to get a participation star. The hired developers that were tricked into a false development process will eventually call out this bs and leave. Depending how gullible they are may take them longer.
I dont need to feel like I'm being heard. I need you to hear me if you're going to ask.
I think it's similar in development, the lead architect or vp or whatever, drives the vision of the overall architecture, architects shape those big things and drive the devs toward that direction
This. Architects have to have a really quite rare blend of skills: superbly diplomatic yet inclusive, and ideally in it for the long-haul.
It's pretty common nowadays that only the "tech lead" or the most senior engineers discuss architectural topics that affect the whole team, but the most junior engineers are left behind.
Large software systems are complex, and there is too much detail for any one person to dive deep into everything, so in my opinion, you discuss overall architecture with the team, but critically, you explain _why_ you are proposing a certain approach, because more junior people don't have this context. Then, you ask the other folks to help you go deep into investigations on whether your architecture is compatible with the details.
If as a TL, you are not teaching and nurturing your young 'uns, you're doing a bad job.
I am in a position where I am doing TL-level decisions, and try quite hard to demo, discuss, share the details and rationale. I write design proposals, documentation, do demo sessions, etc
But the information is just not flowing, and I notice how little the juniors participate in anything. And I don't exactly know what to put my finger on. It's probably some soft-skill I'm lacking, and that I do not know how to improve
But a part of me still feels that that perhaps the young 'uns are just... too fresh. Or that the approach is just too optimistic
In my experience, usually, lack of participation comes from a lack of self confidence in one's understanding of software development, and usually, finding something small and delegating ownership to a junior engineer, with some oversight, gets them to participate more. You have to let go of the notion of having something done perfectly and allow them to make their own mistakes, but don't let them make huge ones. This is the most common case. There are also people who don't care (can't do much here), or aren't very good technically.
Yep that's it... let's not have management or leadership take any responsibility. It's the subordinates fault of course.
To make this work, the architecture needs to be somewhat simple. Architecture astronautics fail the "everyone can keep it in their head" test.
I think they stole that idea (everybody has the architecture in their head) from Extreme Programming.
I don't agree with this. It appeals to our sense of egalitarianism, but in practice I haven't seen it work out well.
Ideally one or at most a few people, who are also developers, owns the architecture, so that it is consistent. They should be senior developers who still work on real features in the code base to avoid architecture astronautism.
Consistency in architecture is more important than genius in architecture in most cases. Let a thousand flowers bloom elsewhere in your life.