Why do you think LLMs don't do a good job at generating good selectors by default?
145 karma · joined December 22, 2013
The reason we specifically chose Rust is because:
* It's rarely someone's first language, so we'll get targeted feedback from users with the right experience level
* It's a somewhat non-intuitive language and has "new/unique" ideas (e.g borrows), so the pain point is particularly strong
* It lacks learning resources (my guess is because the number of Rust developers is relatively small and there's higher barrier to producing content)
We are aware of tech teams that use our challenges instead of LeetCode style questions for interviewing. We run our interviews using this system. Candidates seem to enjoy the experience, and it's much harder to "fake".
There are two main challenges today:
* Interviewers themselves are used to the standard format — they have answers for, a way to benchmark, tools they're familiar with over years, etc.
* While much harder to "cheat" on these challenges (since there are so many touch-points), offering these as take-homes might be lengthy for some engineers.
If you were in our place, what would you try to do for increasing adoption (whether for hiring or learning)?
There's clearly a fact-based, no BS writing style that resonates well with HN for example.
Are there tools that help detect such BS in writing?
Hemingway Editor comes to mind, what else?
Related:
* https://news.ycombinator.com/item?id=32342334
* https://news.ycombinator.com/item?id=37941075
On average I'd say we get a 50/50 split between folks who like the doing/challenge aspect of it, vs those who wished there was more "consuming" type of content, e.g vidoes/text
Here’s what it looks like on the Redis challenge: https://app.codecrafters.io/courses/redis/stages/2/screencas...
Out of curiosity, is there a reason why you prefer video format vs. interactive?
e.g out of habit, when I'm having a meal, I like watching "course videos" or streams occasionally. Is yours similar?
P.S. Jon Gjengset did a comprehensive stream going through the Build your own BitTorrent challenge https://youtu.be/jf_ddGnum_4?si=nwVLbe_2XsheIKav, if you're interested in Rust
> In an answer on the Mercurial mailing list, Olivia Mackall explained how the name "Mercurial" was chosen:
> Shortly before the first release, I read an article about the ongoing Bitkeeper debacle that described Larry McVoy as mercurial (in the sense of 'fickle'). Given the multiple meanings, the convenient abbreviation, and the good fit with my pre-existing naming scheme (see my email address), it clicked instantly. Mercurial is thus named in Larry's honor. I do not know if the same is true of Git.
Would you target "first-time" creators, or experienced ones?
And if experienced, why would they take a bet on Uneebee vs. existing platforms?
Build your own Redis — https://app.codecrafters.io/courses/redis/overview
Build your own Git (interactive)
https://app.codecrafters.io/courses/git/overview
Supports Haskell as well as Rust, among other languages
You're right, we could present it as just the articles.
Our overview is publicly accessible and doesn't require a paywall. https://app.codecrafters.io/courses/bittorrent/overview
All the "content" is also available on our GitHub https://github.com/codecrafters-io/build-your-own-bittorrent
If you'd like us to run tests against your code, show you progress, community examples, hints, and so on, then you can do the interactive experience, which requires signing up.