Learning note / Reflections on my studies
Python Programming
The useful part of learning Python for me is turning a problem into steps I can explain. A short program still needs clear inputs, sensible rules, and a result that means something.
Getting the logic onto the page
I approach programming by separating what goes into a task, what needs to happen, and what should come out. Conditions and loops become easier to reason about when I can describe that sequence in plain language first.
Tracing a value through the code is more useful than staring at the final output. It gives me somewhere specific to look when a result is wrong.
Choosing how to hold the data
Lists and dictionaries are a good example of a small choice that changes the rest of a program. I use a list when order matters and think about a dictionary when the task is really about finding something by a key.
Functions then give each part of that work a name and a clear responsibility. That is the point where a script becomes easier to change.
The connection to my work
These foundations are relevant to my FastAPI and data work: understand the input, handle it deliberately, and make the output usable. The framework adds tools, but the reasoning underneath is still the same.
What I take forward
- Explain the steps before shortening the code.
- Choose data structures around the operation.
- Check intermediate values when debugging.