> 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 4 hours ago | parent | next [-]

Wngman.

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

	▲	2 hours ago \| parent [-]
		[deleted]

▲

bitwize 3 hours ago | parent | prev [-]

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 2 hours ago | parent [-]

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.

	▲	bitwize 2 hours ago \| parent [-]
		Well, that's just the problem, innit. In decades past, systems analysts performed a vital function, viewing the business and understanding its information flows as a whole and determining what information systems needed to be implemented or improved. Historically, in well-functioning information-systems departments, the programmer's job was confined to implementation only. Programming was just a translation step, going from human requirements to machine readable code. Beginning in about the 1980s or so, with the rise of PCs and later the internet, the "genius programmer" was lionized and there was a lot of money to be made through programming alone. So systems analysts were slowly done away with and programmers filled that role. These days the systems analyst as a separate profession is, as you say, nearly extinct. The programmers who replaced the analysts applied techniques and philosophies from programming to business information analysis, and that's how we got situations like with Bingo, WNGMAN, and Galactus. Little if any business analysis was done, the program information flows do not mirror the business information flows, and chaos reigns. In reality, 65% of the work should be in systems analysis and design—well before a single line of code is written. The actual programming takes up maybe 15% of the overall work. And with AI, you can get it down to maybe a tenth that: using Milt Bryce's PRIDE methodology for systems analysis and development will yield specs that are precise enough to serve as context that an LLM can use to generate the correct code with few errors or hallucinations.