Log inSign up
Laszlo profile banner
user avatar

Laszlo

@laszlocph
Building a Kubernetes client with Cursor AI: gimlet-io/capacitor
Budapest, Hungary
gimlet.io/capacitor-next/
Born May 22
Joined April 2009
556
Following
770
Followers
RepliesMedia
  • user avatar
    Laszlo
    @laszlocph
    Jan 12
    word of mouth === bragging > impresses them so much > that they wanna brag about it > to their network > their whole status spins around them discovering & > consuming high quality cool products
    user avatar
    John Rush
    @johnrush
    Jan 10
    If you read this til the end, the chance that you’ll give up on entrepreneurship is 81% or you gonna learn the things that helped me keep going & get here I’ll touch on > product-vs-marketing debate > if distribution is the king > the truth I learned the hard way Let’s go
  • user avatar
    Laszlo
    @laszlocph
    Jan 8
    I guess we're gonna stop doing PR reviews in 2026.
    user avatar
    Daisy Hollman
    @The_Whole_Daisy
    Jan 6
    So apparently @GeoffreyHuntley's Ralph Wiggum technique (and our Claude Code plugin for it) went a little viral over the holidays? I thought I'd share a typical prompt I use with it. All of the instructional videos I've seen don't give thorough enough completion promises, IMHO
    /ralph-wiggum:ralph-loop 'Monitor the PR for any of the following: - Inline comments where the change requested has not yet been pushed to the PR. - Inline comments where the last message in the thread is not a response from Claude - CI failures, even if they appear to be unrelated to your changes (if you think that a test might actually be a flake, you can rerun it with the `gh` command line tool) - Merge conflicts - Extra changes in the PR If you are waiting on CI, do not waste time running sleep. Run some of the pr-review-toolkit agents to try and improve on your PR, or trace through the tests you are waiting on step-by-step, documenting the flow in your dev log, to make sure that the changes actually fix the test.' --completion-promise 'All comments have been addressed, all changes addressing those comments have been pushed to the PR, and all CI tests are passing. There are no merge conflicts in my PR, and it contains only changes relevant to the functionality in the PR
  • user avatar
    Laszlo
    @laszlocph
    Jan 8
    The more you can rely on the model the better. The two archetypes I see: - one is using almost vanila cursor/claudecode - the other has many rules and MCPs in context I am certainly in the vanilla camp.
    Image