Technical – i.dance::in.between

A year ago, I wrote a blog post “Some observations on preference for Pull Request”, with my clear preference against pull-requests (PR)-based coding practice. Fast forward a year, I am at a company practising exactly this, and here I note down some initial thoughts.

Several mini learnings on logging.

An attempt to understand the psychological “safety net” that Pull Requests brings, and ponderings on whether such mentality would still hold in a successful Trunk-based development environment.

We encountered a slightly cryptic error when trying to use Launch Template with Auto Scaling Group (ASG) to launch EC2 instances into a VPC. And a couple more gotchas when fixing the error.

Because setting up a brand new project is rare and thus could be hard, and this is my template.

Notes from a Kotlin Spring Boot API toy project

TIL: “it is not advisable to cache error responses without considerable thought on the adverse implications” – Apigee

Accidentally upgraded to npm 7 at runtime? Here’s how to undo it.

Should a DELETE endpoint respond with 204 or 404 when the resource requested for deletion does not already exist?

A follow up on Pull Requests

Notes on Logging

Some observations on preference for Pull Requests

AWS Launch Template and Auto Scaling Group Gotchas

Initialise a Kotlin Spring Boot project with Postgres

Kotlin Spring Boot: Tech Notes

Caching JWT Verification (and an anti-pattern)

How to use node with npm 6 not npm 7

‘DELETE’ endpoint and idempotency