As a professional programmer, I've been raised on a JVM diet of Java and, more recently, Kotlin. So, statically typed languages. Such languages have great characteristics, code navigation with an IDE is implemented well, refactor tooling is also powerful. Many errors are caught at compile time and the
I think the biggest pitfall with programming paradigms is not picking the "wrong" one – they all have their place – but using a paradigm in a wrong way. It's a problem I've had myself and that I've seen others have too. Now, there
So, in my last blogpost I wrote about business rule validation in a RESTful API. Check that post out if you haven't done so already, I think it's a good one. If you explore the repo mentioned in that blogpost, you can also see the tests
When trying to perform an action – especially one that changes the state of the system – in an API the request often needs to be validated. The question is, what validation should happen where? The DB can help with enforcing certain rules (existence, uniqueness, etc.), but not all. Some of the
Methodical creation of pressure sources can push you in the right direction and help you achieve your objective. You have to be careful though, too much pressure can be a bad thing and cause unnecessary stress and bad feelings.