faced an interesting situation: had to restart journald to change some settings, which triggered (code=killed, signal=PIPE) for all Golang services on this VM. they were configured to "Restart: on-failure" so they never restarted since SIGPIPE is not considered a failure 🤦♂️
This is actually insane but I think this is the future. Instead of 1 product and 5 devs in a team, the chances are we will have 2-3 products and 1 dev, and the dev will be building and maintaining AI pipeline and maybe fixing complex issues / helping with big features.
we live in amazing world
I built a simple game for my son
he kept coming to me for new features, with the energy of a nine years. it was impossible to keep up
so I built a small app where he could say what he wants, and then AI builds it, redeploys the game, voila!
And he has a ton of fun. He already made >20 new levels. Every level has its own unique mechanics, enemy types, etc.
There are 2 mini-games inside, one is 3D basketball and one is car racing. He added achievement system, game shop, cheat codes, etc.
@uninen yep, I did. and it did get slightly better, but still a lot of mistakes. I think it just a combination of complex logic and +1 level of abstraction (i.e. not working with the data directly but working via audit log) is messing up everything :)
Interesting: there's one service in my codebase where AI (both Gemini 3 Flash and Claude Opus 4.6) feels utterly confused every time.
The service calculates stats based on audit log.
This seems to be one of the gaps where AI is currently not very good.
one problem people face when using nginx as load balancer is how to pass real client IP address to the backend servers
nginx supports ip transparency but network setup is complex
simpler way: use proxy_protocol between load balancer nginx and backend nginx!
not sure how much longer I am going to stay on Azure.
there was a perfectly working free/cheap feature - now it is either working much worse or discontinued.
happened with several features already, which makes me think it gonna happen with the rest as well…
Big day, ts2c 3.0.0 is published after 7 months of development! 🎉
Main changes:
- moved to use a much faster parser 💨
- multiple .c and .h files can be emited ✨
- a lot of smaller improvements and bugfixes 🛠️
https://t.co/hjMoXNNkFl
Did you know you can analyse your #nginx configuration for vulnerabilities?
nginx.conf is tricky. And defaults aren’t always very good.
https://t.co/KWmNrXVNv3