even on that I'd separate the short-term craze from the long-term implications.
I'm worried only up to a certain point about cynical and uninformed CEOs who only want to cut their costs. Yes, some roles are likely to go for good, or be deeply changed by AI, but I don't see engineering jobs go anywhere. You can't put 100% AI-generated code in production and expect it to run itself and maintain by itself. Those CEOs will just come back with their tails behind their legs to hire back from the market, at an inflated price, the roles that they laid off (many are already doing that).
But the engineers who learn how to master these tools to boost their productivity without letting them erode their skills are those who will win on the long run.
Those who refuse to embrace them altogether will be akin to an accountant who 40 years ago wanted to do all of his calculations by hand and refused to use a pocket calculator. Or the engineer who 15 years ago refused to look up answers to common coding problems on StackOverflow and only relied on man pages. No matter how brilliant these figures were in their jobs, they couldn't compete with a machine once the technology was mature enough to boost up the expected productivity requirements for someone in their role. And eventually people who mastered the new tools became more productive than them.
On the other hand, those that start depending too much on these technologies are those that will struggle the most if you put them in an environment where these tools aren't readily available. They're akin to the Eclipse fan boy of 20 years ago that learned how to code in Java only in Eclipse and couldn't use any other IDE/editor. Or the StackOverflow serial copy-paste guy who doesn't bother to understand the code, and who is likely to cry when something breaks in production.
Those who win on the long run are usually those who embrace the new tools pragmatically, while still providing added value compared to those tools - without putting themselves in the conditions where those tools can easily replace their job entirely.
Fabio Manganiello /
npub1s9…jdnmu
2025-05-01 10:06:52
in reply to nevent1q…49m7
Author Public Key
npub1s9uc08n58mxqk5umvapqulwzng0sja635q86r36d8n4rr9r9ygaskjdnmuPublished at
2025-05-01 10:06:52Event JSON
{
"id": "ad796f44c2476e4b356f8b9cc86b411ee62bfd38865e2601a5cfa7e80e6d6ec0",
"pubkey": "8179879e743ecc0b539b67420e7dc29a1f097751a00fa1c74d3cea319465223b",
"created_at": 1746094012,
"kind": 1,
"tags": [
[
"p",
"9a0516c9ce94d2b8c5f45b3a9e993af31666ea836d10d9966e748da7dba4166c"
],
[
"p",
"b8fcf3fa16a90df5527b31715505e245a962248ce8e86cdbf914151bcb9998fc"
],
[
"p",
"8179879e743ecc0b539b67420e7dc29a1f097751a00fa1c74d3cea319465223b"
],
[
"e",
"405788dcad80202b289060aef53440c6788768aacab3155a2d6234a8d93435de",
"",
"reply",
"9a0516c9ce94d2b8c5f45b3a9e993af31666ea836d10d9966e748da7dba4166c"
],
[
"e",
"445749ee2dc550bb4f617e6212d95512936a81a93906a15cfe0a153865fc365c",
"",
"root",
"b8fcf3fa16a90df5527b31715505e245a962248ce8e86cdbf914151bcb9998fc"
],
[
"proxy",
"https://manganiello.social/objects/88912390-b226-4c0f-8e54-c90abc7db4f9",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://manganiello.social/objects/88912390-b226-4c0f-8e54-c90abc7db4f9",
"pink.momostr"
],
[
"-"
]
],
"content": "even on that I'd separate the short-term craze from the long-term implications.\n\nI'm worried only up to a certain point about cynical and uninformed CEOs who only want to cut their costs. Yes, some roles are likely to go for good, or be deeply changed by AI, but I don't see engineering jobs go anywhere. You can't put 100% AI-generated code in production and expect it to run itself and maintain by itself. Those CEOs will just come back with their tails behind their legs to hire back from the market, at an inflated price, the roles that they laid off (many are already doing that).\n\nBut the engineers who learn how to master these tools to boost their productivity without letting them erode their skills are those who will win on the long run.\n\nThose who refuse to embrace them altogether will be akin to an accountant who 40 years ago wanted to do all of his calculations by hand and refused to use a pocket calculator. Or the engineer who 15 years ago refused to look up answers to common coding problems on StackOverflow and only relied on man pages. No matter how brilliant these figures were in their jobs, they couldn't compete with a machine once the technology was mature enough to boost up the expected productivity requirements for someone in their role. And eventually people who mastered the new tools became more productive than them.\n\nOn the other hand, those that start depending too much on these technologies are those that will struggle the most if you put them in an environment where these tools aren't readily available. They're akin to the Eclipse fan boy of 20 years ago that learned how to code in Java only in Eclipse and couldn't use any other IDE/editor. Or the StackOverflow serial copy-paste guy who doesn't bother to understand the code, and who is likely to cry when something breaks in production.\n\nThose who win on the long run are usually those who embrace the new tools pragmatically, while still providing added value compared to those tools - without putting themselves in the conditions where those tools can easily replace their job entirely.",
"sig": "1c815ed36583fb884b48bfd2d65d483b1896248bd9e92d2035dd254286566cfb865f8ca8f7a674ca338dc299d57e1a9eecbbdd8cdb0ec67df3be29123c0c879e"
}