News for hackers. Stuff that matters.
Re:Software Architecture Guide by blub on Saturday August 24, 2019 @03:46PM (#20789293)
Software development does have a certain Darwinian character - whatever survives and thrives can't be wrong.

Embracing this seems misguided, because as software becomes more complex, it's no longer enough to have software blacksmiths banging away with their software hammers and unit testing the end result into a releasable shape.

Teams working on high-availability, high-reliability software know this and take a rigorous approach. Too many take the BDD approach (blog-driven development) and when the thing inevitably falls apart, the customers pick up the broken pieces.

Re:Software Architecture Guide by atoav on Saturday August 24, 2019 @04:26PM (#20789500)
> Software development does have a certain Darwinian character - whatever survives and thrives can't be wrong.

I am not sure of that. A lot of what we see today is just adding an abstraction on top of other abstractions. People use five frameworks for a static webpage that could have been easily made in half a day using editor, css and html without ever writing a single line of javascript.

In a evolutionary sense it works for them, but the reason isn't that html and css wouldn't also work, the reason is that they believe they have to use it.

So I'd be careful with the darwinian comparison here, this is more a mimetic or meme-like evolution of ideas and once the layer below is abstracted away it is quite easy to just forget about it alltogether.

Re:Software Architecture Guide by rhizome on Saturday August 24, 2019 @07:34PM (#20790367)
A lot of what we see today is just adding an abstraction on top of other abstractions. People use five frameworks for a static webpage that could have been easily made in half a day using editor, css and html without ever writing a single line of javascript.

Not to speak for them, but I think it's more that despite decades of ridicule, there's still a lot of COBOL out there humming along. Some of it might even be deciding whether or not your health insurance is going to cover that thing that you went to the doctor for the other day. See also: Visual Basic, ColdFusion and so on.

Re:Software Architecture Guide by onemoresoop on Saturday August 24, 2019 @09:56PM (#20790873)
Not sure I agree. One example. Theres a lot of mainframe code still in production, it survived and it’s still doing its job to this day. The reason it survived is because replacing it is very very costly.
Re:Software Architecture Guide by inopinatus on Saturday August 24, 2019 @07:54PM (#20790446)
> Teams working on high-availability, high-reliability software know this and take a rigorous approach

Approaches that are, nevertheless, still more akin to philosophy than engineering.

Re:Software Architecture Guide by blub on Sunday August 25, 2019 @03:11AM (#20791786)
Please detail your understanding of what philosophy is and how it resembles what such teams are doing. My gut feeling is that they're quite different, but I could be missing something...
Re:Software Architecture Guide by inopinatus on Sunday August 25, 2019 @04:56PM (#20795527)
I don’t reward sealioning.
Re:Software Architecture Guide by Chris2048 on Monday August 26, 2019 @07:06AM (#20798801)
> Sealioning is a type of trolling or harassment which consists of pursuing people with persistent requests for evidence or repeated questions

Asking what you mean by what you wrote in a public discussion forum isn't seasoning. You aren't being asked for evidence for you opinion, but what that opinion is, and the context of a discussion forum implies you mean to discuss the topic. Also, I can't see the "persistence" or bad-faith that would make it trolling.

Re:Software Architecture Guide by inopinatus on Tuesday August 27, 2019 @12:14AM (#20806285)
I looked at the correspondent’s other posts in the same thread. They qualified.
Re:Software Architecture Guide by blub on Monday August 26, 2019 @10:10AM (#20799982)
All right, but if we take the standard definition of philosophy then your initial claim makes no sense.

The study of the fundamental nature of knowledge, reality and existence is unrelated to writing software.

Re:Software Architecture Guide by inopinatus on Tuesday August 27, 2019 @12:18AM (#20806299)
When I build applications the questions of “What is truth?” “What is the essence of a thing?” “What is useful?” are top-of-mind throughout, because there’s no rigour without context and purpose.

Software development is applied philosophy. Wittgenstein would’ve been good at it.