I'm a Software Engineer (yes, just imagine that).
Write code. Break it. Rewrite it better.
Sometimes structured. Often chaotic.
No grand mission. Just building things that work (mostly).
Not interested in hype. Not here to impress.
If it runs and makes sense, that’s enough.
Irregular. Depends on mood, time, and whether the code fights back.
- Minimalism is practical.
- Documentation exists for when memory fails.
- Abstractions are useful, until they're not.
- Code is never finished, only abandoned.
Prefer low-level tools and languages (C, C++, ASM, etc).
Not attached to any specific framework.
Code should do one thing and do it well.
If it needs an explanation, it probably wasn't simple enough.
- Projects in various states: complete, broken, or forgotten.
- Experiments that may or may not work.
- Occasional documentation (if lucky).
Some projects here are no longer maintained.
They might be revived, or not.
- Open to issues or pull requests if relevant.
- Not interested in pointless discussions.
- Suggestions welcome, debates not required.