I like to trace down things in order.

For example, let say I'm working on an ecommerce system and I try to understand what happens when a buyer adds an item to its cart. I'm going to put logs / debugger's prompts on the important steps of that operation. Next to those, add a comment that describes why this step is important. The important thing is to label the comment with incrementing numbers. Those numbers allow me to keep track of the order of execution.

Finally, commit this to a dummy branch and share it with your co-workers if both of you are new to this code base.

That's one of the first thing I do when I jump in a new codebase. Pick something that interests you, and log the whole operation.

Hey! OP here. It's a tool for people confined home, because of the COVID-19 crisis, to get help from their local community.

Share it with your friends and family, who knows, it might be helpful to someone!

For my fellow developers, it's also open source! https://github.com/zergov/helpaneighbor Feel free to open issues or PRs for translations / new features! !

High BPM music has a huge effect on me.

I have seen myself iterating a lot more during a session where I would listen to trance music instead of 2000s punk rock.

Is it the smaller amount of lyrics? I don't know, but I'm convinced I have observed a higher productivity when listening to high bpm music in the past 5 years.

Agreed, though the effects can be detrimental when driving.

Have a look at https://www.steadymixes.com for 130BPM mixes and mashups to keep your pace moving.

High BPM music is fine for non-thinking tasks. If I have to actually debug a complicated issue it becomes counterproductive.

The left one is always the error because the right is the right one.

I think you're talking about Sorbet: https://sorbet.run/

I use tmux + vim. I use different tmux sessions for work, school and side projects.

I learned to shut up and let things be when it does not concern me.

Great advise, I am guilty of taking sides/playing hero without knowing the details is important.

If you're familiar with Django, just go for it. The documentation is really nice and it is batteries included: admin panel, authentication, permissions and more. All this free stuff will let you focus on your app instead of what is around it.

For the frontend, it depends on your goals. If you need a quick prototype, just use the Django templating engine and ship something quick. If you want to learn, choose a popular frontend framework and stick to it. They are all pretty good. Check their API / ecosystems and pick the one you like :)