Engineers are expensive, especially good system engineers who are trained in your code base. Very possible that this just hadn't gotten to the top of the priority list.

▲

eviks 3 hours ago | parent [-]

I don't understand why you need training on your code base to design a cache format for read only vs rw workloads, but anyway yours is a comment about neglect, not the "evil" that would happen if you did that design

▲

Spooky23 2 hours ago | parent | next [-]

I see your point but disagree. Engineering is about constraints. Time, materials, labor, scope.

The “evil” of premature optimization is that it’s a misapplication of priority. If I have an acute medical problem that needs attention, it’s not the right time to talk about chloresterol and statins, get my broken leg set.

There’s always a tension between engineering management who needs to deliver a solution to the business and engineers who want to deliver a beautiful object.

▲

win311fwg 3 hours ago | parent | prev [-]

> I don't understand why you need training on your code base to design a cache format

Because anyone willing to come in just to design your cache format is going to expect payment that is many multiples more than the engineers you already cannot afford? Long-term employees cost less, which brings them closer to being affordable, but you have to be able to keep them busy for long periods of time to realize that reduction in cost. A engineer who doesn't understand your codebase isn't going to be useful for very long.

	▲	eviks 3 hours ago \| parent [-]
		You explained why it's beneficial for other workloads, but the original point was about this specific design