Learning note / Reflections on my studies
Computer Engineering
Computer architecture and operating systems help me connect the code I write with the machine that executes it. I find that connection useful when an application needs more than a change to its source code.
What happens beneath the program
Instructions, processors, and memory give a concrete setting to software behavior. The same operation can have very different costs depending on where data is stored and how often it needs to move.
I do not treat hardware as something separate from programming; it sets the conditions the program works within.
The operating system's role
Processes, memory management, and input/output make more sense to me as shared-resource problems. An application needs access to the machine, but it also needs to coexist with other work.
That perspective makes resource use and application isolation easier to discuss in practical terms.
A foundation for better questions
When software slows down, I want to ask whether it is waiting for computation, memory, storage, or a network operation. These foundations do not identify the answer automatically, but they help me avoid treating every delay as the same kind of issue.
What I take forward
- Connect software behavior to machine resources.
- Understand the operating system's responsibilities.
- Identify what an application is actually waiting for.