Takizawamura

I have some functional knowledge of Python. Now I would like to study Assembly Language and C to better understand Python. Part of this is simply driven by curiosity. Does anyone have any tips or recommendations for the journey?

Does anyone have a system or software that they can suggest to track meetings & project progress? These would be for my personal notes.

Currently, I track progress in an Excel sheet with a row covering details of each meeting. Separately I have a weekly log to track the trajectory of and thoughts on each project.

I'm looking for a system that is both simple and efficient.

For those who learned C after learning Python, was it worth it? Did it help you to better understand Python?

My friend works in a bank and for a long time has wanted to make the switch to Python. To date, he has read a few books and knows some intermediate concepts, such as closures, generators, etc.. Outside of Python, he has built workflows in Alteryx and knows some SQL.

His teenage son challenged him to start applying for roles in 3 calendar months from now. He figures he can dedicate a max of 3 hours per day. How should he best use his time?

Should he drill on Leetcode? Build a small portfolio? Gain a specialization within Python? How best would you allocate his hours?

Day 1 with a new IDE at a new company. The scope of an IDE, such as by JetBrains, can be quite daunting. How should one go about prioritizing which IDE components & skills to learn? Anyone have any advice/ tips?

Does anyone have a simple, minimal 'terminal-based' setup for coding that they can share? I'd prefer to stick with application defaults if possible and minimize plugins.

For context, this is for a combination of C and Python coding on a Linux machine.

'Learn to Code' videos often mention that the only way to learn coding is by actually coding. How can I balance this approach and still gain a strong conceptual knowledge of a language? Any tips?

Any languages besides Python worth investing time in for data engineering?

You normally hear of the front-end path as initially easier to enter. Are there any back-end programming paths with a lower threshold to get that initial job?

Real Python puts out a book called CPython Internals. Are there any similar resources (books, posts, videos, etc) for Golang? I'm a beginner, but trying to develop a more intuitive understanding than simple syntax adoption.