This aligns closely with what I have in mind. I love your term "bugbear" - both are definitely in my bugbear list also.
The "architect-y" tower reminds me of leaders who insist on having things done in specific ways without knowing what exactly the impact of what they're asking for.
The 2nd one is crucial since majority of software is written for business purposes and therefore, really needs consideration and to not do so would actually create technical debt and cost the business $$$ in the long term.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What a great answer!
This aligns closely with what I have in mind. I love your term "bugbear" - both are definitely in my bugbear list also.
The "architect-y" tower reminds me of leaders who insist on having things done in specific ways without knowing what exactly the impact of what they're asking for.
The 2nd one is crucial since majority of software is written for business purposes and therefore, really needs consideration and to not do so would actually create technical debt and cost the business $$$ in the long term.