58 ms·

I used to work in a system where seemingly trivial sort()s would break the entire stack. It is entirely plausible that a sort is nontrivial.

• josephg 4y ago
  In 30 years of programming I've worked in plenty of systems where this sort of thing is nontrivial too. But its always the result of incompetent abstractions getting in the programmer's way. Downvotes notwithstanding, I stand by my claim that this is always the result of incompetence. Either at the small level (laziness) or at a larger scale (incompetent system design).
  • _s 4y ago
    I would even go as far as saying the opposite - engineers too "competent" for their own good. I've walked in to so many code based where very talented individuals have made incredibly complex systems, using all their technical know how of best practices & patterns, abstraction layers and facades ... and ignored the fact that all they needed was a three field form with a submit button. It's not just worth knowing if you can, it's if you should.
    • josephg 4y ago
      Yeah - overly clever design isn't good design. The novice creates simple work because she isn't capable. The apprentice makes unnecessarily complex designs to impress. The master makes things simple because extra work would be unnecessary. Mastery isn't measured by much complexity has been added. Its measured by how much complexity has been taken away.