Difficulty in maintaining code quality and clarity while refactoring and designing software

Signals over time

2 observed signals across 1 sources, tracked for 2 days. Confidence: low.

What people are saying Observed

• “It also differes between human-maintained codebases, too. For some greenfield project I'm developing, 99% of the time, fixing architecture and going as far upstream as possible is the right choice. For the codebase I'm working on professionally, doing the hacky thing is the right choice most of the time, because there's enough people changing it frequently enough, with little coordination, that architecture is fluid, and hacks only survive if they work well enough (otherwise someone will come around and fix it). That was true pre-LLM, too, and is simply a function of scale . And ironically, it's not laziness but pragmatism - at this scale, you just can't assume code you worked on last month will look today like anything you remember. Code review process + extensive linting and testing and AI-assisted analysis filters out most of the junior-style mistakes and flag ugly hacks, so you get a moment to pause and double-check, but if it's good enough , you merge it in and go do another useful thing.”

  Hacker News · frustration

• “Thanks for your insights. We might call LLMs non-deterministic transpilers / intention guesstimators. But how much mileage can we get out of them? Being able to somehow describe what is needed in a natural way allows me to solve more problems, to the point of jokingly calling myself and my programming colleagues “product owners”. So your management conclusion isn’t far off. To me, the interesting part is that I’m actually writing down what I want and designing how it should work in a mix of natural language and code. This was previously done mostly in code / comments, where it was easy to lose sight of the big picture as working on decent code just took so much time. This was especially true of refactoring after gaining new insights. That type of refactoring (in our codebases) is now nearly free. The code generated is of dubious quality, so this approach only goes so far. Of course, we’d look for $framework / $library to shave off many hours of work. This is what we still do, but mostly faster. I am, and have been, mostly building on top of an existing pyramid with the benefit that an LLM can consume mountains of documentation, RFCs, bug reports, and so on. I wonder ”

  Hacker News · frustration