the hardest thing with deadlines and dev is that architecture is hard to measure without years of experience at actually implementing feature sets very often marketing is in charge of feature sets and architects rapidly turn grey and drop dead of heart attacks by deadline that is, if the architects are actually qualified, and IMO, software architects can only be called qualified after 10 years working as an engineer there is no magic trick learning how to spec out a project without getting into overruns and quality problems due to deadlines and unrealistic expectations of management
Well, that's why architect is a real job. 🤷♀️
yeah but most of them are like 3 years CS and 2 years writing waffly documents and get hired to direct work they don't understand
for real, i've seen this at a shitcoin job, the "architect" was really a marketing guy in disguise
i'm getting close to being able to do it now, but i've been working mostly full time since 2018 nothing like failing to build the features you thought you could build to teach you prudence in architecture... where building architects must learn to work with material and space, software it's about time and brains
We've got that at my day job right now. The deadline is artificially imposed by the big trade show, the research and product teams take their time in figuring out what they want to debut at the trade show, they ask the devs to do it, the devs say "there's not enough time before the trade show," and chaos ensues. 😅