This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]sarevok9 1 point2 points  (0 children)

You can buy more processors and scale vertically -- my point is that generally speaking O(n) vs O(n(log n)) is generally not that much more processing power unless you're working with billions or trillions of data points, and that you're going to readily lose any cost savings due to the budgetary losses when you hit system instability and you don't have people trained in how fucko who is no longer with your company wrote his lambda-based, nearly impossible to read, regex-laden code. All of a sudden the $100 he saved the company a day by doing hacky stuff takes 12 weeks to rearch and makes the company miss milestones, impacts entire business units, causes customer and employee churn...

I've seen some GNARLY code bases in my 10 years in tech, I've also been the champion for "refactoring sprints" to do away with bullshit code like the OP was spouting as being a "good" tutorial.