this post was submitted on 12 Mar 2024
90 points (100.0% liked)

Programming

17054 readers
886 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] magic_lobster_party@kbin.run 12 points 6 months ago* (last edited 6 months ago)

Write things down. It seems like a stupid chore, tedious, boring, and archaic, but it's the way organizations remember.

I want to add: write things down in a place where everybody can access. For example, make a habit to write issues in GitHub when decisions are made.

Simple, obvious code is easier to write, easier to get to work, easier to understand, and easier to change without breaking it.

Sometimes the simplest code is not immediately obvious. There are often cases where you start to work on what you think is the simple solution, but it turns out it’s more complicated than you initially estimated. At this point, you should know when to take a step back, and try to find alternatives. You might have overlooked a better solution first time around.

I’ve seen this in action too many times in both myself and coworkers. In the worst case a coworker spent many weeks on trying to get a solution to work, when a simple 15 minute solution was available all the time.