When you build something in a complicated fashion or take up the mind state that it should take a good programmer to understand what it is you’re doing, you open the door for future developers to misinterpret and thus patch incorrectly. You are openly asking for years of piled on dog shit to follow. When you write shitty code, you are forfeiting the future integrity of your business

  • 6
    It's a relative thing to me. Your code should be legible and understandable so that pretty much anyone can follow the large moving parts. You also shouldn't hire people who aren't capable, or lack a basic grasp of cs-related mathematics. If you don't have the second bit, you will have shitty code, guaranteed.

    Example: I once saw a company fill a database with all possible permutations of a particular series and then randomly select from them as a means of generating a unique random id. It never occurred to them that they didn't need the database at all, or the reservation and partitioning system they had cobbled together for scale. They had a cluster of 10 servers dedicated to this system, that could be replaced by 10 lines of code in pretty much any language.
  • 1
    @SortOfTested how what wait what? No they didn't... oh wait, "humans". Still, can't compute..
  • 1
    That's always the problem with belief, it ignores objective reality in favor of personal preference 😋
  • 0
    A guy who did the first half of his career as a telephone lineman, then aged out of physical ability and spent the next 20 years riding a classic ASP application to retirement. Combination of knowing just enough to be dangerous and commanding too much seniority to be reasoned with.
  • 1
    @SortOfTested hahah I’d love to spend 6 months at this place. If that’s how they generated Ids, I’d love to see what they built for everything else. Did they build their own time zone app as well?
  • 1
    Thankfully I didn't get that deep in their code. There's a reason I stick to integrating my company's software.
Add Comment