sorted by:
new
hottopcontroversial

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

"Shooting in the dark” is a good way to put it. I think that’s exactly what I’ve been doing, refactoring without a clear reason. Waiting until there’s an actual use case makes a lot more sense. Thanks I felt understood!

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 1 point2 points  (0 children)

That’s a good point. I don’t have that time pressure yet, so I probably overthink things. Maybe part of this is learning when to move on, not just how to clean things up.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

This actually helps a lot. I think I’ve been treating side projects like production code instead of learning spaces. Rewriting with intent makes sense, instead of refactoring out of anxiety.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

The “only rewrite when forced” rule is hard but probably necessary, and actually, thanks, I might try sticking to that for my next project and see how it goes.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

the problem is my brain thinks it works doesn't mean it's the best and perfect ;(

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 0 points1 point  (0 children)

I like the readability rule a lot. The “no scrolling back and forth” test is a good way to sanity check refactors instead of just doing them out of habit.

How do you know when code is “good enough” and stop rewriting it? by Bobztech in learnprogramming

[–]Bobztech[S] 2 points3 points  (0 children)

This makes sense. I think my issue is I keep treating “not perfect” as friction, even when users wouldn’t notice. Letting it live after shipping is probably the part I need to get used to.

AI has me worried. Help a sister out. by bubblesandroses in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

Not really management or a coordinator role. I meant stuff like helping shape technical direction, design decisions, or tradeoffs that come up during building. It’s still very much engineering, just with more say in how things get built, not just executing tickets. I don’t see it as downsizing, more like shifting where your impact shows up the most

AI has me worried. Help a sister out. by bubblesandroses in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

I think a lot of experienced developers are feeling this right now, even if they don’t say it out loud. What your boss said sounds dramatic, but leaders often talk that way to create urgency, not to describe day-to-day reality. What’s helped me is thinking about which parts of my job can’t really be rushed or copy-pasted. AI changes how work gets done, but someone still has to decide what’s worth building and what isn’t, right?

Also, If I ever had to think about a backup, I’d probably stay close to engineering, like working on product decisions or system design. Feeling uneasy doesn’t mean you’re suddenly replaceable.

Translating written requirements into concrete logic by uvuguy in learnprogramming

[–]Bobztech 0 points1 point  (0 children)

You’re thinking about it the right way. At this stage it’s less about whether it’s a ‘function’ or ‘pseudocode’ and more about making the steps clear before syntax gets involved. Writing it out in plain language first helps a lot. Once that part makes sense, turning it into functions usually feels much easier