Stack-aware challenge generation
EraCode tailors practice to technologies you configure or import from profile data.
Why the stack matters
Two developers can both “know TypeScript” while shipping in completely different ecosystems—different runtimes, test runners, deployment hooks, and failure modes.
When practice ignores that context, you rehearse skills that do not transfer cleanly to the code you touch Monday morning.
What you configure
You maintain a technology list in EraCode so challenge generation and daily work can bias toward the languages, frameworks, and tools you care about.
You can build that list manually or bootstrap from profile and resume inputs if you want a faster first pass—everything stays editable afterward.
What you should expect
Personalization steers topics and difficulty—it does not magically know private design decisions. Pair it with repo-backed practice on paid tiers when you want challenges anchored in your own modules and filenames.
Good to know
When a challenge is timed, we use a server-anchored timer and combine your AI score with how long you took—across coding, terminal, and multi-part submissions.