3 ms·

My observation is that many teams lack strong "technical discipline"; someone that says "no, don't do that", makes the case, and takes a stand. It's easy to le

My observation is that many teams lack strong "technical discipline"; someone that says "no, don't do that", makes the case, and takes a stand. It's easy to let the complexity genie out of the bottle if the team doesn't have someone like this with enough clout/authority to actually make the team pause.

Otek 10mo ago
I 100% agree with you but also sad fact is that it’s easy to understand why people don’t want to take this role. You can make enemies easily, you need to deliver “bad news” and convince people to put more effort or prove that effort they did was not enough. Why bother when you probably won’t be the one that have to clean it up
- CharlieDigital 10mo ago
  > You can make enemies easily... Short term, definitely. In the long tail? If you are right more than you are wrong, then that manifests as respect.
  - AlwaysRock 10mo ago
    Ha! I wish I worked at the places you have worked!
Aeolun 10mo ago
I think the problem is that this microservices vs monolith decision is a really hard one to convince people of. I made a passionate case for ECS instead of lambda for a long time, but only after the rest of the team and leadership see the problems the popular strategy generates do we get something approaching uptake (and the balance has already shifted to kubernetes instead, which is at least better)
- CharlieDigital 10mo ago
  > I made a passionate case... My experience is that it is less about passion and more about reason. There's a lot of good research and writing on this topic. This paper, in particular has been really helpful for my cause: https://dl.acm.org/doi/pdf/10.1145/3593856.3595909 https://dl.acm.org/doi/pdf/10.1145/3593856.3595909 It has a lot going for it: 1) it's from Google, 2) it's easy to read and digest, 3) it makes a really clear case for monoliths.

3 ms·

My observation is that many teams lack strong "technical discipline"; someone that says "no, don't do that", makes the case, and takes a stand. It's easy to le

by CharlieDigital 10mo ago

Otek 10mo ago
I 100% agree with you but also sad fact is that it’s easy to understand why people don’t want to take this role. You can make enemies easily, you need to deliver “bad news” and convince people to put more effort or prove that effort they did was not enough. Why bother when you probably won’t be the one that have to clean it up
- CharlieDigital 10mo ago
  > You can make enemies easily... Short term, definitely. In the long tail? If you are right more than you are wrong, then that manifests as respect.
  - AlwaysRock 10mo ago
    Ha! I wish I worked at the places you have worked!
Aeolun 10mo ago
I think the problem is that this microservices vs monolith decision is a really hard one to convince people of. I made a passionate case for ECS instead of lambda for a long time, but only after the rest of the team and leadership see the problems the popular strategy generates do we get something approaching uptake (and the balance has already shifted to kubernetes instead, which is at least better)
- CharlieDigital 10mo ago
  > I made a passionate case... My experience is that it is less about passion and more about reason. There's a lot of good research and writing on this topic. This paper, in particular has been really helpful for my cause: https://dl.acm.org/doi/pdf/10.1145/3593856.3595909 https://dl.acm.org/doi/pdf/10.1145/3593856.3595909 It has a lot going for it: 1) it's from Google, 2) it's easy to read and digest, 3) it makes a really clear case for monoliths.