Casual Conversation

1615 readers

201 users here now

Share a story, ask a question, or start a conversation about (almost) anything you desire. Maybe you'll make some friends in the process.

RULES

Be respectful: no harassment, hate speech, bigotry, and/or trolling
Keep the conversation nice and light hearted
Encourage conversation in your post
Avoid controversial topics such as politics or societal debates
Keep it clean and SFW: No illegal content or anything gross and inappropriate
No solicitation such as ads, promotional content, spam, surveys etc.
Respect privacy: Don’t ask for or share any personal information

Casual conversation communities:

Related discussion-focused communities

founded 1 year ago

MODERATORS

[email protected]

You ever fix something and have no idea what you did that actually fixed the problem? (lemmy.world)

submitted 6 months ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

Usually its something computer related and every time it happens, something about fixing something without knowing why it works now bothers me almost as much as never fixing whatever it is.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 6 months ago* (last edited 6 months ago) (1 children)

Problems that disappear for no apparent reason will reappear for no apparent reason.

I think this is a core part of the technical mindset/instinct. Any unexpected behavior is suspicious and makes you nervous, not just unexpected bad behavior. Plus it's just a professionalism thing - a problem was solved but I don't know what the solution was, that bothers me. It means I might not be able to fix the same problem next time I see it.

[–] [email protected] 3 points 6 months ago

This is something I'm struggling to teach a couple of the junior devs on my team - a PR that "fixes the problem but I don't know why" doesn't fix the problem