Hone your skills,
one question a day.
AI can write code now. The people who get ahead are the ones who can read it, spot its mistakes, and explain it.
That is the skill you build here, a few minutes a day, starting from wherever you are, even if that is zero.
Not sure? Pick the closest. It only decides where we begin; a short check corrects it, and you can change track or path any time.
Dictionaries, closures, JOIN, recursion, git stash, VLANs: 701 short lessons in plain words, each with a worked example that runs.
Never written a line, or years into the job. Beginners get a short lesson before each challenge and a coach that asks the next question instead of handing over the answer. Experienced developers get real tests, no hand-holding, and a level that moves with them, which is why they are the ones who pass it on.
- Read code you did not write and say what it does. The interview question people freeze on.
- Catch the bug the AI missed, because you have met the trap before and know where to look.
- Explain your thinking out loud. The line between using a tool and understanding it.
- A habit that holds. One question a day, a streak worth keeping, progress you can actually see.
AI writes the code. You still have to know if it is right. The people who get stuck now are not the ones who cannot type code; they are the ones who cannot tell why it broke, or explain in an interview what it does.
Hone is built for exactly that gap. Nothing here writes code for you. Real tests decide whether your code passes, the coach asks questions instead of handing over fixes, and your progress ledger only ever records what you actually did.
You learn a loop. Then a dict. Then a sort key. And then you stare at a real system and have no idea which of them to reach for. That is the hardest part of learning to code, and it is where most people stall.
So every challenge here ends with where this shows up: the real thing that uses the exact idea you just practised. The same puzzle is how a shop checks its invoices add up, how a calendar finds a free slot, how a search box scans a huge log file, how your browser remembers the last pages you were on. You do not just learn the tool, you learn what it is for.
Meet a fixed bar on a track and Hone issues a certificate. The same bar for everyone: readiness in the top band, topics held under spaced recall, and problems solved without a hint. Every number on it was recorded as the work was graded, so nothing on a Hone certificate is typed in by the person receiving it.
HONE-PY-0000-0000 and looked up at honecoding.com/certificate. No account, no
sign-in, nothing to send us: type the id and the issuer answers.- Watch your code run. Values appear beside the line that produced them. Ladder rungs draw a timing diagram. Queries show their rows.
- A coach that asks, never tells. Stuck on a loop? It says “What does your counter hold the second time round?”, not the fix.
- Your own path to the answer. Every version you ran is kept, so you can see what changed when it finally went green.
- Help that fits your level. Beginners get a lesson before each challenge. Experienced people get pointed, not taught.
- Hafs. A small lioness who watches you work, brings your hints over herself, and only ever says true things about you.
- Proof a hiring manager can check. A public page of your verified work, résumé lines counted from it, and a job-ready checklist that counts itself. Every number comes from graded answers; nothing is typed in.
- Lessons you can read right now. Short lessons in plain words, each with a worked example that runs, open to anyone with no account, and every one of them ends in a box you actually type into.
- Something to run on every stage. Every stage of every curated path has something to read, something to answer and something to write, including git, the terminal and the switch console, where what you type is graded on the state you left behind.
- A credential a stranger can check. A certificate with a credential id, a signed Open Badge, an add-to-LinkedIn button, and a page that says plainly what it attests to and what it does not.
- One question a day on the thing you are closest to forgetting.
- One challenge on the same idea. Real tests decide if it passes.
- Keep going when you want to; one a day is the minimum, not the limit.
Sign in with email
We send a link. Tap it and you are in; no password to remember.
Where are you starting from?
There is no wrong answer. It only decides where we begin; a short check comes next and corrects it.
What do you want to practice?
Pick the one you want to get good at; every track gets the same care. You can change this any time in Account.
Pick your username
This is the name friends see when you practise together. Letters, numbers and underscores; you can change it later.
Free during beta. Sign in with Google or email to keep your progress on any device; without it, it stays on this one.
Lessons · For kids · About · Your level · Privacy · Terms…
Quick questions to recognise an idea. Your first counts for today; extras are optional practice.
…
One question a day, the same for everybody on this track. Your week is squares only, so sharing it gives nothing away.
Write real code and run it against tests. This is the hands-on work, and it earns more than a question.
When you are done, all of this will be true
When you are done, all of this will be true
A path is the order to learn things in. Follow one and You always shows your next step; every topic still counts wherever you meet it.
Tap any topic to practise it now. Each shows how you've done on it. { } means it has a coding challenge too.
Python quick reference: every topic on one page, one line each, to read without leaving your place.
Your streak, level and the full record of where you stand live in You.