News for hackers. Stuff that matters.
Re:Microservices Are a Big Ball of Mud by Kinrany on Wednesday January 11, 2023 @10:41AM (#34339663)
An important part of programming as a discipline is coming up with things that work regardless of context.
Re:Microservices Are a Big Ball of Mud by fndex on Wednesday January 11, 2023 @11:21AM (#34340169)
Could you give some non trivial examples of architectures or techniques in software engineering that work regardless of the context?
Re:Microservices Are a Big Ball of Mud by gwright on Wednesday January 11, 2023 @11:37AM (#34340421)
good naming

Maybe that is not "architecture" or "technique" but is is definitely not trivial and is important in almost any context -- but also probably not what you were going for.

Re:Microservices Are a Big Ball of Mud by sophacles on Wednesday January 11, 2023 @11:47AM (#34340614)
Good naming is context dependent.

ed: or rather what constitutes a good name is

Re:Microservices Are a Big Ball of Mud by Kinrany on Wednesday January 11, 2023 @02:12PM (#34343045)
Binary search works on git commits and on shelves with differently sized T-shirts equally well.
Re:Microservices Are a Big Ball of Mud by sakjur on Wednesday January 11, 2023 @11:29AM (#34340277)
This sounds interesting, how do you mean? To me it seems like context is perhaps the key element that we should concern ourselves with to further the engineering or scientific aspect of programming.

Let's say we're deciding between floating point arithmetics, fixed decimal numbers, or rational numbers. All three of which are very well-established and useful solutions to the problem of subdividing integers. We have some context already here, and we'll need to provide a bit more context to know which solution to choose. Would you agree with that?

Re:Microservices Are a Big Ball of Mud by Kinrany on Wednesday January 11, 2023 @02:23PM (#34343206)
Before context, we would need to know the problem we're trying to solve. All three are equally good if there are no requirements.