this post was submitted on 10 Jul 2026
429 points (99.5% liked)
Technology
86217 readers
5049 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Interesting perspective. Software development works different where I come from, the dev part is still very much in control of the developers themselves. However the management lives in delusionville and the expectations are pretty much insane compared to the reality of the actual turnout. My comment above was more about educating the general public... AI results can look pretty compelling unless you decide to have a closer look, and a lot of non-dev people are falling for it. Either because they are dumb and gullible, lack analytic thinking or because they have no real contact with AI and are just exposed to the hype through the media.
it's one of those things that people need to ask about things they are an expert at so they can understand how valuable the results really are.
Adjacent comment: Using the electrician analogy, AI is like one of those really cool gadgets you see on Temu that don't actually do half of what they claim and will probably burn the building down. Another analogy is AI are like Roomba's: they kinda work, take forever to finish, clog up easily, and are guaranteed to miss a lot of stuff.
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.