save 30% on the bill, and make an argument that with agentic engineering tailored but standards-compliant software becomes plausible and unlocks advanced cost optimization opportunities.

Like plumbing - I need water, I need it clean and I need it not to break. Good plumbing stands on a lot of science - material, physics, but the plumbing itself is just about solving a problem of delivering water from a to b.

Software, on the other hand, is a means to an end. I don't really care if it's the result of religious catharsis of the author, as long as I know it solves the problem and is of sufficient quality.

It's a literal lose-lose of document formats.

Self-contained HTML like EPUB is so much better.

In other words, an issue is fine if it comes with no expectations. For expectations, on the other hand, a PR or an offer to pay is a better fit.

True, but I doubt the issue's author is just a good Samaritan, created it, immediately forgot and has no expectations.

If I'd be guessing, it's more likely that their security scanner instead of improving quality has added "AI" that automatically creates issues with the source projects.

In addition, you can also point them to the line 20 of the license (github.com/FiloSottile/...) which says 'THIS SOFTWARE IS PROVIDED ... "AS IS" '

I'm permanently fascinated with people who receive something for free and still expect a paid-quality customer service.

The three aspects are in the end about cost efficiency. A #cloudnative solution should cost nothing when it's not bringing value and when it does, it should maximise the cost to value ratio. Cloud's added value is not technological, but in added business efficiency.

#cloud #cloudarchitecture #architecture #antifascism #music

In this post, as usual, there's great (but not necessarily easy) music, political madness and hope and I will be embarking on a cloud architectural adventure in the world of blogging.

Kafka, etc) but that would require a new project. I cannot claim your land if I rebuild your house.

the engineering practices, not just software.

but we keep forgetting that the code was, somewhat surprisingly, only a small part (20% is my guess) of the software engineering. Experienced developers have seen this way before the LLMs - they would spend more time thinking about the implementation than writing code for it. It's time we talk about

It all starts to remind me of the pandemic-forced switch to remote work. Some teams flourished, many struggled. Imo the key was accepting that it's not "same work, just a different chair" but a completely different way of approaching work.
Same here. Yes we can churn much more code, much faster

After discovering starship.rs I'm happy not to have to manage my prompt by hand.

I would go further - the cheapest cloud resource is the one you switched off. Design your workloads so that their components exist and run only when absolutely necessary.

(K8s is a good tool, but its use has to be justified)

dot-com was the creation of Ajax and the birth of web 2.0.