https://github.com/codecrafters-io/languages/blob/master/doc...
145 karma · joined December 22, 2013
https://github.com/codecrafters-io/languages/blob/master/doc...
That's on the cards (e.g we have Build your own React on the pipeline). There are unique challenges to making that experience predictable, so we're focusing on the "console-based" projects for now. There's also often a "subjective" nature when reviewing/testing UI so we need to think through the ideal feedback workflow for courses with frontend components.
That said, I do wanna highlight that these courses do cover a lot of ground. I look forward to your feedback once you manage to get your hands on it!
One of the things we also hear frequently is: "I don't know what to build"
Here's an example of a real user's page, who's in-progress: https://codecrafters.io/users/jaredpalmer
And some examples of "completed" users: https://codecrafters.io/users/eyalfoni https://codecrafters.io/users/byarr
Do these help? Please feel free to drop me a brief note (sarup@codecrafters.io) and I'll be happy to help you write a compelling case for PD and also explore certificates.
Our testers are all OSS. Here's our git tester for example — https://github.com/codecrafters-io/git-tester.
Others can be found on our GitHub org. https://github.com/codecrafters-io
We need to do a better job of exposing links to testers in our in-app UI — good feedback!
https://app.codecrafters.io/tracks — full list here!
Our current target is professional developers and teams with learning budgets.
Here are some reasons why experienced engineers have found value (the first expensed it, the second didn't):
1. One customer manages the Redis team at an infra company, and they used CodeCrafters as a starting point to get up-to-speed on Redis internals — to be able to do their job better. We ended up getting feedback from them on areas we could dive deeper on, to be useful to platform engineers in general.
2. A Distinguished Engineer at a Fortune 500 had built a database product before, and wanted to pick up a new language (Java, if I remember right). So they did our course because they preferred the "learning by doing" approach, and existing resources felt a bit too "hello world / todo-app"-ish.
Please give it a try once more?
I've touched on the topic a little more here: https://news.ycombinator.com/item?id=32345899
Our long-term intention is indeed to be able to help anyone who's interested to learn and grow regardless of their financial situation.
We also realise that not everyone has access to a learning budget. As an early-stage company, our pricing reflects what our current target audience is comfortable paying, and is also a test for long-term sustainability. Over time, we hope to be able to overcome pricing-related hurdles and enable broader access.
As a 2-person team, we're prioritising making a complete experience for Go, Python & JS for starters (our most popular languages).
So far, our tests are language agnostic. Our testers are written in Go (they’re open source, example: https://github.com/codecrafters-io/redis-tester). The testers interact with user code by testing for observable behaviour - exit codes, stdout/stderr, files written etc.
Although the testers are language-agnostic, a lot of the educational “content” is language-specific. We emit language-specific hints in stages where appropriate, and have expert solutions that are language-specific. A lot of this is new, so we might not have coverage across all challenges - this will improve over time.
Does that help explain our setup a little better?
The trial is available on all plans, so no need to ask the wife!
In the early days, we'd find folks sign up to do CodeCrafters because they had a "niche" job that involved knowing Redis or Docker internals (typically platform engineers at infra companies).
However, we saw that there were a set of engineers that would do all of our courses, then do redo some of them in different languages. We initially thought that to be strange (why re-learn the internals once you've already done it) — and they clarified they were in fact looking to pick up a new language.
Possibly my favorite customer call till date is a final year college student who didn't know what Redis was, had experience with C but none in Java — and within a few weeks times, he had learnt about what Redis was (and a bunch of backend concepts while he was at it), then it's internals, while learning Java at the same time
For some companies on that list, we do have more than one engineer subscribing, and for in many cases we've spoken to them to learn about their motivations and feedback. We also have a Private Leaderboards feature for teams.
In the past few months, a nice small win for Paul and I is what we like to call the "Slack Share Effect".
It's when one of our users shares CodeCrafters within their company Slack, and then we notice multiple new users that work at the same company. When we get in touch with them, I always enjoy asking "how did the OP describe CodeCrafters on Slack?" and 100% of the time, I discover that customers do a better job describing CodeCrafters than we ourselves could. It's also how we uncover use-cases :)
We have a pricing page — https://codecrafters.io/pricing, and do have it linked on our menu and footer. Would that help?
The logos highlight companies where our customers (the engineers) work. Since we're early stage, so far it's more common for engineers to discover CodeCrafters, sign up by themselves, and expense it to their company. That might explain why you can't find information about subscription on the intranet.
We also do have cases where we work with companies to land team subscriptions, so if you'd be interested for us to engage with your company, feel free to drop me a note — sarup@codecrafters.io, and I'd love to help. It might be that the person you couldn't locate has moved on from the company, but I don't have a good explanation for why you couldn't find them on LinkedIn :-D If you emailed me, I could ask them and find out for you (for references, etc) — for most listed on the website, I've been in contact with them :)
Until a few months back, we were focused solely on the "challenge" aspect of the product. Based on customer feedback, we've been making new features available that offer more guidance when you're stuck — a 2min preview is available on this demo video — https://codecrafters.io/videos/demo.
1. We show you expert-vetted code approaches for different languages in each stage, and also explain the interesting / difficult parts in the approach.
2. For further inspiration & knowledge, we now also include source walkthroughs for many of the stages, which link to how the official implementation does it. Here's one for Redis, which explains how the PING command is implemented (stage 2 of Redis). https://app.codecrafters.io/walkthroughs/redis-ping-command
Good suggestion regarding having trial projects for every language, we'll consider that.
For example, we're now starting to introduce source code walkthroughs. Here's one going over how the Redis event loop is implemented — https://app.codecrafters.io/walkthroughs/redis-event-loop.
So as you build out your Redis project, you can study in parallel how the official source does it, learn some cool facts, and overall spend more time developing fluency with the Redis docs.
One of the ways you could contribute is adding language support. If one of our courses doesn't support one of the languages you work with, you can add support for it here — https://github.com/codecrafters-io/languages.
When we first started out, we didn't pay any attention to guidance at all, and instead focused entirely on the "challenge" aspect. At that time, it was less common for early career engineers to try out the product.
We've evolved a bit since, and now it's common for us to also see early career professionals, support engineers at devtool companies, bootcamp grads, etc. From time to time, we come across Engineering Managers who'll do our modules as a way to "stay in touch" with programming (and picking up a new language they'd been itching to learn — e.g Rust).
We're probably not suitable for someone new to programming, but otherwise all other levels are welcome and find value.
Today it takes us ~2 weeks to build the "core" parts of a challenge (planning, stage instructions, tester etc). From then on, the changes are incremental (adding support for more languages, better hints/instructions, getting experts to provide feedback on solutions etc).
Hard to say how much time the incremental changes take because they’re done over a span of months, but it’s definitely work. At times our community pitches in to add language support: https://github.com/codecrafters-io/languages
Paul also did a series of tweets when we were building the SQLite challenge if you’d like to see what the challenge-building process is like: https://twitter.com/RohitPaulK/status/1421517393780740100