What if your skills had a scoreboard?
Not just projects sitting in a portfolio. Not self-reported abilities on a resume. But actual battles you've won. Real challenges you crushed. A rank that proves you can deliver under pressure.
That's what Liquidcode gives you.
Frontend developers battle 1v1. Same challenge, different approaches. One week to build. Community votes. Your rank climbs with every win, and suddenly recruiters aren't guessing if you're good. They can see it.
No algorithms. No whiteboard puzzles. Just you, your skills, and something real that people can actually see and judge.
We're still small. Just a handful of developers testing what happens when you stop talking about being good and actually prove it. But that's exactly why this moment matters. Right now, being early means something. Right now, you can actually make your mark.
The Latest Challenge: Markdown Editor
Last week, we dropped the Markdown Editor challenge. Build an editor that handles headings, lists, bold, italics, all the formatting you need. Make it functional. Make it look good. Make it yours.
Simple premise. Endless possibilities.
And here's what happened when developers got their hands on it.
Two Developers, Two Completely Different Visions
Clean interface. Live preview. Menu bar with everything you need right there. It was built exactly as a markdown editor should be: organized, functional, no-nonsense. The kind of tool that gets out of your way and lets you write.
Completely different philosophy. Distraction-free writing experience. Smooth, minimal interface. No markdown knowledge required. Write naturally and download as markdown when you're done. This was built to feel more like publishing than coding.
Same challenge. Same one week timeframe. Totally different solutions.
That's what makes Liquidcode interesting. There's no "correct" answer. Just creativity, skill, and execution.
Now It's Your Turn to Battle the Founder
I'm opening a brand new React contest for the Markdown Editor challenge. But here's the twist: I'm competing too.
First person to join faces me directly. You versus the guy who built this entire platform. One week. Same challenge. Community decides who wins.
Think you can beat me? Think your markdown editor will be better than mine?
Prove it.
Here's what you're building: A markdown editor with headings, lists, bold, italics, and all the standard formatting features. React-based. One week from the moment you join to submit your solution. Then the community votes and we see who actually brought their A-game.
Here's what you get: Win or lose, you earn the Founder Badge. Permanent early adopter status. And I'm not just saying that to sound cool. As Liquidcode grows, that badge unlocks real advantages. Free features. Lifetime perks. The kind of benefits that come from being there at the start.
But more than that? You get to find out if you're actually as good as you think you are.
First Come, First Compete
The contest is live right now. The moment you join, the clock starts. One week to build something that can stand up to what the founder creates.
No waiting. No brackets. No group stages. Just you and me, head to head.
Join the Markdown Editor Contest
First slot open. Challenge accepted?
Help Us Build Something Real
Liquidcode isn't trying to be the next massive platform tomorrow. We're building it right. Developer by developer. Battle by battle. Rank by rank.
But we need competitors. We need developers who understand that proving your skills means actually building something, not just talking about what you could build.
Join us. Compete. Help this community grow into something that actually matters.
The first battle slot is waiting. I'm waiting.
What are you waiting for?
Top comments (5)
"React-based" makes it automatically uninteresting for many. Dare a more open challenge with just any framework? 😎🚀
I considered it, but then I thought, what if one person solves the challenge in Android and the other in React? When it comes time to vote, their code can’t really be compared, and people would probably just vote for the framework they’re more familiar with. That’s why I decided to offer multiple frameworks for the contests, not just React. In the blog, I started a contest in React since it’s the one I’m most comfortable with, but the challenges themselves aren’t tied to React.
It's a very interesting situation, indeed and what you're saying makes sense. On the other hand, if you want to boost engagement, you might actually want to play on the framework wars theme.
Some developers may long to prove they can beat their opponent (and their framework) to death, just using the one they are more familiar with 🏹🪓💣
Think not just Angular vs React, but even novel, smaller frameworks, too, who are eager to prove their worth...
Anyway, Liquidcode looks great, love the idea!!
How specifically is the community deciding? What are the safety measures to prevent bots from voting? How is it preventing people from voting just for someone they know or who asked them to?
It really depends on the person, some might vote based on design, others on features or code quality. Everyone’s free to pick the solution they like most. You’re right though, people might sometimes vote for someone they know, so making the solutions anonymous during voting could be a good idea. Good catch, thanks!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.