lifeofperfect

I once worked with a senior backend engineer who believed that the strongest backend systems were the ones where logic is written more on the database layer than on the code layer. The normal if-else statement you would write to check a users balance, bro writes all that logic directly on the DB, there were triggers, database functions etc. Bro was literally coding with SQL. At that point I didn’t know SQL could even do all that. Bro would review my code then and ask me why was I writing all that logic in code when it could reside directly on the db😂. This was way before AI and bro would prefer to write every single thing by hand rather than install a package, he felt they were not secure. Bro uses a framework just to repurpose it and customize everything! At The point working with bro, he was almost 40. Man! I’ve worked with cracked devs, and I’m grateful for every experience that has shaped me.

too much idea want to finish you people on this twitter. some people are writing their business logic in their dBs 😂 how do you handle horizontal scaling, sharding and replication? how do you ensure a highly available system if your business logic is tightly coupled-

Make talent apply

🚨: The world's richest women, Alice Walton, created a 100% free medical school for underprivileged students.

JUST IN: Apple and Intel $INTC reach agreement for Intel to make chips in Apple devices, WSJ reports.

One fatal cultural flaw of ours is the collective inability to appreciate how politics at every level impacts on the most minute detail of your everyday personal life forever. E.g there’s an invisible yet straight line between your government and your height/dentition/genes, etc.

Your registration endpoint shouldn’t leave orphaned users in the database when the welcome email fails to send. The problem: user creation lives in PostgreSQL. Email sending lives in an external service. You can’t wrap both in a single database transaction. The fix: if the email fails, delete the user and their invitation. This is the SAGA pattern. When a multi-system operation fails partway through, you compensate by undoing the completed steps. Built this today in Go with Resend for email delivery and PostgreSQL transactions for the rollback.

Your registration endpoint shouldn’t leave orphaned users in the database when the welcome email fails to send. The problem: user creation lives in PostgreSQL. Email sending lives in an external service. You can’t wrap both in a single database transaction. The fix: if the email fails, delete the user and their invitation. This is the SAGA pattern. When a multi-system operation fails partway through, you compensate by undoing the completed steps. Built this today in Go with Resend for email delivery and PostgreSQL transactions for the rollback.