Q: Why so many unfinished projects?

I care about each line of code i write, what it does, how and why it exists, so I can actually maintain it.

I’d rather have an incomplete codebase I can revisit and trust, than ship something generated overnight without context or ownership.

Maintenance requires context, not just code:

- Clear problem definition
- Good architecture
- Solid system design
- Long-term ownership
- Discipline in testing and refactoring

That’s engineering.

#AI #LLM #OpenSource

@ghostwriter i feel the same way, though nobody would believe it looking at what likely seems like chaos in my repos. had to learn to not be afraid to fuck my own shit up to be more good in the long run.

@bobmagicii That’s part of the process most people don’t talk about.

What looks like chaos from the outside is usually exploration, iteration, and pushing boundaries.

You have to break things, rebuild, and seeing where assumptions fail, building real understanding.

Most people skip this step and just keep stacking abstractions they don’t fully understand.

@ghostwriter Same here! Unfortunately, my personal quality standards influence my work, and that slower process to get it right once doesn't fly very well. I need a way to learn balance between good enough for the job and good enough for myself.
@cautionbug @ghostwriter not sure about that. compromising your quality standards is just another way of applying a multiplier to tech debt and future grief.

@cautionbug Job is one thing. They tell me „You don‘t get paid for beautiful code“, ok, they don‘t get beautiful code and they have to pay for the bug fixing later.

Personal projects are … personal. I want to like what I make.

@ghostwriter

@chris_evelyn This is generally the position I would take, too, I just struggle to actually *keep* that balance.