Cybersecurity Engineer in the making | Building toward systems-level security research | Linux internals, exploit dev, Bash → Python → C | Documenting the climb
I'm not learning the way everyone else is learning. I'm not primarily focused on how many tools I can use or how good I am at operating them. I'm focused on understanding the engineering behind what I'm learning — how and why something was built, the underlying architecture, mechanisms, mathematics, protocols, hardware, software, and the design decisions that make it work.
For me, knowing how to use a tool is useful, but understanding what happens underneath that tool is far more valuable. Tools change, technologies evolve, and new tools replace old ones, but deep foundational knowledge stays with you.
I don't want to just know how to use the technology. I want to understand why it works, how it works, and how it was engineered in the first place.
I know how to use Linux, but I'm still learning Linux.
There's a difference.
I can use commands and work with the system, but I want to go beyond knowing what commands to type.
I want to understand the engineering behind what I'm using.
What actually happens underneath those commands?
How does the hardware communicate with the software?
What happens from the moment I press the power button to the moment I see the Ubuntu login screen?
Why was the system designed the way it was?
So I'm restarting my Linux learning journey from the ground up, not to learn how to use Linux, but to understand how it actually works.
Hardware → CPU → Memory → Storage → Firmware → Bootloader → Kernel → System Calls → Processes → Filesystems → Networking → Security.
I'm not trying to memorize commands.
I'm trying to understand the concepts, architecture, mechanisms, and engineering decisions behind the technology.
And I'll be documenting the journey as I learn.
I don't just want to use technology. I want to understand the engineering that makes it possible.
I'm not learning the way everyone else is learning. I'm not primarily focused on how many tools I can use or how good I am at operating them. I'm focused on understanding the engineering behind what I'm learning — how and why something was built, the underlying architecture, mechanisms, mathematics, protocols, hardware, software, and the design decisions that make it work.
For me, knowing how to use a tool is useful, but understanding what happens underneath that tool is far more valuable. Tools change, technologies evolve, and new tools replace old ones, but deep foundational knowledge stays with you.
I don't want to just know how to use the technology. I want to understand why it works, how it works, and how it was engineered in the first place.
Creating football content (news, highlights, photos, banter, or updates) does not automatically equal deep football knowledge, tactical understanding, or quality analysis. Not trying to belittle anyone but I can say @Blue_Footy is one of the guy i highly respect his football knowledge...
@NEISNigeria Please, I’d appreciate some technical clarification. The platform showed 3,071/3,763 PUs (81.6%), then 12,450/3,763 (330.9%), and later 2,415/4,184 (57.7%). Could this be due to what?, educate me please
#inec#osunvotes2026#osun#OsunDecides
@sowore@davido@officialABAT I respected this guy but sometimes you just have to shut up, his state can't deliver 5k vote for him last presidential election. Why so interested in another state election
@footbolmatter10@_papy_giddy1 He disrespected you. Only people who have no respect for their own parents would try to insult someone else's parents, even if that person did something wrong.