Remix.run Logo
▲ sushisource 20 hours ago

I think this thinking misses the forest for the trees a lot of the time. Assuming you're as good as you say you are at this, you need to ask how much building robust maintainable systems _actually helps the business_. The number of products where being super duper robust actually matters is probably less than you think. It can be painful as an engineer to accept, but it's often true.

I actually happen to work on a product where reliability _is_ our #1 most critical thing, and even then in certain features and certain situations it is perfectly reasonable to prefer time-to-market over quality as long as we are clear about that to our users.

So, I'd encourage you to think from a product perspective.

▲ctkhn 19 hours ago | parent [-]

We have a similar issue but when you look at it long term it still doesn't make sense from a product perspective. We have incredibly brittle and unreproducible env setups from local (just got working this year) to dev, qa, pre-prod etc. and some tickets to automate away a lot of that work would be paid off within a quarter. Instead everyone up to and including staff engineers does nothing about it. Even our documentation of infra setups in lower environments (that prod support uses to set up higher envs) is very sloppy. But no one is evaluated on it at all. I still do it thoroughly myself just so I don't have to re-learn things when I see them again a year later but otherwise there would be no point.