Rock and Null

For most of the history of software, we've adapted ourselves to the software.

For decades, we optimized code for humans.

For decades, software engineering has been built around one core assumption: the same input should always produce the same output.

We are entering a strange communication loop.

We originally built Promies to solve a very specific problem of our own: distributing and managing promo codes for our Android apps.

When we first introduced Pale Blue Spring Admin, it was a bit of a tease.

If you’ve shipped even one mobile app, you’ve probably run into the same problem.

The barrier to shipping software has collapsed.

The hardest part of building a project isn’t always dealing with failure.

Not long ago, junior engineers learned by working closely with more senior ones.

We recently ran into a frustrating production issue: our Spring Boot application using SQLite would occasionally lock up, and the only way to recover was to restart the entire service.

Having spent time as a software engineer in a large tech company and later launching my own company, I’m often asked which experience is “better.”

At Pale Blue, we’ve always admired the magic of Django Admin - that moment when you define your models and instantly get a clean, intuitive interface to browse, search, and manage your data.

Rewriting software is a topic that sparks endless debates among engineers.

The concept of the T-shaped engineer isn't new.