I built a small tool with swc-interview — code is open, feedback welcome
Postmortem: how we exhausted the connection pool in swc-interview
About 3000 words. Read the summary table first, then decide whether to go deeper.
Built a visual debugging panel for swc-interview over the weekend
Turned it into an actionable checklist; every step says why it is done and what breaks without it.
Two weeks with swc-interview: what feels right and what drives me up the wall
About 3000 words. Read the summary table first, then decide whether to go deeper.
Six rules for error handling in swc-interview that I settled on
War story: swc-interview timezone handling almost cost us a full day of billing
Turned it into an actionable checklist; every step says why it is done and what breaks without it.
The edge cases the swc-interview docs never spell out
Turned it into an actionable checklist; every step says why it is done and what breaks without it.
Building an internal platform with swc-interview from scratch: architecture and decision log
Why does swc-interview use twice the memory of comparable tools?
Happy to be convinced otherwise in the comments.
Newbie question: how should a swc-interview config file be organised?
swc-interview logging: what separates "readable" from "usable"
I attached the relevant test cases so you can just run them.
Help: swc-interview fails to start intermittently in containers, logs inside
This is the community home (/en/c/swc-interview). Pick any item in the megamenu above and the centre column swaps to that slug’s own SFC page while both side columns stay put; switch to another community and the whole theme colour changes with it.