Recently, a client told me that the code I had written to sync their systems and a new datasource blew up their AWS EC2 instances. Apparently, the synchronisation engine kept getting killed for using up too much memory. More than a few gigabytes, actually. To sync a few tens of
Sometimes, opting for sensible defaults seems obvious. Yet, sometimes, the default and most obvious option isn't the most sensible.
I have, as a teenager, fiddled around with phpMyAdmin when fooling around with WordPress and OGSpy, back when OGSTeam still relied on SVN for versioning, and I didn't know crap about development, let alone architecture.
A simple way to print any and all errors in Nest.js, for people who aren't experienced with it.
Sometimes, the smallest things take up quite a bit of time. This time, it was a simple serialisation issue.
You have a TypeORM entity. It has a relationship. The relationship entity has a nested relationship to a third. And you need that third entity to save the world and crack the bank vault open. How the hell do we get it?
Optimize your mobile app's performances and run "big" and "complex" queries in NoSQL, using CQRS & Serverless! (in our case, Firestore & Firebase Cloud Functions)