Links

Senior engineering practitioners from major technology companies gathered for a multi-day retreat to confront the questions that matter most as AI transforms software development. The discussions covered more than twenty topics across breakout sessions, but the most significant insights didn’t emerge from one single session. Instead, they surfaced at various intersections; we found that the same concerns kept appearing in different conversations, framed by different people solving different problems. This publication synthesizes those cross-cutting themes, organized around the patterns that senior leaders need to understand and act on now. The retreat did not produce a single, unified vision of the future, but instead produced something more useful: a map of the fault lines where current practices are breaking and new ones are forming. ...

Someday years from now we will look back on the era when we were the last generation to code by hand. We’ll laugh and explain to our grandkids how silly it was that we typed out JavaScript syntax with our fingers. But secretly we’ll miss it. We’ll miss the feeling of holding code in our hands and molding it like clay in the caress of a master sculptor. We’ll miss the sleepless wrangling of some odd bug that eventually relents to the debugger at 2 AM. We’ll miss creating something we feel proud of, something true and right and good. We’ll miss the satisfaction of the artist’s signature at the bottom of the oil painting, the GitHub repo saying “I made this.” ...

“Archivio Grafica Italiana is the first online archive dedicated to the entire Italian graphic design heritage.” Beautiful resource. Some samples came as a true surprise to me, like the New York City Subway signage, though the Italian connection is a bit weak on that one. (via)

The actual phrase ‘Dark Ages’ itself derives from the Latin saeculum obscurum, which Caesar Baronius – a cardinal and Church historian – came up with around 1602. He applied the term exclusively to the tenth and eleventh centuries. However, and very significantly in his use of the term, Baronius was not decrying a state of scientific malaise, or a particularly turbulent political period – he’s talking about a lack of sources surviving from that time. Indeed, Baronius sees the cut off point for the dark ages to be the Gregorian reforms of 1046, following which we see a massive increase in surviving documentation. ...

Sam over at theTangentSpace has the perfect analysis on Europe’s sorry situation in these troubled times, so much so that I have a hard time picking just one or two paragraphs to quote here. Let’s just go with the opening: Europe must increasingly prepare for a world in which the protection of America is replaced by protection from America. An essential component of this is moving away from dependence on US goods and services and, perhaps most essential of all, US tech and tech infrastructure. ...

Writing forces clarity. When I explain a concept to others - in a doc, a talk, a code review comment, even just chatting with AI - I discover the gaps in my own understanding. The act of making something legible to someone else makes it more legible to me. – Addy Osmani in 21 Lessons From 14 Years at Google The one quoted above is #12, and I’ve been religiously abiding by it for a long time, but all 21 are well worth reading. If you’ve been in software engineering long enough, they’ll resonate with you. Also, most lessons apply to all kinds of career paths, not just software. ...

As AI generated content becomes the norm, I believe that human-generated content and raw thoughts and emotion will become more valuable. In many ways, I’d rather read a raw, unproduced, and scrappy blog post with grammatical mistakes over perfectly generated content that serves little value. – Armeet Singh Jatyani, Importance of Writing

Every machine serves a purpose. People need purpose. The temptation to become the machine is higher than ever. The promise of the machine is alluring. If I can just keep chugging forward, I will end up somewhere that is not here. If I can turn myself into a mechanism that takes input and consistently works towards some goal, I will make it. [..] You’re not a machine. You’re a person. Play to your strengths. Be sharp and strategic like a scalpel, not blunt like a mallet. Stop fetishizing the grind. Dream bigger. ...

When I’m writing, I write. When I’m cooking, I cook. When I’m talking to someone, I put my phone away. The constant mental juggling that felt necessary before now feels exhausting. There’s something meditative about giving your full attention to a single task. – 47nil

AI can replace most of programming, but programming isn’t the job. Programming is a task. It’s one of many things you do as part of your work. But if you’re a software engineer, your actual job is more than typing code into an editor. The mistake people make is conflating the task with the role. It’s like saying calculators replaced accountants. Calculators automated arithmetic, but arithmetic was never the job. The job was understanding financials, advising clients, making judgment calls, etc. The calculator just made accountants faster at the mechanical part. AI is doing something similar for us. ...