The boss is clueless.
But the 5 architects, 10 project leads and 20 QAs that worked with me last 2-3 years, are not. They have a clue.
And when it comes to code, that problem isn't solved by having a boss that reviews commits or being in team. If I leave, someone else will have to dig through that lrage chunk of code I did during last years. Team or boss with a clue won't help here, the only thing I can do on that is to write code that is easy to undestand, instead of showing my::meta::<template>.ftw->is().this.doing skills.
project that would last 2-3 years
I will give you example - new project, runtime 2 years:
3 months, requirement engineering, i'm not involved on that.
3 months, prof-of-concept implementation. First try to code what they have engeered above.
3 months, testing and evaluation of the PoC. Refine requirements. i'm not involved on that.
3 months, project planning - system design specs and stuff is getting finalized. partly involved
<one year past>
3 months, i actually write code
3 months, pre-prodction testing, i'm not involved on that unless they find bugs
3 months, in-field testing, i'm not involved on that unless they find bugs
3 months, prepation for prodction, i'm not involved on that unless they find bugs (pls!! no
and finaly.... SOP: Start-of-Production. Now you can visit your Daimler or BMW or whatever dealer to buy my work.