Thank you! I _think_ we learnt that from CodeCademy who was among the first to introduce the pattern.

Eventually, we would love to. In the near/mid-term, it's unlikely.

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)

It's a change we'd love to see taking place.

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)?

Why do you call it "a lambda"? Perhaps clearer as "WhatsApp router for your sales team"

Didn't fit in the title haha - just wanted to emphasise that its just serverless

I don't really know why you would want to emphasize that. For people interested in the product, knowing the backend is serverless is irrelevant. For people interested in the technology, "serverless" and "lambda" convey virtually nothing.

I wanted to emphasise as usually the product that works is the "simplest" - we made lots of pivots and wrote lots of code before we came up with this more simple solution

The first link is exactly what I was looking for. Thank you!

I was hoping to discover tools, free or paid, that specifically help with editing copy aimed at a technical audience.

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?

The Vale linter, though it requires some initial decisions. https://passo.uno/posts/first-steps-with-the-vale-prose-lint...

So cool. Looks like the proselint site is down. For anyone else who wanted to read the approach - https://github.com/amperser/proselint/blob/b5b7536bec5fd461e...

(CodeCrafters team here).

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

Watching videos serves a diferent role than interactive b/c you get to take in audio and visual together, which _can_ support a higher bandwidth learning(depending on quality of the video). Also, for unfamiliar subjects, it’s useful to be exposed to the concepts and constructs first so you can build a mental scaffoliding that supports the details. Speech seems to be a better medium for that.

Interactive, like other info sources that present info linearly and in high detail are much less efficient, but allow you to learn the ‘doing’ aspect that a video would not.

But I am curious about what you’ve made. How has the reception for this type of info product been so far?

Makes sense. Reception has been healthy so far :)

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

Interactive stuff requires me to participate whereas videos/streams can be consumed when I'm less attentive. I've just checked out Jon Gjengset's video, that's exactly what I'm talking about. Another similar channel: https://www.youtube.com/elie2222

I'm more interested in (a) system/code design and (b) mechanically how they solve problems (eg how they debug, get around the editor etc) to improve myself. I'm less interested in the code itself.

It’s a zoomer and younger millennial thing. It’s difficult for me to understand. But if you want to appeal to them, make videos.

We do have a supplementary screencasts feature (this challenge doesn’t have one yet since its new).

Here’s what it looks like on the Redis challenge: https://app.codecrafters.io/courses/redis/stages/2/screencas...

Thanks for the tip! After 10 years-ish of doing it, I'm now done with it haha

Thanks everyone for the tips and links. Gonna look for the top Dell Ultrasharp or LG Ultrafine model that's in stock and within my budget, and go for it.

I found this nugget from Wikipedia [0] quite funny.

> 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.

[0] - https://en.wikipedia.org/wiki/Mercurial