|
|
|
|
|
by Balinares
128 days ago
|
|
I literally got my current cushy gig to fix a codebase that was crumbling under its own unmaintainable weight at a company that, like you, thought that quality doesn't matter. This is not the first time in my career I get a great job that way. "Quality doesn't matter" people are why I'm not worried about employment. While there is value in getting features out fast, definitely, there always comes a point on your scaling journey where you have to evolve the stack structure for the purpose of getting those features out fast sustainably. That's where the quality of the engineering makes a difference. (Anecdotally, the YouTube codebase may be locally messy, but its overall architecture is beautiful. You cannot have a system that uploads, processes, encodes, stores, and indexes massive amounts of videos every hour of every day that in the overwhelming majority of cases will be watched less than 10 times, and still make a profit, without some brilliant engineering coming in somewhere.) |
|