mattrighetti

Every developer has at least once in their career stumbled upon the scenario where a program would not print something as they initially thought.

Recently I’ve been working on a pretty big rust project and to my surprise I couldn’t get tests to work properly.

Consider this scenario: you’re building a website that has a classic navbar at the top, this navbar has a button that reflects the user authentication status, showing a "Profile" button if the user is authenticated and showing a "Login" button in case the…

Playtomic is probably the biggest application for booking tennis/padel courts in Europe.

Anyone who has developed with Rust using sqlx for database operations has likely needed to write tests for their database interactions.

In a previous [0] post I’ve discussed why I ditched sea-query and why sql is almost always the best way to not re-learn something new from the beginning that will inevitably end up slowing you down or simply not working at all in the long run.

Query builders and ORMs have been around for as long as I can remember, each serving different purposes.

Askama implements a template rendering engine based on Jinja.

Lately I’ve been working on Ulry, after tiressly trying to make Next.js work for me, I realised it wasn’t the right fit (I’m not alone).

The other day I working on a side project of mine and I stumbled upon a bug in my code that I couldn’t immediately figure out how to solve.