notadoctor_ssh

I usually have the Lo-fi beats playlist[1] on Spotify playing.

[1] https://open.spotify.com/playlist/37i9dQZF1DWWQRwui0ExPn?si=...

I am planning to do this for my hobby projects. I think it will help me write better code and also learn a few things. For professional projects, I think the time I will try to add stuff but it relies on my manager's approval.

I recently started doing this. My project involved using three different services, where one of them was internal. I only had API documentation for these services and because of many reasons, there was a delay in obtaining the API keys required and I was stuck on testing my code. That's when I decided to write unit tests and mock these services wherever I am using and started testing my code. There were zero bugs in these integrations later.

While doing this I also found one more benefit, at least for my use case. The backend for user login was simple when I started, but it started growing in a few weeks. Writing test cases saved me from manually logging in with each use case, testing some functionality, then logging out and repeating with other use cases.

Not sure if it is a practical benefit or not, but writing test cases initially also helped me rewrite the way I was configuring Redis for a custom module so that the module can be tested better.

My only issue is that it takes time, and selling higher-ups this was kind of difficult.

Hey, would love to chat on this. Can you share your email?

I would like to add web servers like nginx to your list.

Apart from this, I would ask you to concentrate more on the concepts than the tools that you have chosen. Like you can use tools Django has to build an API server but concentrate more on finding out more about the life cycle of the request that hits the API server.

I think this is the best advice in the thread so far.

Any more details on how you got that First job? Was it an MNC or a startup? Were you already working for it in India?