tsmango

4 ms·

1. 1.▲
   by tsmango 1y ago

   Good question, because entropy is real. The teams I’ve seen do this well keep consistency with a mix of guardrails and culture. Guardrails - Size and complexity limits. Lints for max lines/ABC/branching. If a service starts growin
2. 2.▲
   by tsmango 1y ago

   I’m the author of the post. I get the reaction. For something like a simple login flow, this probably looks like a lot of ceremony. The goal isn’t to over-engineer it, though. Each piece handles a single concern that may evolve independentl
3. 3.▲
   by tsmango 1y ago

   I’ve been writing a series of “Design Principles” based on lessons learned from building and running software systems. The latest one is about scaling. The core idea: most apps don’t need things like Kafka or CockroachDB on day one. You can
4. 4.▲
   Design Principle: Minimize Dependencies(sleepingpotato.com)

   4 points by tsmango 2y ago|0 comments
5. 5.▲
   Looping Design Principle: Events over Callbacks(sleepingpotato.com)

   1 points by tsmango 2y ago|0 comments
6. 6.▲
   Managing Change and Minimizing Whiplash on Engineering Teams(compromised.dev)

   3 points by tsmango 2y ago|0 comments
7. 7.▲
   Bullshit Apologies / Re: Boston API Jam(thomasmango.com)

   3 points by tsmango 15y ago|0 comments