I was a software consultant with “architect”* experience for the last 10 years of my career or whatever you want to call it. 50~80% of my job was basically saying the same thing their in house developers were saying. Maybe the other half was pushing tech stack upgrades (CVS -> SVN -> Git/Perforce ), (CGI to basically anything else), etc etc. My least favorite role was being a hatchet man, eg one of the Bobs from office space.
Professionally I used a shit ton of analogies and metaphors. Absolute most effective was comparing new feature development to an electrician adding a new light or receptacle. You may find you need to upgrade the service panel (database or other services), it can take time to pull new lines and doing so can interfere with existing equipment. Finally you can only pull so many new cables through an existing building before you need to do necessary cleanups and rearrangements (eg refactoring). Failing to do so may lead to brown outs (crashes) or the entire building catching on fire (eg Microsoft Dumpster Fire 11). Last bit is you can help explain the complexity of a feature as top floor, mid level, or basement (eg “soonish”).
* Architect title/role was something I would try my best to bury. The companies that needed an Architect only figure that out when they discover MS Access DB isn’t going to work /s but only a little bit. Also what the fuck is an “Architect”, its not like any of our titles have any national standards.
This video is kind of triggering my deep seated hatred of MBA’s but if you ever want to explain to the normies what your job is like, “The Expert” https://youtu.be/BKorP55Aqvg is perfect.
Yeah, I can relate. I’ve been doing consultant work and I always tried to avoid being pushed into the “architect” role. My background for over 25 years was software development and we had a lot of success with agile methods (doing it right is hard but viable and it produces quality software) My experience is that a good dev team does not need an “architect” to tells them what’s best.
But all of this is now gone anyway, or at least taking an extended break. At the moment no one is investing in development teams, and the prospect of being able to fire all the developers because AI can do their job now is making CEOs giddy everywhere. Not going to happen (and this should be obvious for anyone who can judge the quality of code or the effectiveness of processes in terms of reliability, quality, cost, performance etc.) but that doesn’t stop them from trying.
I framed the “AI” craze as parallel to shelf checkout kiosks. They were sold as the future and a way of getting rid of those pesky human workers. Reality is they’re an open wound on the company. Unfortunately it will cost more money to get rid of them so they’re still there.
That’s the difference with AI currently. Cancel your subscription, toggle it to off in your IDE, and its gone. I believe this is why they’re trying to push “AI” everywhere, hoping it will stick somewhere.
Otherwise I liked a well manged agile development process. Heck of a lot less stressful than water fall.
I was a software consultant with “architect”* experience for the last 10 years of my career or whatever you want to call it. 50~80% of my job was basically saying the same thing their in house developers were saying. Maybe the other half was pushing tech stack upgrades (CVS -> SVN -> Git/Perforce ), (CGI to basically anything else), etc etc. My least favorite role was being a hatchet man, eg one of the Bobs from office space.
Professionally I used a shit ton of analogies and metaphors. Absolute most effective was comparing new feature development to an electrician adding a new light or receptacle. You may find you need to upgrade the service panel (database or other services), it can take time to pull new lines and doing so can interfere with existing equipment. Finally you can only pull so many new cables through an existing building before you need to do necessary cleanups and rearrangements (eg refactoring). Failing to do so may lead to brown outs (crashes) or the entire building catching on fire (eg Microsoft Dumpster Fire 11). Last bit is you can help explain the complexity of a feature as top floor, mid level, or basement (eg “soonish”).
* Architect title/role was something I would try my best to bury. The companies that needed an Architect only figure that out when they discover MS Access DB isn’t going to work /s but only a little bit. Also what the fuck is an “Architect”, its not like any of our titles have any national standards.
This video is kind of triggering my deep seated hatred of MBA’s but if you ever want to explain to the normies what your job is like, “The Expert” https://youtu.be/BKorP55Aqvg is perfect.
Yeah, I can relate. I’ve been doing consultant work and I always tried to avoid being pushed into the “architect” role. My background for over 25 years was software development and we had a lot of success with agile methods (doing it right is hard but viable and it produces quality software) My experience is that a good dev team does not need an “architect” to tells them what’s best. But all of this is now gone anyway, or at least taking an extended break. At the moment no one is investing in development teams, and the prospect of being able to fire all the developers because AI can do their job now is making CEOs giddy everywhere. Not going to happen (and this should be obvious for anyone who can judge the quality of code or the effectiveness of processes in terms of reliability, quality, cost, performance etc.) but that doesn’t stop them from trying.
I framed the “AI” craze as parallel to shelf checkout kiosks. They were sold as the future and a way of getting rid of those pesky human workers. Reality is they’re an open wound on the company. Unfortunately it will cost more money to get rid of them so they’re still there.
That’s the difference with AI currently. Cancel your subscription, toggle it to off in your IDE, and its gone. I believe this is why they’re trying to push “AI” everywhere, hoping it will stick somewhere.
Otherwise I liked a well manged agile development process. Heck of a lot less stressful than water fall.