Well, I'm sure you're well aware of perils of premature optimization and know how to deliver a product within a reasonable timeframe. TigerStyle seems to me to not be developed through the lens of producing value for a company via software, but rather having a nice time as a developer (see: third axiom).

I'm not saying the principles themselves are poor, but I don't think they're suitable for a commercial environment.

▲

SatvikBeri 3 hours ago | parent | next [-]

TigerStyle is developed in the context of TigerBeetle, who seem to be a successful company getting a lot done.

	▲	vohk 2 hours ago \| parent \| next [-]
		I had the same association but interestingly this version appears to be a "remix" of TigerBeetle's style guide, by an unrelated individual. At a glance, there is a lot of a crossover but some changes as well. I think the point is well made though. When you're building something like a transactions database, the margin for error is rather low.
	▲	baalimago 3 hours ago \| parent \| prev [-]
		Then I'm curious about what their principles on deadlines. I don't see how it aligns with their coding styleguide. Taking the TigerStyle at face value does not encourage deliverance. They're practically saying "take the time you need to polish your thing to perfection, 0 technical debt". But ofc, I understand styleguides are... well.. guides. Not law.

▲

atomicnature 2 hours ago | parent | prev | next [-]

Why do you think developer enjoyment is orthogonal to productivity and delivery?

▲

stouset 3 hours ago | parent | prev [-]

Which ones, specifically?