Recent submissions

Comment · 6 months ago
Xstate has helped me clean up some hairy situations in the past. Looking forward to the next version, and thanks for your great work!
Comment · 6 months ago
This is great! Just what I was looking for. Will try it out!
Comment · 6 months ago
Absolutely! But that doesn't capture an interrupted interactive session
Comment · 6 months ago
Comment · 6 months ago
I'm trying that out with Cursor now. But it does take some work to get it to the same state with subagents and making sure it understands the state of the progress that was interupted. But it seems worth the time to get a solid skill defined up and running that can do this, given that's it's an almost daily event by now.

Maybe a good candidate for a Claude Routine! "By this time each day, brace for upcoming outage by preparing a comprehensive information package for Cursor to take over your work on active sessions" ...

Comment · 6 months ago
I was hoping for that to work, but it seems to produce an empty file. Maybe it needs the API to work as well
Comment · 6 months ago
Have anyone found good techniques to get a session out of Claude Code, so that I can point another tool at it and pick up there? This always seems to happen at the worst possible time, after having spent an hour getting deep into something – half finished edits across files, subagents running, etc.
Comment · 7 months ago
“Thinking is to humans as swimming is to cats. They can do it, but they prefer not to.” - Kahneman
Comment · 11 months ago
Favourite Blues Brothers quote!
Comment · 2 years ago
Cannot recommend that book enough
Comment · 2 years ago
Yawn. Scrum is a standard that eliminates the need for figuring out and agreeing about a bunch of things. This has great value in the real world. What would the author do instead? Is scrum “perfect”? No. Does it solve all problems? No of course not. But it’s not meant to. It’s an abstraction layer on top of the complex mess that is software development and team coordination. Blaming the abstraction layer when something goes wrong is typically a strawman. Like blaming the REST API when it’s actually the database that’s slow.
Comment · 2 years ago
Nice :) I built the same thing a few years back for RxJS debugging. Turned out to be really useful!
Comment · 6 years ago
It’s the closest thing we have to a useful standard library. Date handling in js without a library is a code smell.
Comment · 6 years ago
Me too. This is one of my favourite podcasts.
Comment · 7 years ago
I was a musician before becoming a software developer. Max/MSP was my gateway into the general field of programming and I still rely on the intuition I built back then when forming mental models about problem solving. Object-orientation, functional concepts, declarative programming – it’s all in there in a very tangible way. It’s just a joy to work with! So, seeing how Max just keeps maturing and becoming more and more accessible makes me very happy! And having it integrate so well with Ableton and the outside world is really a major leap forward compared to back then (2004, pre-Ableton acqusition). We spent oceans of time getting sensors, midi and OSC working together reliably! Now it’s a non-issue.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton