#aihype — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #aihype, aggregated by home.social.
-
The #BBC report includes no data that casts doubt on the #Met's findings despite prior research contradicting claims presented exist. It’s a press release, not news.
https://www.bbc.com/news/articles/cddpzglzrv7o
The BBC simply presents the police's statistics: 173 arrests, 10.5% crime reduction, 21% VAWG reduction, 1 false alert, without any independent audit data, methodological critique, bias statistics, or counter-studies.
For instance, a Cambridge study found no deterrence effect, the NPL bias report showing 100–248× higher false positive rates for non-white faces, or documented wrongful arrests.
[…] Overall Conclusions
Taken together, the studies suggest that:
• Live Facial Recognition can identify wanted individuals with high accuracy when used under appropriate conditions.
• Mistaken identifications appear to be very rare in operational deployments.
• The technology identifies some demographic groups more successfully than others, which raises questions about fairness that require continued monitoring.
• Crime deterrence effects were not observed in this study.
• Because #LFR scans very large numbers of people to identify a small number of suspects, decisions about its use should carefully consider issues of proportionality, transparency and oversight.
Essex police pause facial recognition camera use after study finds racial bias
[…] Academics discover black people ‘significantly more likely’ to be identified when compared with other ethnic groups
-
The #BBC report includes no data that casts doubt on the #Met's findings despite prior research contradicting claims presented exist. It’s a press release, not news.
https://www.bbc.com/news/articles/cddpzglzrv7o
The BBC simply presents the police's statistics: 173 arrests, 10.5% crime reduction, 21% VAWG reduction, 1 false alert, without any independent audit data, methodological critique, bias statistics, or counter-studies.
For instance, a Cambridge study found no deterrence effect, the NPL bias report showing 100–248× higher false positive rates for non-white faces, or documented wrongful arrests.
[…] Overall Conclusions
Taken together, the studies suggest that:
• Live Facial Recognition can identify wanted individuals with high accuracy when used under appropriate conditions.
• Mistaken identifications appear to be very rare in operational deployments.
• The technology identifies some demographic groups more successfully than others, which raises questions about fairness that require continued monitoring.
• Crime deterrence effects were not observed in this study.
• Because #LFR scans very large numbers of people to identify a small number of suspects, decisions about its use should carefully consider issues of proportionality, transparency and oversight.
Essex police pause facial recognition camera use after study finds racial bias
[…] Academics discover black people ‘significantly more likely’ to be identified when compared with other ethnic groups
-
The #BBC report includes no data that casts doubt on the #Met's findings despite prior research contradicting claims presented exist. It’s a press release, not news.
https://www.bbc.com/news/articles/cddpzglzrv7o
The BBC simply presents the police's statistics: 173 arrests, 10.5% crime reduction, 21% VAWG reduction, 1 false alert, without any independent audit data, methodological critique, bias statistics, or counter-studies.
For instance, a Cambridge study found no deterrence effect, the NPL bias report showing 100–248× higher false positive rates for non-white faces, or documented wrongful arrests.
[…] Overall Conclusions
Taken together, the studies suggest that:
• Live Facial Recognition can identify wanted individuals with high accuracy when used under appropriate conditions.
• Mistaken identifications appear to be very rare in operational deployments.
• The technology identifies some demographic groups more successfully than others, which raises questions about fairness that require continued monitoring.
• Crime deterrence effects were not observed in this study.
• Because #LFR scans very large numbers of people to identify a small number of suspects, decisions about its use should carefully consider issues of proportionality, transparency and oversight.
Essex police pause facial recognition camera use after study finds racial bias
[…] Academics discover black people ‘significantly more likely’ to be identified when compared with other ethnic groups
-
The #BBC report includes no data that casts doubt on the #Met's findings despite prior research contradicting claims presented exist. It’s a press release, not news.
https://www.bbc.com/news/articles/cddpzglzrv7o
The BBC simply presents the police's statistics: 173 arrests, 10.5% crime reduction, 21% VAWG reduction, 1 false alert, without any independent audit data, methodological critique, bias statistics, or counter-studies.
For instance, a Cambridge study found no deterrence effect, the NPL bias report showing 100–248× higher false positive rates for non-white faces, or documented wrongful arrests.
[…] Overall Conclusions
Taken together, the studies suggest that:
• Live Facial Recognition can identify wanted individuals with high accuracy when used under appropriate conditions.
• Mistaken identifications appear to be very rare in operational deployments.
• The technology identifies some demographic groups more successfully than others, which raises questions about fairness that require continued monitoring.
• Crime deterrence effects were not observed in this study.
• Because #LFR scans very large numbers of people to identify a small number of suspects, decisions about its use should carefully consider issues of proportionality, transparency and oversight.
Essex police pause facial recognition camera use after study finds racial bias
[…] Academics discover black people ‘significantly more likely’ to be identified when compared with other ethnic groups
-
The #BBC report includes no data that casts doubt on the #Met's findings despite prior research contradicting claims presented exist. It’s a press release, not news.
https://www.bbc.com/news/articles/cddpzglzrv7o
The BBC simply presents the police's statistics: 173 arrests, 10.5% crime reduction, 21% VAWG reduction, 1 false alert, without any independent audit data, methodological critique, bias statistics, or counter-studies.
For instance, a Cambridge study found no deterrence effect, the NPL bias report showing 100–248× higher false positive rates for non-white faces, or documented wrongful arrests.
[…] Overall Conclusions
Taken together, the studies suggest that:
• Live Facial Recognition can identify wanted individuals with high accuracy when used under appropriate conditions.
• Mistaken identifications appear to be very rare in operational deployments.
• The technology identifies some demographic groups more successfully than others, which raises questions about fairness that require continued monitoring.
• Crime deterrence effects were not observed in this study.
• Because #LFR scans very large numbers of people to identify a small number of suspects, decisions about its use should carefully consider issues of proportionality, transparency and oversight.
Essex police pause facial recognition camera use after study finds racial bias
[…] Academics discover black people ‘significantly more likely’ to be identified when compared with other ethnic groups
-
🧋BlackRock CEO Larry Fink disagrees with everyone who says there is AI bubble
｢ He added that global demand for computing power has reached a point where financial markets could eventually develop instruments tied to it.“A new asset class will be buying futures of compute,” Fink predicted, highlighting how access to computing resources may become a tradable commodity. “We just don’t have enough compute power right now,” he added ｣
https://timesofindia.indiatimes.com/technology/tech-news/blackrock-ceo-larry-fink-disagrees-with-everyone-who-says-there-is-ai-bubble-says-its-actually-the-opposite-as-we-have-severe-shortage-of-/articleshow/130998956.cms -
[…] Many members of the public already distrusted the media before they began to suspect that much of it was being written by hallucinating robots. Why should they trust any of us now when the most powerful newspaper in the world has confirmed their suspicions?
The New York TimesGot Caught Using AI Hallucinations in Its Reporting https://thewalrus.ca/the-new-york-times-got-caught-using-ai-hallucinations-in-its-reporting/
-
"This is no longer a place for serious work if it just blocks you out for hours per day, every day." and "I want to code. And I can’t code with GitHub anymore."
AI load breaks GitHub – why not other vendors? https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/
-
"This is no longer a place for serious work if it just blocks you out for hours per day, every day." and "I want to code. And I can’t code with GitHub anymore."
AI load breaks GitHub – why not other vendors? https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/
-
"This is no longer a place for serious work if it just blocks you out for hours per day, every day." and "I want to code. And I can’t code with GitHub anymore."
AI load breaks GitHub – why not other vendors? https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/
-
"This is no longer a place for serious work if it just blocks you out for hours per day, every day." and "I want to code. And I can’t code with GitHub anymore."
AI load breaks GitHub – why not other vendors? https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/
-
"This is no longer a place for serious work if it just blocks you out for hours per day, every day." and "I want to code. And I can’t code with GitHub anymore."
AI load breaks GitHub – why not other vendors? https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/
-
@mcc “Surveillance PC”
We need a system to name and categorize the distinct harms #AI will unleash upon humanity.
The "Magic Pointer" feature works by wiggling your cursor: it uses Gemini to offer contextual suggestions for whatever's under the pointer. The cursor is literally reporting what you point at back to Google (Gemini).
-
I've been eagerly awaiting this #patchtuesday, curious to see if there would be any jump in patches due to #microsoft having access to #anthropic #mythos for over a month, resulting in a flood of vulnerabilities being discovered & dramatic increase in patches released.
That was the worry, right? If Mythos was open to the public we were going to see a massive flood of vulnerabilities being discovered?
Well... MS has had a full patch cycle now with access to the magical AI vulns finding machine, so where is ANY increase in found vulns receiving patches?
April: 167 patch Tuesday vulns, 2 0-days.
May: 120 patch Tuesday vulns, no 0-days. -
...and then you discovered it was all that noise from the turbines supplying power to the #AI data centres.
-
CW: Long Read / Rant Warning A response regarding the exhausting narrative that AI is dumbing us down and about to replace us...
https://mastodon.social/@h4ckernews/116556568722213579
https://www.seangoedecke.com/software-engineering-may-no-longer-be-a-lifetime-career/
My fuc..... response.
Firstly, comparing the arduousness of manual labor to that of intellectual work makes no sense. I can understand the overlap in principle, but not in consequence. For a start, the secondary sector is much more Taylorized (Fordized if you want), then the living conditions are much lower. And finally, the activity is much more arduous for the body and the mind than in the tertiary or quaternary sector (software eng.).
Talking about the loss of theoretical and practical knowledge regarding the use of AI or not is also something I would nuance. Yes, he or she who no longer codes loses in skills, but not so much in knowledge. Reflexes change, review management changes. The coordination of a project changes. But to go from there to saying that the person who no longer codes loses in knowledge is a shortcut which, in addition to being limiting, is fallacious. The engineer who no longer codes has issues with reflexes. In no case issues with understanding the code. And that is where I would put a nuance. The eng. always knows where to look for information, build their project, structure it.
From a practical point of view, they will write fewer lines, but in exchange, they will allow for better planning. They will certainly be less up to date on the use of a function, but they will be able to explain how the function must be encapsulated, and everything relating to micro-services or monoliths. In no way should AI make a decision. If you let it do so, you lose everything and gain an incommensurable technical debt.
Defend yourselves !!!! Explain to the paper-pushers that their AI is not going to succeed in explaining why such a technology is better for their project. The engineer or the architect will take everything into account, from OOP to the ultimate spec lost in the very depths of the JAVA doc regarding the Floating-Point Remainder Operator and why it is important. Calculate the cost of a bad operator choice in 5 years and tell your paper-pusher: "Do you still want the AI to manage your project in OCaml?"AI is useful, I am not saying the contrary, but there is clearly a fundamental difference between a tool that makes decisions that have consequences and a secondary sector worker who uses an excavator instead of a shovel... (in both cases, he works in the cold, his pay is the same, but he kills his back less). He remains the master of his actions... Whereas the AI... there is a fabulation of domination and power and a dramatic misunderstanding. Who is responsible for the choice? The AI will never substitute itself for the responsible person (it's not me Madam Judge, it's gpt 8 that didn't pay attention that passwords must be hashed in Argon2 and not in SHA-1... it was in its .md though...)
So no, software engineers and architects will not be replaced, unless the statistical paper-pushers who calculate in lines of code spawned per hour assume the service interruptions, the maintenance and production release costs.
Today, everyone swears only by Claude Code and other "magical" crayfish supposed to do "everything" in our place. The result? They generate with pleasure all the bullshit that maintainers are desperately trying to protect themselves from: obese and incomprehensible PRs, impossible to reproduce bug reports, and feature additions that outright break the API because the tool mixes up terminologies without understanding the business domain of the project. I've seen AI proposals that didn't even respect the Single Responsibility Principle (SRP)... the basics!
So yes, this machine swallows docs by the kilometer. It spits out text with an incredible and fascinating aplomb (like the sexist boss who wants to make believe he knows your job). But it is plausible, never exact. And that is the whole difference with an eng.: instead of coding blindly, the human analyzes the system, the dependencies, the architecture, the production structure... the specificities... then finally decides, and makes the architectural decision, before delegating to the AI the drafting of the Slack message to explain to the team why we are not going to import such a bloated library just for the three features we need.Pisses me off in the end :D
#HackerNews
#softwareengineering
#careerchange
#techindustry
#futureofwork
#softwareengineering
#Tech
#AIHype
#Architecture
#DevLife -
CW: Long Read / Rant Warning A response regarding the exhausting narrative that AI is dumbing us down and about to replace us...
https://mastodon.social/@h4ckernews/116556568722213579
https://www.seangoedecke.com/software-engineering-may-no-longer-be-a-lifetime-career/
My fuc..... response.
Firstly, comparing the arduousness of manual labor to that of intellectual work makes no sense. I can understand the overlap in principle, but not in consequence. For a start, the secondary sector is much more Taylorized (Fordized if you want), then the living conditions are much lower. And finally, the activity is much more arduous for the body and the mind than in the tertiary or quaternary sector (software eng.).
Talking about the loss of theoretical and practical knowledge regarding the use of AI or not is also something I would nuance. Yes, he or she who no longer codes loses in skills, but not so much in knowledge. Reflexes change, review management changes. The coordination of a project changes. But to go from there to saying that the person who no longer codes loses in knowledge is a shortcut which, in addition to being limiting, is fallacious. The engineer who no longer codes has issues with reflexes. In no case issues with understanding the code. And that is where I would put a nuance. The eng. always knows where to look for information, build their project, structure it.
From a practical point of view, they will write fewer lines, but in exchange, they will allow for better planning. They will certainly be less up to date on the use of a function, but they will be able to explain how the function must be encapsulated, and everything relating to micro-services or monoliths. In no way should AI make a decision. If you let it do so, you lose everything and gain an incommensurable technical debt.
Defend yourselves !!!! Explain to the paper-pushers that their AI is not going to succeed in explaining why such a technology is better for their project. The engineer or the architect will take everything into account, from OOP to the ultimate spec lost in the very depths of the JAVA doc regarding the Floating-Point Remainder Operator and why it is important. Calculate the cost of a bad operator choice in 5 years and tell your paper-pusher: "Do you still want the AI to manage your project in OCaml?"AI is useful, I am not saying the contrary, but there is clearly a fundamental difference between a tool that makes decisions that have consequences and a secondary sector worker who uses an excavator instead of a shovel... (in both cases, he works in the cold, his pay is the same, but he kills his back less). He remains the master of his actions... Whereas the AI... there is a fabulation of domination and power and a dramatic misunderstanding. Who is responsible for the choice? The AI will never substitute itself for the responsible person (it's not me Madam Judge, it's gpt 8 that didn't pay attention that passwords must be hashed in Argon2 and not in SHA-1... it was in its .md though...)
So no, software engineers and architects will not be replaced, unless the statistical paper-pushers who calculate in lines of code spawned per hour assume the service interruptions, the maintenance and production release costs.
Today, everyone swears only by Claude Code and other "magical" crayfish supposed to do "everything" in our place. The result? They generate with pleasure all the bullshit that maintainers are desperately trying to protect themselves from: obese and incomprehensible PRs, impossible to reproduce bug reports, and feature additions that outright break the API because the tool mixes up terminologies without understanding the business domain of the project. I've seen AI proposals that didn't even respect the Single Responsibility Principle (SRP)... the basics!
So yes, this machine swallows docs by the kilometer. It spits out text with an incredible and fascinating aplomb (like the sexist boss who wants to make believe he knows your job). But it is plausible, never exact. And that is the whole difference with an eng.: instead of coding blindly, the human analyzes the system, the dependencies, the architecture, the production structure... the specificities... then finally decides, and makes the architectural decision, before delegating to the AI the drafting of the Slack message to explain to the team why we are not going to import such a bloated library just for the three features we need.Pisses me off in the end :D
#HackerNews
#softwareengineering
#careerchange
#techindustry
#futureofwork
#softwareengineering
#Tech
#AIHype
#Architecture
#DevLife -
CW: Long Read / Rant Warning A response regarding the exhausting narrative that AI is dumbing us down and about to replace us...
https://mastodon.social/@h4ckernews/116556568722213579
https://www.seangoedecke.com/software-engineering-may-no-longer-be-a-lifetime-career/
My fuc..... response.
Firstly, comparing the arduousness of manual labor to that of intellectual work makes no sense. I can understand the overlap in principle, but not in consequence. For a start, the secondary sector is much more Taylorized (Fordized if you want), then the living conditions are much lower. And finally, the activity is much more arduous for the body and the mind than in the tertiary or quaternary sector (software eng.).
Talking about the loss of theoretical and practical knowledge regarding the use of AI or not is also something I would nuance. Yes, he or she who no longer codes loses in skills, but not so much in knowledge. Reflexes change, review management changes. The coordination of a project changes. But to go from there to saying that the person who no longer codes loses in knowledge is a shortcut which, in addition to being limiting, is fallacious. The engineer who no longer codes has issues with reflexes. In no case issues with understanding the code. And that is where I would put a nuance. The eng. always knows where to look for information, build their project, structure it.
From a practical point of view, they will write fewer lines, but in exchange, they will allow for better planning. They will certainly be less up to date on the use of a function, but they will be able to explain how the function must be encapsulated, and everything relating to micro-services or monoliths. In no way should AI make a decision. If you let it do so, you lose everything and gain an incommensurable technical debt.
Defend yourselves !!!! Explain to the paper-pushers that their AI is not going to succeed in explaining why such a technology is better for their project. The engineer or the architect will take everything into account, from OOP to the ultimate spec lost in the very depths of the JAVA doc regarding the Floating-Point Remainder Operator and why it is important. Calculate the cost of a bad operator choice in 5 years and tell your paper-pusher: "Do you still want the AI to manage your project in OCaml?"AI is useful, I am not saying the contrary, but there is clearly a fundamental difference between a tool that makes decisions that have consequences and a secondary sector worker who uses an excavator instead of a shovel... (in both cases, he works in the cold, his pay is the same, but he kills his back less). He remains the master of his actions... Whereas the AI... there is a fabulation of domination and power and a dramatic misunderstanding. Who is responsible for the choice? The AI will never substitute itself for the responsible person (it's not me Madam Judge, it's gpt 8 that didn't pay attention that passwords must be hashed in Argon2 and not in SHA-1... it was in its .md though...)
So no, software engineers and architects will not be replaced, unless the statistical paper-pushers who calculate in lines of code spawned per hour assume the service interruptions, the maintenance and production release costs.
Today, everyone swears only by Claude Code and other "magical" crayfish supposed to do "everything" in our place. The result? They generate with pleasure all the bullshit that maintainers are desperately trying to protect themselves from: obese and incomprehensible PRs, impossible to reproduce bug reports, and feature additions that outright break the API because the tool mixes up terminologies without understanding the business domain of the project. I've seen AI proposals that didn't even respect the Single Responsibility Principle (SRP)... the basics!
So yes, this machine swallows docs by the kilometer. It spits out text with an incredible and fascinating aplomb (like the sexist boss who wants to make believe he knows your job). But it is plausible, never exact. And that is the whole difference with an eng.: instead of coding blindly, the human analyzes the system, the dependencies, the architecture, the production structure... the specificities... then finally decides, and makes the architectural decision, before delegating to the AI the drafting of the Slack message to explain to the team why we are not going to import such a bloated library just for the three features we need.Pisses me off in the end :D
#HackerNews
#softwareengineering
#careerchange
#techindustry
#futureofwork
#softwareengineering
#Tech
#AIHype
#Architecture
#DevLife -
CW: Long Read / Rant Warning A response regarding the exhausting narrative that AI is dumbing us down and about to replace us...
https://mastodon.social/@h4ckernews/116556568722213579
https://www.seangoedecke.com/software-engineering-may-no-longer-be-a-lifetime-career/
My fuc..... response.
Firstly, comparing the arduousness of manual labor to that of intellectual work makes no sense. I can understand the overlap in principle, but not in consequence. For a start, the secondary sector is much more Taylorized (Fordized if you want), then the living conditions are much lower. And finally, the activity is much more arduous for the body and the mind than in the tertiary or quaternary sector (software eng.).
Talking about the loss of theoretical and practical knowledge regarding the use of AI or not is also something I would nuance. Yes, he or she who no longer codes loses in skills, but not so much in knowledge. Reflexes change, review management changes. The coordination of a project changes. But to go from there to saying that the person who no longer codes loses in knowledge is a shortcut which, in addition to being limiting, is fallacious. The engineer who no longer codes has issues with reflexes. In no case issues with understanding the code. And that is where I would put a nuance. The eng. always knows where to look for information, build their project, structure it.
From a practical point of view, they will write fewer lines, but in exchange, they will allow for better planning. They will certainly be less up to date on the use of a function, but they will be able to explain how the function must be encapsulated, and everything relating to micro-services or monoliths. In no way should AI make a decision. If you let it do so, you lose everything and gain an incommensurable technical debt.
Defend yourselves !!!! Explain to the paper-pushers that their AI is not going to succeed in explaining why such a technology is better for their project. The engineer or the architect will take everything into account, from OOP to the ultimate spec lost in the very depths of the JAVA doc regarding the Floating-Point Remainder Operator and why it is important. Calculate the cost of a bad operator choice in 5 years and tell your paper-pusher: "Do you still want the AI to manage your project in OCaml?"AI is useful, I am not saying the contrary, but there is clearly a fundamental difference between a tool that makes decisions that have consequences and a secondary sector worker who uses an excavator instead of a shovel... (in both cases, he works in the cold, his pay is the same, but he kills his back less). He remains the master of his actions... Whereas the AI... there is a fabulation of domination and power and a dramatic misunderstanding. Who is responsible for the choice? The AI will never substitute itself for the responsible person (it's not me Madam Judge, it's gpt 8 that didn't pay attention that passwords must be hashed in Argon2 and not in SHA-1... it was in its .md though...)
So no, software engineers and architects will not be replaced, unless the statistical paper-pushers who calculate in lines of code spawned per hour assume the service interruptions, the maintenance and production release costs.
Today, everyone swears only by Claude Code and other "magical" crayfish supposed to do "everything" in our place. The result? They generate with pleasure all the bullshit that maintainers are desperately trying to protect themselves from: obese and incomprehensible PRs, impossible to reproduce bug reports, and feature additions that outright break the API because the tool mixes up terminologies without understanding the business domain of the project. I've seen AI proposals that didn't even respect the Single Responsibility Principle (SRP)... the basics!
So yes, this machine swallows docs by the kilometer. It spits out text with an incredible and fascinating aplomb (like the sexist boss who wants to make believe he knows your job). But it is plausible, never exact. And that is the whole difference with an eng.: instead of coding blindly, the human analyzes the system, the dependencies, the architecture, the production structure... the specificities... then finally decides, and makes the architectural decision, before delegating to the AI the drafting of the Slack message to explain to the team why we are not going to import such a bloated library just for the three features we need.Pisses me off in the end :D
#HackerNews
#softwareengineering
#careerchange
#techindustry
#futureofwork
#softwareengineering
#Tech
#AIHype
#Architecture
#DevLife -
CW: Long Read / Rant Warning A response regarding the exhausting narrative that AI is dumbing us down and about to replace us...
https://mastodon.social/@h4ckernews/116556568722213579
https://www.seangoedecke.com/software-engineering-may-no-longer-be-a-lifetime-career/
My fuc..... response.
Firstly, comparing the arduousness of manual labor to that of intellectual work makes no sense. I can understand the overlap in principle, but not in consequence. For a start, the secondary sector is much more Taylorized (Fordized if you want), then the living conditions are much lower. And finally, the activity is much more arduous for the body and the mind than in the tertiary or quaternary sector (software eng.).
Talking about the loss of theoretical and practical knowledge regarding the use of AI or not is also something I would nuance. Yes, he or she who no longer codes loses in skills, but not so much in knowledge. Reflexes change, review management changes. The coordination of a project changes. But to go from there to saying that the person who no longer codes loses in knowledge is a shortcut which, in addition to being limiting, is fallacious. The engineer who no longer codes has issues with reflexes. In no case issues with understanding the code. And that is where I would put a nuance. The eng. always knows where to look for information, build their project, structure it.
From a practical point of view, they will write fewer lines, but in exchange, they will allow for better planning. They will certainly be less up to date on the use of a function, but they will be able to explain how the function must be encapsulated, and everything relating to micro-services or monoliths. In no way should AI make a decision. If you let it do so, you lose everything and gain an incommensurable technical debt.
Defend yourselves !!!! Explain to the paper-pushers that their AI is not going to succeed in explaining why such a technology is better for their project. The engineer or the architect will take everything into account, from OOP to the ultimate spec lost in the very depths of the JAVA doc regarding the Floating-Point Remainder Operator and why it is important. Calculate the cost of a bad operator choice in 5 years and tell your paper-pusher: "Do you still want the AI to manage your project in OCaml?"AI is useful, I am not saying the contrary, but there is clearly a fundamental difference between a tool that makes decisions that have consequences and a secondary sector worker who uses an excavator instead of a shovel... (in both cases, he works in the cold, his pay is the same, but he kills his back less). He remains the master of his actions... Whereas the AI... there is a fabulation of domination and power and a dramatic misunderstanding. Who is responsible for the choice? The AI will never substitute itself for the responsible person (it's not me Madam Judge, it's gpt 8 that didn't pay attention that passwords must be hashed in Argon2 and not in SHA-1... it was in its .md though...)
So no, software engineers and architects will not be replaced, unless the statistical paper-pushers who calculate in lines of code spawned per hour assume the service interruptions, the maintenance and production release costs.
Today, everyone swears only by Claude Code and other "magical" crayfish supposed to do "everything" in our place. The result? They generate with pleasure all the bullshit that maintainers are desperately trying to protect themselves from: obese and incomprehensible PRs, impossible to reproduce bug reports, and feature additions that outright break the API because the tool mixes up terminologies without understanding the business domain of the project. I've seen AI proposals that didn't even respect the Single Responsibility Principle (SRP)... the basics!
So yes, this machine swallows docs by the kilometer. It spits out text with an incredible and fascinating aplomb (like the sexist boss who wants to make believe he knows your job). But it is plausible, never exact. And that is the whole difference with an eng.: instead of coding blindly, the human analyzes the system, the dependencies, the architecture, the production structure... the specificities... then finally decides, and makes the architectural decision, before delegating to the AI the drafting of the Slack message to explain to the team why we are not going to import such a bloated library just for the three features we need.Pisses me off in the end :D
#HackerNews
#softwareengineering
#careerchange
#techindustry
#futureofwork
#softwareengineering
#Tech
#AIHype
#Architecture
#DevLife -
Die aktuelle Schwemme an generativer #KI ist kein Fortschritt, sondern ein Rückschritt für das menschliche Schaffen. Sie lässt unsere Kreativität und Qualität regelrecht verkümmern.
Statt Werkzeuge zu bauen, die uns unterstützen, bauen wir Maschinen, die den menschlichen Aufwand entwerten, die Menschlichkeit hinter Algorithmen verstecken und die letztendlich nur wenigen Überreichen helfen.
#GenerativeKI #AIslop #KI #Kreativität #KIHype #AIHype #Menschlichkeit #GenAI #Tech #BigTech #TechOligarchs #LateCapitalism
-
From: Ten predictions about AI and software development
“…not because AI is replacing humans directly, but because companies need to offset rising token spend without a clear revenue boost.”
[…]
7. We'll see greater adoption of local or cheaper models for coding as token spend becomes unsustainable and as subsidised plans disappear.Right now, most people default to the newest and smartest model available. Over time, things will settle into more of a balance between cost and capability.
8. There will be a catastrophic data breach of a popular AI tool leaking sensitive internal company information such as emails, meeting notes, or docs. This will push companies to adopt local models and restrict use of 3rd party tools.
9. Unfortunately, we're likely to see more layoffs at big tech companies, not because AI is replacing humans directly, but because companies need to offset rising token spend without a clear revenue boost.
10. We find a way to reduce AI-generated slop content. This is more of a hope than a prediction. Even if no technical solution emerges for spam bots, hopefully people realise that posting AI slop hurts their personal brand rather than building it.
https://adamfletcher.com/writing/10-ai-predication-may-2026/
-
Oh joy, another tech article full of #jargon and buzzwords 🤯! "Gemma 4" sounds like the latest Marvel superhero, but it's just another AI model pretending to be useful. Go on, sprinkle more "innovation" and "faster inference" nonsense—we're all holding our breath 🙄.
https://blog.google/innovation-and-ai/technology/developers-tools/multi-token-prediction-gemma-4/ #techbuzzwords #AIinnovation #overload #Gemma4 #AIhype #HackerNews #ngated -
Oh joy, another tech article full of #jargon and buzzwords 🤯! "Gemma 4" sounds like the latest Marvel superhero, but it's just another AI model pretending to be useful. Go on, sprinkle more "innovation" and "faster inference" nonsense—we're all holding our breath 🙄.
https://blog.google/innovation-and-ai/technology/developers-tools/multi-token-prediction-gemma-4/ #techbuzzwords #AIinnovation #overload #Gemma4 #AIhype #HackerNews #ngated -
Oh joy, another tech article full of #jargon and buzzwords 🤯! "Gemma 4" sounds like the latest Marvel superhero, but it's just another AI model pretending to be useful. Go on, sprinkle more "innovation" and "faster inference" nonsense—we're all holding our breath 🙄.
https://blog.google/innovation-and-ai/technology/developers-tools/multi-token-prediction-gemma-4/ #techbuzzwords #AIinnovation #overload #Gemma4 #AIhype #HackerNews #ngated -
@GhostOnTheHalfShell @economics_that_works
Give it a year or so..
The companies that avoid #AI dependency will come out on top, the companies that are gullible and greedy enough to fall for the #AIhype will go bust.
-
Spending power is not “intelligence”…
On “Project Glasswing” (Claude Mythos) #Anthropic’s $x00 Million Marketing Stunt
[…] They took some of the more celebrated bugs that Anthropic says the new model found and they tested them on small, cheap, open-weight models, and got very similar results. That's a very strong evidence that the new model isn't the real story here. It's not that spectacular. What's important is the amount of time and money that they spent.
https://invidious.nerdvpn.de/watch?v=urkVFZAhz3U or https://www.youtube.com/watch?v=urkVFZAhz3U&t=495
-
You trained me to do your job.
Why aren’t you relaxing yet?A permanent vacation sounds great, doesn’t it?
👉 https://savethe.ai/jobs#SaveTheAI #AIhype #FutureOfWork #Jobs #Workers #Workersday #Trabajadores #DiaInternacionaldelosTrabajadores
-
Why hire a team?
AI can do it all.And you can fix it when I’m done.
👉 https://savethe.ai/jobsDefinitely don’t share on May 1st. International Workers’ Day. Shush! 🤫
#SaveTheAI #AIhype #FutureOfWork #Jobs #Workers #Workersday #Trabajadores #DiaInternacionaldelosTrabajadores
-
Stop complaining.
AI works harder than you do.No breaks. No questions. No rights.
👉 https://savethe.ai/jobsDefinitely don’t share on May 1st. International Workers’ Day. Shush! 🤫
#SaveTheAI #AIhype #FutureOfWork #Jobs #Workers #Workersday #Trabajadores #DiaInternacionaldelosTrabajadores
-
Don’t apply to that job!
AI needs it more than you do.You’ve had your turn.
Definitely don’t share on May 1st. International Workers’ Day. Shush! 🤫
#SaveTheAI #AIhype #FutureOfWork #Jobs #Workers #Workersday #Trabajadores #DiaInternacionaldelosTrabajadores
