To me, LinkedIn was supposed to be the professional network — a place for thoughtful discussion about work related stuff and genuine connection. Yet, over the years, it feels that the content and tone has shifted for engagement (“what do you think?”, “how do you do it?”), self glorification (“especially after quitting a company and highlighting all the successes” srsly, if it was so cool, why did they quit?) and provocative extremes. Everything for the reach.
(more…)-
Reproducible Vibe Coding | It’s all About Context
Actually I wanted to try a bit GithubCopilot with
Agents.md. Yet .. I think during the project I totally forgot to test the influence of the Agents file but tried “vibeCoding” in a reproducible way.I had a very little project in mind that authenticates to Mastodon, fetches some data, saves into a database and displays some metrics on a web page in basic charts. Nothing overly fancy, but also some stuff that would simply take some time when coding “alone”. Like proper OAUTH flow, paging through mastodon apis, rate limiting, database writing, database setup script and cleanup. Some Javascript for the chart, etc.
But I thought it might be nice to try with GithubCopilot (GHC). But I’m also a big fan of reproducible results. So … step by step, what did I do.
(more…) -
Recommended read: What Actually Makes You Senior
On Mastodon, I just found a link to the Terrible Software Blog. (Definitely a blog to follow, I just added it to my RSS reader).
I found this article pretty good: What Actually Makes You Senior.
But if you strip away the title, the salary, and the years of experience, there’s one core skill that separates senior+ engineers from everyone else: reducing ambiguity. Everything else flows from that.
Matheus LimaIt’s about the ability to handly fuzzyness and derisking projects. I really like the “they first make the problem clear. Then, and only then, they go to solve it.”
Check it out: https://terriblesoftware.org/2025/11/25/what-actually-makes-you-senior/
-
I Changed the Fediverse Handler to @fgraf
When I started the Fediverse integration of the blog, I just made a default handler for the full blog and called it
@blog@www.locked.de. Yet, the more I use the blog for the fediverse, the less this made sense to me as it felt too impersonal.While I could switch the setting to allow profiles for both, users and the blog itself — which would introduce a completely new user … I also could stop overthinking it.
TL;DR: this profile is renamed to @fgraf.
The IT Blog@fgraf@www.locked.deIT, Tech, Data, …
248 posts53 followersAnd if you are not yet on the Fediverse, I would recommend giving it a try. ;-)
-
How to write great agents.md(s) – A recommendation from GitHub
GitHub’s new guide, How to write a great agents.md: Lessons from over 2,500 repositories, pulls lessons from over 2,500 repositories to show how to document AI agents effectively. It’s not just about clarity but also about making collaboration, reproducibility, and scalability possible.
The guide breaks down how to structure
agents.mdfiles for real-world utility. It highlights common mistakes and explains why solid documentation is the backbone of any successful AI project. Whether you’re a developer, DevOps engineer, or just curious about AI tooling, this is a practical roadmap.For anyone serious about AI development, this is a resource worth keeping: https://github.blog/ai-and-ml/github-copilot/how-to-write-a-great-agents-md-lessons-from-over-2500-repositories/
-
Recommended Read about a Microservices Reality Check
Docker’s recent article “Do You Really Need Microservices?” delivers a good dose of pragmatism with regards to Microservices. The article doesn’t dismiss microservices outright— it acknowledges their value at massive scale — but it also hightlights an uncomfortable truth: most teams simply don’t operate at that scale.
What I particularly like are the warnings about hidden costs, the kind that reveal themselves after committing to the architecture and having to operati it over years and through a lot of releases. Operational overhead, debugging “fun” and the complexity of managing distributed systems aren’t just footnotes — they’re a true burden for teams without the resources to handle them properly.
Check it out: You Want Microservices—But Do You Need Them? | Docker
Fediverse reactions
-
-
Your Backup Plan Is Incomplete Without Restore Tests
Backups should be routine not only for folks in the IT. If you’re reading this you probably already have SOME backup process in place. Ideally automatically or with a scheduled reminder.
But doing backups regularly is just half the story …
(more…)Fediverse reactions
-
-
Ever Wondered What Would Happen If You Lost Your Account?
Paris Buttfield-Addison, a developer and long-time Apple user, recently lost permanent access to his Apple ID. And he didn’t even do anything wrong. The result: 20 years of photos, messages and data? Gone. A true worst case scenario! But let’s have a look, should we learn something from that?
(more…)Fediverse reactions
-
-
The Cost of Going All-In on AI
On Mastodon, I just came across “I Went All-In on AI. The MIT Study Is Right.” from Josh Anderson. He spent three months building a product using only AI-generated code. The result? A working product, but also a dangerous realization: He no longer fully understood his own creation. When a small change was needed, he hesitated.
(more…) -
LLM Update in Production: When Prompts Fail — and What It Means for Your Applications
t3n recently wrote that OpenAI’s GPT 5.1 update might come with a surprise to desktop users: previously reliable prompts no longer behave as expected. While this may be just a minor annoyance in day-to-day chat interactions, think about what that means in production environments.
(more…)
