I'm a big supporter of "everyone can do whatever they want with their lives" but it reinforces the notion that people without commitments that can spend their time outside of works doing AI/leetcode/YT videos are better rewarded than people with a busy life.
> client-s3: Added support for annotations. You can now attach up to 1000 annotations directly to objects and create, retrieve, list, and delete them using new annotation APIs.
S3 has tags, metadata, and now annotations?
https://t.co/0zUxQmVHKn
True story, I was nominated for employee of the quarter for saving our company millions of dollars a month for rearchitecting a complicated legacy app
But they gave the award to a girl in HR because “she shows up every day with a smile on her face”
I find TypeScript works well with AI coding agents. I just released a TypeScript book "Practical TypeScript Artificial Intelligence Programming" that can be read for free online: https://t.co/b0dOQAUcGH Enjoy! In the past I only used JavaScript or TypeScript when I had to but this year I have been enjoying TypeScript and have started using it for some projects.
From T-shaped to M-shaped architect.
AI lowers the barrier to code but raises the bar on building the right thing.
The GOTO episode with Teena & Luca nails it: empathy + elevator skills now matter more than ever.
How is AI changing your role as an architect?
🧵
Linux: Should I use overlay or native filesystem snapshot capabilities for Docker?
Mac/Windows: Should I use one Virtual Machine per container or a shared one for all?
WSL containers ⚡
At #MSBuild, we announced a built-in way to create, run, and interact with Linux containers on Windows.
Watch the demo on demand: https://t.co/NVotUyk1U9
When companies like Meta or Microsoft lay of experienced people or make their lives so miserable that they voluntarily leave, they are unknowingly erasing institutional memory.
Every company's infrastructure is chock full of Chesterton's fences and stays up because of unwritten processes.
The code bases are typically huge, so nobody can understand them end-to-end. When the people that know the history are gone, the only thing the remaining crew can do is fight fires and make cosmetic changes at the edges. Rewriting from scratch is not an option since, as your favorite AI will say, the software has become load bearing for the company's success.
The good news is that I think for green-field code, vibe coding offers a way to avoid this trap by embracing the invariant that all software should be evolvable without any human needing, or even be allowed, to understand the inner workings of it.
Only if you take the human developer completely out of the loop like this, you can ensure that software never atrophies into legacy software.
This may sound radical to AI coding deniers, but the reality is that code inevitably becomes incomprehensible for humans, so the rational solution is to just assume it is like so from the start.
@BrianOConner@GuruPundit@MarioNawfal Maybe first robots kill half the planet population and remaining humans do space exploration and meet aliens.
Then a few thousand years later robots kill half the population across the universe and remaining humans evolve in counciousness with sandworm poo.