[fogleman]

> The kinds of topic being discussed are not "is DRY better than WET", but instead "could we put this new behavior in subsystem A? No, because it needs information B, which isn't available to that subsystem in context C, and we can't expose that without rewriting subsystem D, but if we split up subsystem E here and here..."

Hmm, sounds familiar...

Bingo knows everyone's name-o

Papaya & MBS generate session tokens

Wingman checks if users are ready to take it to the next level

Galactus, the all-knowing aggregator, demands a time range stretching to the end of the universe

EKS is deprecated, Omega Star still doesn't support ISO timestamps

https://www.youtube.com/watch?v=y8OnoxKotPQ

[lkglglgllm]

Wngman.

Number of softwares not supporting iso8601, TODAY (no pun), is appalling. For example, git (claiming compatibility, but isn’t).

[tormeh]

It's an infuriatingly accurate sketch. A team should usually have responsibility for no more than one service. There are many situations where this is not possible or desired (don't force your kafka connect service into your business logic service), but it's the ideal, IMO. More services mean more overhead. But someone read a blog post somewhere and suddenly we have four microservices per dev. Fun times.

[bitwize]

This is the kind of situation you get into when you let programmers design the business information systems, rather than letting systems analysts design the software systems.

[QuercusMax]

I don't think I've ever worked on a project that had "system analysts". You might as well say "this is what happens when you don't allow sorcerers to peer into the future". Best I've ever had are product managers who maybe have a vague idea of what the customer wants.

[wavemode]

No, this is the situation you get into when you have programmers build a system, the requirements of that system change 15 times over the course of 15 years, and then you never give those programmers time to go back and redesign, so they keep having to stack new hacks and kludges on top of the old hacks and kludges.

Anyone who has worked at a large company has encountered a Galactus, that was simply never redesigned into a simple unified service because doing so would sideline other work considered higher priority.