chrisrickard

6 ms·

1. 1.▲
   by chrisrickard 19d ago

   damn... cursor doesn't get as much love as claude code or codex (on here anyways), but honestly, it's gotten amazing in the last 6 months. i loved switching between sol / fable / grok 4.5. ... and something tells me fabl
2. 2.▲
   by chrisrickard 26d ago

   much needed, will give it a crack - congrats on shipping!
3. 3.▲
   by chrisrickard 3mo ago

   Of course it’s an Australian spider
4. 4.▲
   by chrisrickard 4mo ago

   Cursor 3 is a full rewrite. No VS Code
5. 5.▲
   by chrisrickard 4mo ago

   I’ve found it interesting too. It’s like I spent 20 years mastering painting in watercolour… nerding out on other painters, canvas options, even the backstory on some guy that makes a specific paint etc. And I don’t regret any of that. but
6. 6.▲
   by chrisrickard 4mo ago

   … i’m still seeing a therapist about this time period.
7. 7.▲
   by chrisrickard 6mo ago

   Thank you, a refreshingly interesting read
8. 8.▲
   by chrisrickard 8mo ago

   I have read all your yearly reviews and you’ve been an inspiration Michael. Keep it up, and I’m glad your 8th year was your happiest yet!
9. 9.▲
   by chrisrickard 8mo ago

   Skills are chainable e.g. skill A can invoke skill B and then decide to invoke skill C etc… I don’t believe your slash commands can do this?
10. 10.▲
    by chrisrickard 8mo ago

    Very cool, I didn’t realise the web audio API was so extensive these days
11. 11.▲
    by chrisrickard 8mo ago

    I did this recently. Created a Skill that had access to executing very specific ific (reviewed) script for DB interaction, that connects to your a replica/anonymised DB, read only user, via VPN, via a jumpbox.
12. 12.▲
    by chrisrickard 9mo ago

    Really fun idea treating an album like a dependency!
13. 13.▲
    by chrisrickard 9mo ago

    Also, probably a good way to give LLMs more context compared to “div soup”
14. 14.▲
    by chrisrickard 9mo ago

    Amazing achievement guys, seriously impressive. Now onwards and upwards!
15. 15.▲
    by chrisrickard 9mo ago

    very cool concept. and great tracks. congrats on shipping!
16. 16.▲
    by chrisrickard 10mo ago

    Another 15-yearer here too! Thank you HN, and for all the work you do @dang and @tomhow
17. 17.▲
    by chrisrickard 10mo ago

    Because the ridiculous scope creep perhaps? And spending $96M of government money on an website (still with large faults that were backed out) This was Accenture and Deloitte - not some backyard dev shop.
18. 18.▲
    by chrisrickard 11mo ago

    I’m working on Userdoc, a spec-driven development workspace. Break down your software requirements (Userdoc guides you through the process), refine/confirm, setup your technical specs, coding/business guidelines & guardrails,
19. 19.▲
    by chrisrickard 11mo ago

    Your second point “planning in advance” could be referred to as spec-driven development… it’s a funny term in a sense (didn’t we always do that?), but I think your 7th point drives it home “a very weird form of management” - clear instructi
20. 20.▲
    by chrisrickard 1y ago

    This is why AI development will be huge in the “Buy vs Build” space… Businesses (with a capable tech team)can build the 20% of the SaaS they need, and stop paying for the 80% every single month.
21. 21.▲
    by chrisrickard 1y ago

    We are tackling this at https://userdoc.fyi - we help you build your specs (epics, stories, acceptance criteria, tech notes, test cases, etc) - then you can generate what we call Dev Plans, one or more requirement layers for imp
22. 22.▲
    by chrisrickard 1y ago

    Tools like Userdoc ( https://userdoc.fyi ) help in a few ways, you can easily create requirements (stories, personas, journeys, test cases), but also reverse engineer existing source code into detailed docs, then ask natural langu
23. 23.▲
    by chrisrickard 1y ago

    Vibe coding in the traditional sense (coined by Karpathy back in Feb): 20% Vibe coding using detailed, structured requirements (from tools like Userdoc): 65%
24. 24.▲
    by chrisrickard 1y ago

    Userdoc is primarily around building and maintaining software requirements, so we don't do competitor research, or watch market trends etc. But we can import any info you already have (documents etc), and have an interactive wizard to
25. 25.▲
    by chrisrickard 1y ago

    The AI coding wars heat up…
26. 26.▲
    by chrisrickard 1y ago

    I think at a high level you’re correct. But no matter how much “vibe” is in the code, businesses still need to create, validate, review, and approve software requirements. This is what we help with at Userdoc.fyi - AI augmented requirements
27. 27.▲
    by chrisrickard 1y ago

    This is Userdoc, AI augmented software requirements.
28. 28.▲
    by chrisrickard 1y ago

    Similar to a feature we offer in Userdoc, we can reverse engineer a codebase not themes, features (stories), and highly detailed descriptions. In terms of of how useful it is, we’ve had many customers fing it extremely valuable… something
29. 29.▲
    by chrisrickard 1y ago

    Check out http://userdoc.fyi - helps build out super detailed requirements, user personas, and user journeys with AI
30. 30.▲
    by chrisrickard 2y ago

    Userdoc has versioning of stories and acceptance criteria, aimed to at helping this exact issue https://userdoc.fyi (transparency: I’m the founder)