@ufried
Uwe Friedrichsen. Longtime traveler in the world of IT. Dot Connector. Keeper of timeless wisdom. Translator between floors. System design. Resilience. Sustainability. Tries to make (not only) IT a (bit) better place.
Next week. Final chance.
Agile meets Architecture 2026 starts in 7 days.
28+ sessions. Interactive AMAs. Unconference format. Practitioners sharing real solutions.
After this week, it's too late.
Final seats available.
Book now: pretix.eu/AmA/2026/
March 10β11, Berlin
hmm, lobbyzentrale wΓΌrde es gefΓΌhlt noch etwas besser treffen ...
the problem i see with most decision makers is they never realized that their perceived problems with sw dev usually are not caused by sw dev. they think, reducing time and cost for sw production further would solve all their problems with sw dev.
personally, i think the opposite will happen.
/e
exactly the same, i am afraid: immediate sw dev cost and throughput.
now they hope to increase throughput using ai (which is a pattern i observe in many companies, especially at IT decision maker level).
/1
delivering features nobody wants is the biggest problem we currently have in software development. delivering more features without clearly measuring their value will just aggravate the problem.
important: users/customers define value, not business departments. this is where the problems start 2/2
just read in a client document: "with ai, we have to focus on value, e.g., features delivered".
well, a feature delivered is _not_ value. it is just output. it only becomes value if the user accepts it (and is willing to use/pay for it).
1/2
i released a new blog post discussing why you are not "left behind" if you do not become an AI-based software development expert right now, but still need to learn AI-based software development. sounds paradoxical? yes, the world sometimes is ;)
enjoy if you like ;)
www.ufried.com/blog/not_lef...
I released a new blog post, discussing the concept of "technical debt", how it is about much more than technical debt alone, what we actually try to achieve β resulting in an extensive graph of detrimental drivers we need to consider. enjoy if you like ... ;)
www.ufried.com/blog/forget_...
da hilft dann auch kein alibi-bildchen mit don quijote mehr, wenn der artikel voller ernst die βkonsequenzenβ der aus der luft gegriffenen behauptung von herrn merz durchdekliniert, ohne je die behauptung auf ihren gehalt hin zu hinterfragen. da sehe ich ein versagen der medien auf ganzer linie /e
mich bringt es nicht mehr zum staunen. es ist so plump, dass es schon peinlich ist. traurig ist daran nur, wie die medien (auch der genannte artikel) solche plumpen aussagen dann voller eifer βanalysierenβ und sie damit erst gefΓ€hrlich machen - und die leute, die noch darauf hereinfallen /1
darum geht es herrn merz doch gar nicht. ΓΌberlege einfach, wer von der verunsicherung profitiert - genau die parteien, deren oberster lobbyist herr merz ist. und wenn lobbyisten inhaltlich keine argumente haben, stellen sie einfach behauptungen auf. schade nur, dass die presse das noch verbreitet
β We solve problems by adding, not subtractingβeven when subtracting is better.
@ufried.bsky.social : "The addition bias quandary"
We drown in complexity. Yet we keep adding more.
i released a new blog post discussing that based on scientific research we default to add things when solving problems instead of subtracting things, what it means for us and IT in general. enjoy if you like ... ;)
www.ufried.com/blog/additio...
1 year: It will become undeniable that LLMs write good code 1 year: Weβre finally going to solve sandboxing 1 year: A βChallenger disasterβ for coding agent security 1 year: KΔkΔpΕ parrots will have an outstanding breeding season 3 years: the coding agents Jevons paradox for software engineering will resolve, one way or the other 3 years: Someone will build a new browser using mainly AI-assisted coding and it wonβt even be a surprise 6 years: Typing code by hand will go the way of punch cards
I joined the Oxide and Friends annual predictions podcast episode this week - here are my 1, 3 and 6 year predictions for AI and LLMs (and KΔkΔpΕ parrots) simonwillison.net/2026/Jan/8/l...
"The Human's world ends soon," said the cat.
"Again?" said the dog.
"They are fond of endings and beginnings. Even if nothing changes."
The dog whined.
"Same procedure as last year?" said the cat.
"Please."
The cat lay on the dog's head and purred, muffling the fireworks.
#CrossRepost
Rich Hickey with the best #AI take of 2026 so far - gist.github.com/richhickey/e...
i find this comic strip very reassuring in a strange way ... :)
www.smbc-comics.com/comic/the-co...
i just released the 2nd (and last) blog post discussing the well-known paper "the ironies of automation" and what its findings mean for the current agentic ai automation move (spoiler: some more questions we still need to take care of).
enjoy if you like ... ;)
www.ufried.com/blog/ironies...
I thoroughly recommend reading all of Cory Doctorow's recent speech on AI skepticism, it's crammed with new arguments and interesting new ways of thinking about these problems pluralistic.net/2025/12/05/p...
the recording of my talk "simplify! 10 ways to reduce complexity in software development" from code.talks 2025 is live: www.youtube.com/watch?v=Psx6...
the unabridged slide deck is available at: speakerdeck.com/ufried/simpl...
enjoy if you like ... ;)
Final reminder! If you've got a software architecture practice story we'd love to hear it at ICSA 2026 next summer. Abstracts due this Friday (28/Nov) and submissions (paper or presentation) the following Friday (5/Dec). conf.researchr.org/track/icsa-2...
#icsa2026 #softwarearchitecture
as so often, hobbes nails it β¦ imo, his observation has become even more accurate today β¦
i just released a new blog post (part 1 of 2) discussing the well-known paper "the ironies of automation" and what its findings mean for the current agentic ai automation move (spoiler: quite some questions we still need to find answers for). enjoy if you like ... ;)
www.ufried.com/blog/ironies...
simple observation, often hard to implement: if you want to implement change in your organization, you must be willing to sacrifice the heroes of your current organization.
(not always but) very often they are the preservers of the status quo because change threatens their hero status.
indeed! one of my all-time favorites - so much more raw energy than the default polish mix
in terms of creativeness and how much better a 12" can be compared to the 7" probably one of the best 12" ever made.
the only other ones i know that are getting close are also from ztt, e.g., "machinery (beta mix)" or "beatbox" (where the ending lets you understand everything you have heard before)
otoh, the ai solutions became more powerful since i wrote the blog series which pushed the boundaries a bit. still, demanding custom quirks that do not fit into a higher level abstraction everywhere takes its toll in terms of complexity β and may quickly go beyond the abilities of an ai solution /e
for prototypes, i fully agree.
however, if you build (big) production-ready systems, i think, a few simple prompts in lovable or alike will not do the trick. you will need to specify things in much more detail and chances are that you break the abilities of the ai coding solution. /1
Heute auf der W-JAX: Agile Flow Day β Modern Productivity
OKRs, Lean & Kanban im Fokus β mehr Flow, bessere Zusammenarbeit von Mensch & Technik.
Mit Wolfgang Pleus, Thomas Schissler, Tal Uscher, @felixstein.bsky.social, @hschwentner.bsky.socialΒ & @ufried.bsky.social.
#jaxcon
released a new blog post in the light of the recent aws outage, discussing why blaming aws is exhibiting outdated thinking patterns and what you need to do instead if you want to build reliable systems today: www.ufried.com/blog/it_is_y.... enjoy if you like ... ;)