Operations | Monitoring | ITSM | DevOps | Cloud

I spend a good amount of my time deploying Aiven services for demos and examples. Traditionally the tools I reach for are: If I’m writing a program, I may also look to the Aiven API, perhaps using curl at the command line or in a shell script, or perhaps with direct HTTP requests in a Python program. The API is how the console and the CLI tool talk to Aiven, but I generally find that too low level to be comfortable, and I always have to look up how to pass in the Aiven user token.

CloudZero now breaks out Snowflake Cortex spend on its own, so the AI usage buried in your Snowflake bill becomes a line item you can track and allocate before it ramps into a surprise.

"Every website was once designed for people. That assumption is beginning to change." For nearly three decades, the internet has worked in a predictable way. Whenever we wanted to know something, we searched for it, clicked through a few websites, compared information, and made a decision. Whether it was buying a new phone, planning a vacation, or researching software for work, businesses knew exactly how people behaved online.

There is a question a lot of engineering leaders are quietly sitting with right now: we have rolled out AI tools across the team, the developers seem faster, so why isn't more software actually shipping? It is a reasonable thing to consider. Pull requests are opening faster. Lines of code per sprint are up. The boilerplate that used to take full afternoons now takes minutes. By every local measure, the investment is paying off.