Senior Software Engineer. Founding team @ Euphoric.

Joined November 2007
The job ad was written by ChatGPT. The CV was polished by ChatGPT to match it. Then a tool scores one against the other and, surprise, everyone's a strong match. Nobody learned anything. And the screening tool isn't the first thing that went wrong.
1
1
1
28
Pull up the last three people you hired. Did every one of them meet every line in the job spec? Probably not. Which means some of those must-haves were never must-haves.
1
1
1
16
Daniel Vernon retweeted
Forgot to mention - we blasted straight through 500,000 and are at 540k now 😳
T3 Code now has over 400,000 users :)
142
15
12
1,539
41,444
Daniel Vernon retweeted
Quality of the feedback we get on T3 Code has skyrocketed last few weeks. People keep sharing detailed write ups of everything broken/weird/confusing. It’s the best. Thank you all. Really appreciate the opportunity to build something awesome.
127
14
5
2,032
54,168
Bring your hiring together. Publish jobs, source candidates, track applications and review shortlists with clear evidence. Marxel connects the workflow, with explainable AI screening and your team in control of every hiring decision. Get started free: marxel.co
1
1
20
.@thsottiaux my recent reset just disappeared?
89
I asked Astra light to investigate and review some accuracy/efficient on an engine in running in around 5-10 minutes it nuked 10% of my weekly 5x usage is this expected @thsottiaux
82
20 mins in Astra low and it’s took 10% of my 5x weekly usage whutttt @thsottiaux @OpenAIDevs
1
66
Candidate experience is mostly a coordination problem. Slow feedback, repeated questions, and unclear next steps usually mean the hiring team has lost state. Better hiring software should make that state explicit.
128
I’m skeptical of screening systems that output a score without showing the work. A useful hiring tool should show what the candidate has demonstrated, what is still unknown, and what to verify next. The decision stays with the human.
116
Most hiring workflows do not have an information problem. They have a decision problem. The evidence is spread across CVs, interview notes, inboxes, and Slack. By the time someone asks for a recommendation, the context is gone. That is what I’m exploring with Marxel.
79
opencode go usage just got super nerfed, doesn't feel like its worth now
132
Daniel Vernon retweeted
I’d argue Dan Abramov was vastly more impactful. Vastly. Dan is the reason anyone even *understands* how React works.
I think people don’t realize how much of the success of React is actually @shadcn. I once referred to React as the actual “LEGO brick for adults.” But in reality it was more the description of the geometry of the bricks. The spec. Shadcn is what people actually wanted from React. Reusable high quality components that also tunable. It’s a pseudo-library. There’s code but it’s actually meant to be digested into your context window and remixed.
Readers added context they thought people might want to know
React was open-sourced in 2013 and dominant for years before shadcn/ui launched in January 2023. Other UI libraries predated it. react.dev/versions ui.shadcn.com/docs/changelog…
12
17
3
555
53,209
every few weeks the tools change enough that the workflow you just learned already feels old
1
126
a five hour build is enough to find the next problem no need to pretend it’s the final product
1
122
Replying to @github
We have temporarily paused the roll-out of Kimi K3 while we mitigate an incident with GitHub Actions. We will resume the roll-out as soon as possible and update docs with Kimi K3 pricing, which will be $3 per 1M input tokens, $15 per 1M output tokens, and $0.30 per 1M cached input tokens.
83