Backend Engineering

“I believe clarity beats motivation, ownership beats blame, and every hard idea has a simple analogy.”
Senior software engineer by profession
An optimizer by obsession
An entrepreneur at heart
I used to edit .java & .js files for a living. Now I just type in a terminal and things happen.
Along the way, I build things and write down what I learn. You'll meet both as we go.
Stay close. Watch me build, fail, iterate & win, all in public.
When I learn something deeply, I try to write it simply.
Fewer words, sharper thoughts, and something that stays with you.
Here,
catch.
This is a space where I write my thoughts out from the things that I learn, understand and experience in day-to-day life. It's an effort to document original thoughts that arise at certain phases of my life, which might be beneficial to anyone in the pursuit of the same. Happy learning!
As a Backend engineer, one of the important parameters to validate the work is the number of ms at which the API returns the required resource.
Focus only on the resources that the client needs as a response. Move everything else to async to reduce response time. Use messaging brokers like Kafka for multi-service processing. In Spring, use @EnableAsync and @Async for asynchronous tasks.
Learning to build an application from tutorials/clones ~ Learning to drive a bicycle

Here goes the final episode of our podcast.

There was a guy, observing work done by 2 men on the agricultural field.





