Benjamin Han<p>(Coding with AI: 1/5)</p><p>I love <a href="https://sigmoid.social/tags/running" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>running</span></a>, but I also love coding. I can still code for hours a day. But there’s a limit: I could only get a few hours of quality work in before feeling exhausted. That changed a month ago, when I started experimenting with coding AI. Since then, I’ve had to consciously cut down my coding hours — it’s so much fun (and addictive) that I simply can’t stop!…</p><p>(read: <a href="https://www.linkedin.com/posts/benjaminhan_ai-genai-coding-activity-7368876024144564224-zPHg" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linkedin.com/posts/benjaminhan</span><span class="invisible">_ai-genai-coding-activity-7368876024144564224-zPHg</span></a>)</p><p><a href="https://sigmoid.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> <a href="https://sigmoid.social/tags/genAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>genAI</span></a> <a href="https://sigmoid.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>coding</span></a> <a href="https://sigmoid.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://sigmoid.social/tags/agenticAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>agenticAI</span></a> <a href="https://sigmoid.social/tags/softwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>softwareEngineering</span></a> <a href="https://sigmoid.social/tags/futureOfWork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>futureOfWork</span></a></p>
Recherches récentes
Options de recherche
#softwareengineering
4 messages4 participants1 message aujourd’hui
I got my paper for a conference rejected and that's how I feel right now:
The paper is dope, BTW. Just needs a bit more time, care and love.
We don't need more. We need less.
Every week:
A new framework.
A new "layer".
A new AI wrapper.
A new YAML format to abstract what used to be a shell script.
And then we wonder:
"Why is our software hard to debug?"
"Why do our builds break randomly?"
"Why is onboarding a 6-month journey through tribal folklore?"
I once said I write bug-free software that can be finished.
People laughed, especially product people.
Not because it's wrong.
But because they’ve forgotten it's possible.
We build complexity on top of confusion:
A + B becomes C.
C + D becomes E.
Now, E is broken, and we would create a new layer, but nobody knows how A or B worked in the first place. For example HTML/JavaScript, we leave it there and just add layers around it.
Take XML.
Everyone says it's ugly.
But you could validate it automatically, generate diagrams, enforce structure.
Now we're parsing YAML with 7 linters and still can't tell if a space is a bug.
Take Gradle.
You can define catalogues, versioning, and settings, but can't update a dependency without reading 3 blogs and sacrificing a goat.
This is called "developer experience" now?
Take Spring Boot.
I wouldn't trust a Spring Boot or any java Framework powered airplane.
Too many CVEs. Too much magic. Too little control.
We don't need "smarter" tools.
We need dumber, boring, reliable defaults.
Start boring.
Start small.
Then only change the 1% that needs to be fast, clever, or shiny.
You'll rarely even reach that point.
Like everyone says, "Y is more performant and faster than X", but no one reached the limit of X. Why should I care? Meanwhile, we use performant AI.
Real engineering is not chasing hype.
It's understanding the system so deeply that you no longer need most of it.
We've replaced curiosity with cargo cults.
We've replaced learning with LLM prompting.
And somehow, we're surprised when AI loses to a 1980s Atari in a chess game.
At least the Atari understood its own memory.
Simplicity = less maintenance = fewer bugs = happier teams.
We need less. Not more.
#devex #simplicity #softwareengineering #nocodependency#stopthehype #bugfree #springboot #gradle #xml #yamlhell #boringisgood #minimalism #AIhype #infrastructure #cleancode #pragmatism #java #NanoNative
Dans un monde où les systèmes deviennent toujours plus complexes, l'architecture logicielle joue un rôle crucial. Cette formation intensive vous permettra de :
- Maîtriser les fondamentaux de l'architecture modulaire
- Comprendre les patterns essentiels, de l'Event-Driven Architecture aux Microservices
- Acquérir une approche pragmatique pour la migration des systèmes legacy
https://buff.ly/42Y61lT
Join ACCU For Access To Journals
ACCU members receive two fantastic journals:
C Vu - The formal journal of ACCU for its members Overload - Journal focusing on all aspects of software development
Memberships from just £35/year: https://accu.org/menu-overviews/membership/
accu.orgMembership InformationACCU - professionalism in programming
This week I'm mostly in Iowa. I gave a talk yesterday at Iowa State (https://www.ece.iastate.edu/events/joint-cs-and-ecpe-seminar-with-dan-katz-reception-to-follow/) and am meeting lots of people with interests in #ResearchSoftware and #SoftwareEngineering. Tomorrow I'll be at U Iowa for a Heliophysics workshop (https://tinyurl.com/HelioSoft2025) where I'll be discussing research software and standards.
www.ece.iastate.eduJoint CS and ECpE Seminar with Daniel Katz – Department of Electrical and Computer EngineeringCollege of Engineering, Iowa State University
For my next #Perl #blog post, should I write about:
* Util::H2O::More as an alternative to Moo for #OOP modulinos, or
* Log::Any to log to the #Apple #macOS unified logging system?
Some background:
* Moo with modulinos: https://phoenixtrap.com/2025/08/03/moodulinos/
* Util::H2O::More: https://metacpan.org/pod/Util::H2O::More
* Log::Any: https://metacpan.org/pod/Log::Any
* Apple’s unified logging system: https://developer.apple.com/documentation/os/logging
The Phoenix Trap · Lightweight object-oriented Perl scripts: From modulinos to moodulinosDeveloping a complex Perl script that needs just a llittle object-orientation? Try the modulino pattern alongside the lightweight Moo module.
#Codingbootcamps, once a popular pathway to #softwareengineering jobs, are #disappearing due to the rise of #AI. AI’s ability to generate code has eliminated many #entryleveldeveloper roles, making it difficult for bootcamp graduates to find employment. https://www.reuters.com/lifestyle/bootcamp-bust-how-ai-is-upending-software-development-industry-2025-08-09/?eicker.news #tech #media #news
My "Highly Interactive Testing for Uninterrupted Development Flow" paper is live on arxiv! 
It's my first submitted paper, it's unaffiliated and unsupervised.
I've put a lot of effort into it and already got a few important insights on the design of the testing library and corresponding workflows.
I already aware of some weaknesses of my work, but hope you enjoy the reading!
Update: got it, no further help needed.
I'm trying to publish a preprint of my paper for ICFP-2025 on https://arxiv.org. I need an endorsement to submit it to cs.SE category.
Can someone help me with that?
To endorse me, you need to have at least 3 articles published in cs.* categories for the last 5 years.
https://info.arxiv.org/help/endorsement.html
P.S. Got the endorsement, submitted the preprint for review. Kudos to @michaeldorner
arxiv.orgarXiv.org e-Print archive
I went off on a bit of a vent on the AImperor's new clothes:
(Slightly revised edition, thanks for all the feedback:)
https://opensourcerer.eu/the-aimperors-new-clothes/index.html
opensourcerer.euThe AImperor is Neither Naked nor Impeccably Dressed | OpenSourcerer.euLars Marowsky-Brée on Free, Libre, and Open Source, Software Engineering, and IT
Even experienced software engineers can be intimidated when joining a new team...
You might have to:
Learn a new domain. Learn new coding patterns. Learn new development processes.
As an existing team member, make an effort to walk newcomers through your process of committing code, even if it's already documented…
Can they work through it themselves?