I remade Hamurabi, the game I used to play a lot as a kid (even though it had a different name back then).

Misha Hohlovici — Wed, 02 Sep 2026 20:43:34 +0000

Back in the 90s, when I was in school, I had a game on my home PC called Gospodar. The idea was simple: you have 10 years to rule. You plant crops, buy land, feed your people, and wait for new settlers. I could play it for hours.

My dad was totally into it too. He quickly figured out the math and could sit there managing the kingdom for ages. We would often discuss how much grain to save for planting and how much to give to the people.

Years later, I found out it was actually the classic game Hamurabi. The code was written in BASIC back in 1973, and the original dates all the way back to 1968! The developers of the version I played just changed the name and the setting, but kept the original rules.

I always had warm memories about it and wanted to play it again. I tried finding modern versions online, but they just weren't fun. They were either pure text or had broken logic that made it way too easy to win.

I usually build websites and apps, but this time I thought, why not recreate this game from scratch exactly the way I want it?

I decided to stick to the original, keeping the Hamurabi name and the Babylon setting. I found the classic formulas online, built the engine, ran it, and realized something. My childhood memory was actually a pretty simple game. When you are an adult, those 10 years don't feel like a lifetime anymore, and the mechanics are too obvious.

I played it many times and figured out what needed to change. The original game was a bit repetitive and the math was too simple. You could get the highest score just by getting lucky in the final year.

So, I made the math a bit harder. Now, just saving up grain until year 10 is not enough for a good ending. The game tracks the stability of your rule over the whole period. It checks how population growth matches your land expansion, if there were any sudden crashes, and how well you handled crises. The cost of a mistake is much higher now.

Winning is not easy anymore. But it is possible, even if you accidentally starve a few dozen people along the way (tested it myself 😅).

Aside from the logic, I also updated the visuals. I generated some graphics and music, and added a few languages. It is a web app, so you can play it in any browser on your computer or phone. There are no registrations or accounts. Your progress is automatically saved right in your browser, so you can stop anytime and continue later.

I hope those who remember the classic Hamurabi get a nice feeling of nostalgia. And if you have never heard of it, this is a great chance to touch a piece of gaming history.

You can try your hand at ruling Babylon here: https://hammurabi.webixsoft.com

P.S. I am going to show the game to my dad this weekend. I am really curious to see what he thinks about the new balance!

Stop pasting .env files in Slack. I built an MCP server to share secrets directly from my code editor.

Misha Hohlovici — Thu, 06 Aug 2026 20:49:46 +0000

We've all been there. You need to share a .env file or an API key with a teammate. You copy it, switch to Slack or Telegram, paste it, and just hope that chat history never gets hacked.

It's a massive security hole, but we do it because it's fast.

I wanted to make secure sharing just as fast, but without leaving my AI code editor. So, at my studio Webix Soft, I built Whisper - a client-side encrypted secret sharing tool with a built-in MCP server.

The MCP Magic (Why I really built this)

Context switching breaks your flow. If you use AI editors like Cursor/Windsurf or Claude/Codex leaving your code to open a browser and generate a secure link is annoying.

With the @webixsoft/whisper-mcp package, you don't have to. You just ask your AI assistant:

"Create a secure link for my .env file."

That's it. The AI uses the MCP tool, encrypts your file locally on your machine, and drops a self-destructing secure link right into your chat. You copy the link, send it to your colleague, and keep coding.

How the security works (Zero-Knowledge)

Client-side encryption: Your secret is encrypted in your browser (or via the local MCP server) before it ever hits the internet.

The Key is in the Hash: The decryption key is generated locally and placed inside the URL hash (like #KEY). Our servers only receive a meaningless ciphertext and never see the key.

Burn after reading: When your teammate opens the link, their browser decrypts it locally. Once viewed, the data is wiped from our database forever. We don't even collect IP addresses.

A few extra nice things

Markdown Rendering: If you share a Markdown-formatted config or doc, Whisper renders it beautifully on the other side. You can easily switch to the raw source, copy it, or download it as a file.

Dark Mode: Because nobody wants to be blinded by a white screen at 2 AM. You can toggle it on the fly.

I'd love for you to try it out and hear your thoughts, especially on the MCP workflow!

You can check out the web app here: https://whisper.webixsoft.com/
And find the MCP package on npm: @webixsoft/whisper-mcp

DEV Community: Misha Hohlovici

I remade Hamurabi, the game I used to play a lot as a kid (even though it had a different name back then).

Stop pasting .env files in Slack. I built an MCP server to share secrets directly from my code editor.

The MCP Magic (Why I really built this)

How the security works (Zero-Knowledge)

A few extra nice things