A Java Geek weekly 119

Structured error messages for HTTP APIs

I’ve been trying to improve my knowledge and understanding of HTTP APIs. For this, I’m reading and watching the following sources:

  • Books. At the moment, I’m finishing API Design Patterns. Expect a review soon.
  • YouTube. I’d recommend ErikWilde' channel. While some videos are better than others, they all focus on APIs.
  • IETF RFCs. Most RFCs are not about APIs, but a friendly person compiled a list of the ones who are.

Today, I’d like to introduce the "Problem Details for HTTP APIs" RFC, aka, RFC 7807.

Martin Fowler’s boardgame-related blog posts

I knew that Martin Fowler was a boardgame player, but I just realized he also blogged about his experience. I have to admit that I’m not that committed.

Ukraine Alarm integration with HomeAssistant

So sad and so cool at the same time. I hope it helps.

21 Lessons From 14 Years at Google
  1. The best engineers are obsessed with solving user problems.
  2. Being right is cheap. Getting to right together is the real work.
  3. Bias towards action. Ship. You can edit a bad page, but you can’t edit a blank one.
  4. Clarity is seniority. Cleverness is overhead.
  5. Novelty is a loan you repay in outages, hiring, and cognitive overhead.
  6. Your code doesn’t advocate for you. People do.
  7. The best code is the code you never had to write.
  8. At scale, even your bugs have users.
  9. Most "slow" teams are actually misaligned teams.
  10. Focus on what you can control. Ignore what you can’t.
  11. Abstractions don’t remove complexity. They move it to the day you’re on call.
  12. Writing forces clarity. The fastest way to learn something better is to try teaching it.
  13. The work that makes other work possible is priceless - and invisible.
  14. If you win every debate, you’re probably accumulating silent resistance.
  15. When a measure becomes a target, it stops measuring.
  16. Admitting what you don’t know creates more safety than pretending you do.
  17. Your network outlasts every job you’ll ever have.
  18. Most performance wins come from removing work, not adding cleverness.
  19. Process exists to reduce uncertainty, not to create paper trails.
  20. Eventually, time becomes worth more than money. Act accordingly.
  21. There are no shortcuts, but there is compounding.
European alternatives for digital products

I wanted to write a blog post, but there’s already an existing site. The Cloud Computing section is quite nice.

Bun Introduces Built-in Database Clients and Zero-Config Frontend Development

I’m using Bun for the JavaScript module of my side project, a Kotlin Multiplatform project. I’m quite happy so far.

Claude Code on the go

Geekery on another level. It gives me ideas.

Stop Forwarding Errors, Start Designing Them

Interesting post on the core of error management: transient vs. permanent, and how to make them useful to people who are reading them.

Docker Kanvas Challenges Helm and Kustomize for Kubernetes Dominance

TIL.

Web development is fun again

I did CSS, the first version, when nobody did. I did DHTML when nobody did. But web development somehow became more and more complex, and every time I had to develop a UI without Vaadin, I felt like I had to learn an entirely new approach again. For me, it’s less about making it fun, than making it possible without spending weeks to learn again. Like the author, I think I have the foundations; I missed the implementation details.

Shutdown Signals with Docker Entrypoint Scripts

I knew about the shell vs. exec form of ENTRYPOINT, but I learned about the exec instruction in the delegated shell script.

How Github monopoly is destroying the open source ecosystem

Monopoly is bad, and still, here we are. I have both a GitHub and a GitLab account, to prepare for the time when GitHub’s monopoly will break.

Codeberg

Codeberg is a non-profit, community-led effort that provides Git hosting and other services for free and open source projects.

Other services include a Codeberg Pages, i.e., static site hosting.

Nicolas Fränkel

Nicolas Fränkel

Nicolas Fränkel is a technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

Read More
A Java Geek weekly 119
Share this