I'm Yigit and I'm a computer engineer with hands-on experience in backend systems. This site is my playground. You can take it seriously, or not. I'm just enjoying a piece of tech that actually belongs to me.
I was first introduced to video games as a kid on a Windows XP machine with a floppy disk drive and a CD-ROM. I played a lot back then, but only a few really stuck with me.
One of them was Duke Nukem: Manhattan Project, a seriously underrated 2.5D platformer. A blond, jacked guy kicking mutant ass across rooftops, cracking jokes, saving women, and blowing up pigs with style. It was raw, stupid, masculine, heroic, and unforgettable. You can still grab it from a no-DRM platform, or just watch a playthrough. Your call.
And then... there was Duke Nukem Forever.
What should’ve been the continuation of a legendary franchise turned into one of the most infamous development disasters in gaming history. Years of delays, engine swaps, creative drift, and when it finally launched, it was a clunky, tone-deaf mess. Not because Duke was outdated, but because the soul was gone.
But there’s a twist in the story.
In 2022, an old 2001 build of Duke Nukem Forever leaked online. People saw a completely different game. Not perfect but promising. The art direction was there. The tone was raw. The pacing made sense. It wasn’t polished, but it was Duke.
That build became the foundation for a community-driven restoration. Fans, modders, and developers started bringing the 2001 vision back to life, piece by piece. No corporate funding. No deadlines. Just people who remembered what mattered. And honestly? That version looks more alive than anything the studios ever shipped.
That’s why Duke must live, not just as a meme or a relic, but as a reminder of what happens when you build with intent, lose your way, and then fight to take it back.
Ever wonder why university education overlaps so much with corporate standards? I used to think it was just how the world worked, that this was how engineers were made. Turns out, they’re not trying to make engineers. They’re training soldiers. People who follow orders, avoid questions, and never say “but…”
The academy? It’s already full of people unqualified to teach fundamentals. Instead of helping you build real foundations, they feed you recycled content you could’ve found on the internet. It’s not education. It’s onboarding. They should rename engineering faculties to “Corporate Orientation Department of X.”
And then there’s the corporate feudalism. Most companies don’t innovate, they don’t even own their own foundations. Employees are treated like interchangeable parts. Plug-and-play humans, just like the products they ship. Low pay. High expectations. Zero support. Looks like Abraham Lincoln missed a few spots.
But maybe the real problem isn’t just the system. Maybe it’s the individuals who comply with it so eagerly. The ones who call themselves engineers but act like factory workers. Obsessing over tools. Copying tutorials blindly. Chasing paychecks and job titles like it means something while forgetting how to build, or why they even started. Just becoming an organic layer between a large language model and the project folder.
Some will say, “That’s just how business works, like it or not.” But that’s a delusional take. Technology and civilization are supposed to make life easier, not more miserable. If this is truly the only way, then you're not building a future. You're just riding the tail of the Ouroboros.