An article from OpenAI on how they created a complete project without any human-written code.

This is, of course, kind of marketing material for OpenAI, but it also has interesting points:

 code throughput increased, our bottleneck became human QA capacity.

 management is one of the biggest challenges in making agents effective at large and complex tasks. One of the earliest lessons we learned was simple: give Codex a map, not a 1,000-page instruction manual.

 the agent’s point of view, anything it can’t access in-context while running effectively doesn’t exist. Knowledge that lives in Google Docs, chat threads, or people’s heads are not accessible to the system. Repository-local, versioned artifacts (e.g., code, markdown, schemas, executable plans) are all it can see.

And the most important point, in my opinion:

 kind of architecture you usually postpone until you have hundreds of engineers. With coding agents, it’s an early prerequisite: the constraints are what allows speed without decay or architectural drift.
...
In a human-first workflow, these rules might feel pedantic or constraining. With agents, they become multipliers: once encoded, they apply everywhere at once.

In any case, it's an interesting read. Obviously, it's all related to a completely green field project. So, your mileage for decade-old monoliths may vary.

P.S. Also, according to the diagrams in this article, OpenAI uses VictoriaMetrics, which is also cool :)

#ai #programming

Читать полностью…

Apparently, AWS had at least two recent outages due to AI. It was originally reported by Financial Times, but their article is behind a paywall. If you’re subscribed, you can read it here.

Me seeing these news surprisingly coincided with me seeing this post on Reddit: Vibe coders passing responsibility on code reviewers.

And this is kinda true, scary, and reassuring at the same time.

True because it’s indeed very easy these days to generate a lot of code in almost any language.

Scary, because the meme about 5000+ lines PRs with LGTM stands true. While AI code reviewers can quite effectively catch typos and style issues, that humans kinda suck in catching; overly complex logic is usually Ok for them. Thus, we will face more outages in the nearest future, in my opinion.

Reassuring, because it means that those of you who “keep the lights on” are not going anywhere because of AI. In fact, quite the opposite.

#ai

Читать полностью…

​​For those of you, who're into MySQL.

There's an open letter to Oracle to establish a foundation to take care of MySQL.

https://letter.3306-db.org/

You can subscribe to make your voice heard. I would say, it's an important thing to do, because, you know, community matters. Also, it doesn't require much work from your side at this point.

More information is available via that link above.

#databases #mysql

Читать полностью…

From CatOps with love: a new issue of our newsletter is here!

https://newsletter.catops.dev/p/catops-digest-2026-02-14

#digest #newsletter

Читать полностью…

Some results of a fun testing of different LLMs to generate Terraform code.

This article is old, but they have updated the results in mid 2025. Anyways, keep in mind that since then, LLMs evolved. So, even those results are not quite correct anymore.

Still, it’s an interesting test that you can also do yourself. Another point is that LLMs are already quite usable to generate Terraform code.

#terraform #ai

Читать полностью…

A Friday read for y’all.

A collection of AI slop reports security reports to the curl project.

This eventually forced the curl team to halt their bug bounty program on Hackerone.

Here’s also a FOSDEM talk by Daniel Stenberg - the creator of curl - on how to survive the avalanche of AI generated code.

#ai #slides #fosdem

Читать полностью…

​​For today’s Donations Monday, let’s help our friends from DevOps 01 chat to buy an EcoFlow for 154s Separate Mechanized Brigade.

https://send.monobank.ua/jar/5fYjQVfvFA

There’s just a small push left!

#donations #Ukraine

Читать полностью…

The first newsletter of this year is live!

https://newsletter.catops.dev/p/catops-digest-2026-01-30

#newsletter #digest

Читать полностью…

I know that the last thing you'd like to see on Wednesday is yet another remote code execution possibility in Kubernetes, but here you are.

Kubernetes Remote Code Execution Via Nodes/Proxy GETPermission

and here's a lab for that.

tl;dr: web sockets use GET to initiate a connection and then upgrade it, but the permissions are only checked for GET, regardless of what you send through that web socket later. Thus, read permissions are enough to run some code.

P.S. This news came from the chat. If you want to join our chat (in Ukrainian), you can use this link.

#kubernetes #security

Читать полностью…

Unfortunately, kubectl flame tool for profiling in Kubernetes wasn't updated in 4 years. It cannot even run on ARM-based machines.

But what if you need to profile something in your systems? You can use continuous profiling, if it's available in your observability stack.

Or you can use kubectl prof to do some ad-hoc profiles.

- Tool on GitHub
- Medium post

#kubernetes #performance

Читать полностью…

Wanna become a true Terraform SLOPerator?

Here is a carefully vibecoded solution by Anton Babenko. I can confirm that he checks the docs at least once during his Claude conversations, so you can be confident in the quality :)

Jokes aside, this is a cool Skill for Claude Code, which currently works better than any other official or popular alternative out there.

#terraform #ai #claude

Читать полностью…

“How much memory does a Kubernetes node use without the Kubernetes layer”? This is exactly the question From RSS to WSS: Navigating the Depths of Kubernetes Memory Metrics tries to figure out.

And the answer to this question might be harder to get to, as it seems at the first glance.

#kubernetes #systems

Читать полностью…

I found a young blog that has some potential. There are two articles so far:

- Frameworks for understanding databases
- Sorted string tables (SST) from first principles

If you've read "Designing Data-Intensive Applications" by Martin Kleppmann and "Database Internals" by Alex Petrov, you may find these articles repeating information from those books. However, unless you actively work on building databases, you may easily forget this information.

So, such articles serve as a great reminder. I enjoy getting back to such "low level" details from time to time. These details help one to better understand the tradeoffs of the end solution, in my opinion.

#databases

Читать полностью…

I think, this could be a good Friday read: "When Change Outruns Us" is a tale about sustained progress.


The main point of this article is that smart companies do not push for "constant change for the sake of change", but rather adopt a more cyclic pace, when the periods of extensive work are followed by more relaxed times.

This article is particularly interesting to me, because I've just finished listening to the "Slow Productivity" book by Cal Newport. One of the principles, outlined in that book, is that one should work in their natural pace. However, a constant run is no one's natural pace. Another observation in that book, is that starting from the second half of the XX century, managers started to approximate work by "business", i.e. if you look busy, you do some work, even if in the reality, there are zero outcomes.

Many tech companies like to claim that they are "outcomes-oriented" or "value impact", but in my experience, "business" is still the approximation for work. Especially, once a company growth beyond the size, when everyone naturally knows everyone, as well as what they are doing.

#culture #mgmt

Читать полностью…

Starting a new year with a postmortem, eh?

There was a prolonged incident with Kafka at Honeycomb last month. Here you can find a preliminary postmortem for this incident.

"Preliminary" means that there is no root cause analysis yet, but there's already the timeline and the remediation steps.

#postmortem

Читать полностью…

For today's donations Monday, I'd like to share once again the standing Monobank jar for FPV equipment.

This jar is for the unit in which a guy from my wife's hometown serves.

https://send.monobank.ua/jar/4WLw91UqFe

#donations #Monday

Читать полностью…

Collaboration sucks is a nice Friday evening read about the ways we work together.

I think, this article has interesting thoughts, but as usual, you need to use your own judgement to understand the environment you’re in.

For example:

You’re the driver” is a key value for us at PostHog. We aim to hire people who are great at their jobs and get out of their way. No deadlines, minimal coordination, and no managers telling you what to do.
In return, we ask for extraordinarily high ownership and the ability to get a lot done by _yourself._ Marketers ship code, salespeople answer technical questions without backup, and product engineers work across the stack

This works great until end up with the codebase that has a unique flavor of the same wheels at every corner. Sure, there are ways of dealing with that, but you have to have those constraints beforehand.

However, the idea of limiting your collaboration and inviting only the relevant people into the decision making process, makes total sense. If your company growths, at some point it will grow beyond the point a single person can understand every aspect of your system. When it happens, sharing proposals to everyone wouldn’t, indeed, improve your collaboration and the team spirit; it would just generate noise. And when there is too much noise, it’s easy to lose important signals.

#culture

Читать полностью…

​​Support a friend of mine on the Frontline!

Last year, she chose the tough path: Combat Medic.
Now, she needs our help to secure critical medical supplies that can't wait for paperwork.

No donation is too small. Let’s help her save lives!

- Mono Jar: https://send.monobank.ua/jar/75jQXw6aYq
- Mono: 💳: 4874100025644306
- Privat: 💳: 5168745027810065

#donations #Ukraine

Читать полностью…

Continuing the topic of Terraform, here's an article from a friend of mine on how to keep the versions of Terraform binaries, modules, and providers in check.


This article was already featured in Anton's newsletter, but it won't hurt to re-iterate. If you're into Terraform, make sure to subscribe, tho.

P.S. If you're hiring in DE, CH, LU, DK, or remote; he has his CV on his blog. You know what to do 😉

#terraform

Читать полностью…

Two bundles on Humble Bundle:

- Linux for Seasoned Admins by O’Reilly. This is a reoccurring bundle, so check if you have it already before buying!
- Networking bundle by Pact. This is a video bundle to prepare for various certification exams.

#books #bundle

Читать полностью…

Hello Kubernetes Community,

Multiple issues are disclosed today in ingress-nginx, and assigned the following CVE IDs: CVE-2026-1580, CVE-2026-24512, CVE-2026-24513, CVE-2026-24514.

The most serious of these issues have been rated HIGH (CVSS calculator, score: 8.8).

https://groups.google.com/a/kubernetes.io/g/dev/c/9RYJrB8e8ts?pli=1

Читать полностью…

A book bundle for Solutions Architect exam preparations from Packt.

Packt didn’t have the best reputation, but the topic may be interesting to many people in this channel.

#books

Читать полностью…

Some time ago, I posted here an article from a well-known company on how they use Terraform.

When I was reading that article, I had a thought: “C’mon, I also can write crap like that!”.

So I did!

I hope you like it!

#terraform #oc

Читать полностью…

A book bundle for exam and interview preparations from Manning press.

I'm not sure how good are those books outside the context of interviews, but Manning books usually considered good.

#books

Читать полностью…

Bring Back Ops Pride is a new article by Charity Majors on how it comes that the operational work is often seen as of lower importance, and why is it bad.

This is her answer to the comments under her another article “You Had One Job”: Why Twenty Years of DevOps Has Failed to Do it. This article has some interesting ideas, but it's a marketing material, so beware.

#ops #culture

Читать полностью…

For today's donations Monday, I'd like to share once again the standing Monobank jar for FPV equipment.

This jar is for the unit in which a guy from my wife's hometown serves.

https://send.monobank.ua/jar/4WLw91UqFe

#donations #Monday

Читать полностью…

Another Friday read on the Culture debt.

The core idea behind it is the same as for the technical debt, but this time it’s about the culture. As company growths, relationships within it inevitable change. This is silly to ignore these changes. Yet, if nothing is done, the culture can drift away, and then it’s much harder to fix, than refactoring a couple of services.

Also, this line strikes hard, when talking about the symptoms of the culture debt: “What you reward diverges from what you say you value.”

People are quite good in calling bullshit on someone or something. It’s often quite obvious when proclaimed values are just empty slogans. This erodes trust as nothing else.

#culture

Читать полностью…

A topic on Reddit that argues for a new term - Claude Hole. This is when AI is tasked with fixing an issue, but you actually end up further away from the fix after the AI changes.

This reminded me of a completely unrelated article - I Was Kidnapped by Deutsche Bahn and All I Got Was 1.50 EUR - in that story, the author also ended up further away from their destination than at the beginning of their journey.

Regardless of your views on AI, distinguishing good from bad becomes more and more valuable these days.

#ai

Читать полностью…

Our job is all about tradeoffs.

This article describes tradeoffs of database indices.

#databases

Читать полностью…

​​I'm back!

It always feels nice to start a new year from scratch. Unfortunately, it's often not the case, and we have to finish things that remained.

Today's fundraiser is one of those things: let's help a friend of mine to raise funds for a pickup truck for the Zaporizhzhia front lines:

https://send.monobank.ua/jar/5mSFtTYUFt

#donations #Ukraine

Читать полностью…