SUYASH NAMDEO
I learn by breaking systems and understanding why they break. Programming is a craft, game development is a creative outlet, and philosophy keeps me questioning why things are built the way they are.
Type help to see available commands. Use arrow keys for history.
I work close
to the machine.
Most people use computers. I want to understand them. My daily driver is Arch Linux, my window manager is Hyprland, and I configure everything by hand—not because it's faster, but because understanding how things work at every layer is the whole point.
I treat programming as a craft rather than a skill checklist. I read documentation. I build things to break them. I fix them properly. Slow progress is fine when genuine understanding is the goal.
Outside of systems work, game development is where logic meets storytelling. Philosophy keeps me asking why things are designed the way they are. Consciousness studies make me question what experience itself means.
Fundamentals first
Read the docs. Understand the primitives. Skip no steps.
Learn by doing
Break it intentionally. Fix it properly. Own the result.
Question the defaults
Why does this exist this way? Could it be otherwise?
What drives me.
Linux & Systems
Daily-driving Arch Linux, crafting Hyprland configs, understanding how the OS makes decisions you never asked it to explain.
Programming
Writing code that works and understanding why it works. C# for systems logic, Python for scripting, Bash because everything is a shell script eventually.
Game Development
Building worlds where mechanics and narrative reinforce each other. Godot Engine as the workshop. Story-driven design as the north star.
Philosophy
Why is software designed this way? What assumptions underlie a tool? Philosophy as a debugging framework for the ideas behind the technology.
Consciousness
What is experience? Why does subjective reality feel like anything at all? The hard problem is still hard, and that's precisely what makes it worth studying.
Storytelling & Lore
World-building as a discipline. Creating lore that feels inevitable in hindsight. Narrative design where every detail earns its place.
Customization
The environment reflects the person. Every config file is an opinion about how work should feel. Ricing as philosophy, not aesthetics.
Optimization
Not premature. Thoughtful. Understanding bottlenecks before fixing them. Performance as a form of respect for the user and the machine.
The toolkit.
Languages
Linux & OS
Game Development
Tools & Workflow
Things I've built.
What I'm building
toward right now.
Strengthening Fundamentals
Going back to basics of data structures, algorithms, and memory management — to write better code from a place of understanding.
Completing a Meaningful Game
Turning the narrative prototype into a complete, shippable experience. One finished game that says something.
Exploring Consciousness
Reading Chalmers, Nagel, Dennett, and Hofstadter. Building a personal framework for thinking about subjective experience.
Low-Level Exploration
Working toward understanding C and systems-level programming — memory, pointers, compilation, linking.
Learn Deeply. Build Patiently. Question Everything.
Learning
Slow progress that produces real understanding beats fast progress that produces only familiarity.
Building
Every project is a commitment to finishing something and owning the result.
Questioning
Convention isn't justification. The best tools came from someone asking why.
Let's connect.
Open to interesting conversations about Linux, game design, philosophy, or anything worth building.