Re:Behaviours to avoid in a software architecture role
by pc86 on Tuesday February 02, 2021 @09:44PM
(#26009985)
Not to just reframe AnimalMuppet's point, but which of these two things is more likely?
1) Your couple hours of research has uncovered something blatantly obvious that was somehow missed by the other party.
2) Your couple hours of research hasn't shown you some edge case or something that is common knowledge once you've been in the field for 2+ decades.
I'm not saying #1 never happens, only that #2 is much more likely. It's a horses vs. zebras argument.
Re:Behaviours to avoid in a software architecture role
by imafish on Wednesday February 03, 2021 @02:52AM
(#26011539)
3) The other party has a lot of stuff on his/her plate and does not get the luxury to spend hours of research/thought on architectural details.
Re:Behaviours to avoid in a software architecture role
by bluefirebrand on Wednesday February 03, 2021 @09:51AM
(#26014039)
And don't forget "Hasn't actually worked hands on with anything you're doing for a decade"
Re:Behaviours to avoid in a software architecture role
by AnimalMuppet on Tuesday February 02, 2021 @05:30PM
(#26007874)
In pc86's scenario, though, it's much more likely that you're the one with the ego, thinking that reading a few blog posts makes you more informed than a 20-year industry vet.
Either way you lose.