Tech – 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.

friends with my imposter syndrome”. She shared the lessons learnt and how she manages her own professional development.

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

Imposter syndrome is a well-written topic. Being a fairly confident person, I was not sure whether I had imposter syndrome a year into my professional programming career. In fact, I realised that this illustration by Gemma Correll “Am I even good enough to have imposter syndrome?” spoke to me well.

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

A follow up on Pull Requests

Notes on Logging

Some observations on preference for Pull Requests

AWS Launch Template and Auto Scaling Group Gotchas

“How I made friends with my imposter syndrome”

Initialise a Kotlin Spring Boot project with Postgres

Kotlin Spring Boot: Tech Notes

How I overcame imposter syndrome after a year in software development

Caching JWT Verification (and an anti-pattern)