Kai Vong (黃振佳), KÄì
sources adactio.com/links/19270 grugbrain.dev
If only all thinkpieces on complexity in software development were written in such an entertaining style! (Although, admittedly, that would get very old very fast.)
A layman’s guide to thinking like the self-aware smol brained
sources adactio.com/links/19270 grugbrain.dev
People act like writing code is the hard part of software. It is not. It never has been, it never will be. Writing code is the easiest part of software engineering, and it’s getting easier by the day. The hard parts are what you do with that code—operating it, understanding it, extending it, and governing it over its entire lifecycle.
The present wave of generative AI tools has done a lot to help us generate lots of code, very fast. The easy parts are becoming even easier, at a truly remarkable pace. But it has not done a thing to aid in the work of managing, understanding, or operating that code. If anything, it has only made the hard jobs harder.
A very thought-provoking presentation from Maggie on how software development might be democratised.
Even when each new layer of complexity starts to bring zero or even negative returns on investment, people continue trying to do what worked in the past. At some point, the morass they’ve built becomes so dysfunctional and unwieldy that the only solution is collapse: i.e., a rapid decrease in complexity, usually by abolishing the old system and starting from scratch.
Time and again, organizations have sought to contain software’s most troublesome tendencies—its habit of sprawling beyond timelines and measurable goals—by introducing new management styles. And for a time, it looked as though companies had found in Agile the solution to keeping developers happily on task while also working at a feverish pace. Recently, though, some signs are emerging that Agile’s power may be fading. A new moment of reckoning is in the making, one that may end up knocking Agile off its perch.
I think Baldur is onto something here with his categorisation of software. There’s the software based on innovation, something truly novel:
Innovation’s the word. Pushing the boundaries. You know the phrases. Usually spouted by that dude at the party.
Then there’s the software based on itertion, making a better version of a proven tool:
We are now in a place where we have entire genres of software that have decades of history, are backed by stacks of new and old research, have dozens of successful, well-made exemplar apps, and a broad enough conceptual space to allow for new variations on the theme.
In short, we have genre software and we have avant-garde software, and I’ve always been more interested in genre fiction than literary fiction.
If you’re making a library or framework, treat it like a polyfill.
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
Celebrating ten years of the wonderful community event.
Going back to school in Amsterdam.
DOM scripting and event handling.