> no revenue line to follow, and no market to lose
Two paragraphs later, the topic is:
> Cost
I mean this is just incredibly lazy thinking and writing.
There's always a cost line to follow, just because there's "not a revenue line" means absolutely nothing it just sounds pithy.
And if you cut your cost hard enough, you will put platform stability in danger, or hamstring your engineering org's ability to test and iterate, which will make you lose your market.
when systems engineers through intelligent restructuring of low level data structures save 1 TB of ram for their company without loss of productivity that is unrelated to revenue and market but still improving the bottom line.
if FB puts strings shorter than 64 bytes not on the heap but into the string control data via a union, that's in the same category of saving costs without adding a single new feature.
skrtskrt · · focus · HN ↗
Two paragraphs later, the topic is:
> Cost
I mean this is just incredibly lazy thinking and writing. There's always a cost line to follow, just because there's "not a revenue line" means absolutely nothing it just sounds pithy.
And if you cut your cost hard enough, you will put platform stability in danger, or hamstring your engineering org's ability to test and iterate, which will make you lose your market.
Again, incredibly lazy thinking and writing.
froh · · focus · HN ↗
when systems engineers through intelligent restructuring of low level data structures save 1 TB of ram for their company without loss of productivity that is unrelated to revenue and market but still improving the bottom line.
if FB puts strings shorter than 64 bytes not on the heap but into the string control data via a union, that's in the same category of saving costs without adding a single new feature.