Professional software engineer, musician, gamer, stoic, democratic socialist

  • 6 Posts
  • 230 Comments
Joined 3 years ago
cake
Cake day: July 2nd, 2023

help-circle






  • And by the fact of the longest part of programming being digesting code you didn’t write, in effect you’ve taken a long-cut and could have written it yourself faster.

    The conclusion doesn’t follow from the premise. Just because an LLM may need to tweak something doesn’t mean it necessarily would have been faster to do it manually. Humans need to tweak things all the time, it’s called revising, and it’s an important part of improving code.

    But I wouldn’t claim that using LLMs is always faster than coding manually, nor the opposite. There are times when LLMs do slow me down. It’s important to recognize when that risk is high.

    But I’m quite certain that for prototyping specifically, i.e. building a desired UX to get a feel for it and experiment with whether the ideas are sound, LLMs are faster.

    So you don’t get a valid answer, you just get a convincing one.

    That’s why you shouldn’t trust an LLM’s reasoning; it doesn’t actually have sound reasoning abilities. You shouldn’t rely on an LLM to reason about problems, you should use it to generate code quickly when the reasoning has either already been done by a human and/or it exists in its training set. LLMs are closer to a search engine than a problem solver.

    When asking the person why they did it…

    I see no reason why this process is mutually exclusive with using an LLM. You can use both human reasoning and LLM code generation.

    No disagreement from me about trivial changes. I make them in my editor all the time, assuming I even have an editor in front of me. Sometimes I don’t, and it’s possible to use dictation to an LLM to make trivial changes without touching a keyboard.

    That means that reviews of LLM outputted code by their nature are either invalid and/or non-optimal.

    Not convincing. I’ve given my reasons










  • If you identify with this post and you are in a manager position, please heed my warning. Throw away your prototypes. Stop vibing “quick fixes to unblock me”. Stop trying to help your devs because you think you’re superman now. You are only pissing everyone off, I promise. The devs who didn’t stop coding while you were off doing important manager/product stuff are the ones who understand what’s best for the codebase. And yes, they also know how to use LLMs.

    Just because you feel like you have a new superpower doesn’t mean that everyone needs to be saved. Follow the damn engineering process.




  • A mix of gpt-5.5 and claude opus 4.7, wrapped in my own mobile web UI that doubles as planning software and document editor.

    The reason for the mobile focus is I’ve been trying to detach from my home office as much as possible, meaning I do a lot of up-front planning via ADRs and task/story writing, then I spawn agents to actually work on coding tasks. The only part that really requires sitting at a desk is code review, manual testing, and deeper human-in-the-loop coding or debugging sessions.

    If you are able to max out the $100/mo plans from either OpenAI or Anthropic, then that is already a very cost-effective option.