[–] 10 points 7 months ago

Don't jump right in to coding.

Take a feature you want, and use the plan feature to break it down. Give the plan a read. Make sure you have tests covering the files it says it'll need to touch. If not, add tests (can use LLM for that as well).

Then let the LLM work. Success rates for me are around 80% or higher for medium tasks (30 mins--1 hour for me without LLM, 15--30 mins with one, including code review)

If a task is 5 mins or so, it's usually a hit or miss (since planning would take longer). For tasks longer than 1 hour or so, it depends. Sometimes the code is full of simple idioms that the LLM can easily crush it. Other times I need to actively break it down into digestible chunks

  • source
  • [–] 4 points 7 months ago

    Solving problems for the sake of solving them yields great joy (and unexpected benefits). You don't need to have a stable job to solve a sudoku or crossword once in a while.

    If not for space exploration, we'd not have soo many technologies. We'd not have pushed so many boundaries that a lot of advances would have happened way too late than we did.

  • source
  • parent
  • context
  • view more: ‹ prev next ›