Commerce student on paper.
Linux user by lifestyle.
Programmer because I broke things and wanted to fix them.
Yes, I studied commerce.
No, I didnโt stop there.
Somewhere between balance sheets and bash scripts, I realized I enjoy:
- making computers do boring work for me
- arguing with Linux until it obeys
- deploying things to the cloud and pretending I planned it all along
I donโt know everything.
I know enough to make it work โ the rest gets handled at 2 AM with an LLM and my dark aura prompts.
- Commerce background with strong technical depth
- Backend, automation, Linux, and cloud-focused
- Comfortable shipping real systems, not just demos
- Learns fast, breaks carefully, fixes properly
- Knows why things work, not just how
Think โpractical engineer with business sense,โ not โtutorial collector.โ
Python builds the system.
Bash controls the system.
C++ reminds me humility exists.
Linux is home. Everything else is a guest OS.
Yes, Iโve broken Arch.
Yes, I fixed it.
No, reinstalling is not a solution โ itโs surrender.
- Telegram bots that actually behave
- Backend services that donโt panic
- Linux automation
- Cloud-hosted tools that quietly do their job
- Side projects that teach me more than tutorials ever did
If it breaks, understand why.
If it works, understand how.
If it works twice, document it.
I donโt fear logs.
I donโt fear errors.
I fear silent success โ because thatโs when something is definitely wrong.
Iโm not here to flex buzzwords.
Iโm here to learn, build, and ship โ one commit at a time.
โญ If you found this repo, welcome.
๐ ๏ธ If somethingโs broken, itโs probably a feature (for now).