News for hackers. Stuff that matters.
Re:Software Architecture Guide by blub on Saturday August 24, 2019 @03:09PM (#20789065)
If you want to see how a properly referenced text looks like, pick any of the following:

* Code Complete - McConnell

* The Economics of Software Quality - Capers Jones

* Facts and Fallacies of Software Engineering - Robert Glass

* Making Software - Oram & Wilson

... and there are many others. Not all references have survived the test of time, L. Bossavit describes in his book " Leprechauns of Software Engineering" how several software development "facts" are in fact myths.

The approach you suggest suffers from a chicken & egg problem because you first have to be experienced enough to be able to evaluate such reference-free content, as the blog written by Martin Fowler. It's precisely the inexperienced that are likely to internalize such advice and perpetuate personality cults.

Your objections are invalid; one does not need to be better at a task than an individual in order to criticize them. Asking for references and proof is perfectly legitimate, at least if we want to approach our discipline more as engineering and less as "Strunk & White" as someone comically suggested in another comment.,

Re:Software Architecture Guide by Barrin92 on Saturday August 24, 2019 @03:33PM (#20789206)
>Your objections are invalid; one does not need to be better at a task than an individual in order to criticize them. Asking for references and proof is perfectly legitimate, at least if we want to approach our discipline more as engineering and less as "Strunk & White" as someone comically suggested in another comment

Software development, as often as comparisons are made to engineering or science is neither. It's a craft. The tools differ from person to person, each piece of software is different, a lot of practises are learned and tacit and transmitted from one pracitioner to the next.

Writing code is more like being a blacksmith than being a scientist, as much as people yearn for formalistic answers and peer reviewed studies so that they can have the appearance of objectivity, a lot of software development is fundamentally subjective.

Re:Software Architecture Guide by mlthoughts2018 on Saturday August 24, 2019 @04:04PM (#20789384)
The rampant semantic games about art vs science vs engineering vs craft littering this thread are nauseating. It’s all of those things in different contexts and situations, and regardless, seeking evidence backed advice is the right thing to do no matter what context you’re in.

My electrician father doesn’t base his craft on thought leading blogs. He has actual textbooks on electrical equipment, and guides with examples on using tools and solving certain common problems, full of reference material to other books.

I happen to think software is something like 70% craft, 25% science and 5% art, and to me this suggests not putting much stock in armchair blog opinions (and yes that includes Fowler’s) and instead seek scientific or data-backed analyses, even for craftsmanship such as any of the references in the comment above yours.

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.

Re:Software Architecture Guide by Chris2048 on Monday August 26, 2019 @07:01AM (#20798779)
Software development is indeed not "engineering or science";

But that doesn't mean it has to be "craft" or other highly subjective fields, nor that we can't aim for similar standards as other engineering disciplines.

> Writing code is more like being a blacksmith than being a scientist ... a lot of software development is fundamentally subjective.

But writing code is more like engineering than science, so why not compare those? There is subjectivity to engineering design too, but plenty objectivity in the constraints - what make something "fundamentally" subjective versus some other kind of subjective?

Is it possible we don't need to compare programming to any other profession? We can instead identify there is subjectivity in software development, and that some (but maybe not all) it it could be more objective for a benefit.

Re:Software Architecture Guide by hutzlibu on Saturday August 24, 2019 @04:20PM (#20789469)
"Your objections are invalid; one does not need to be better at a task than an individual in order to criticize them"

He did not say that. He said, that he wants concrete criticism, what ideas are wrong and if possible, why ...

Re:Software Architecture Guide by inopinatus on Saturday August 24, 2019 @08:31PM (#20790601)
Referencing and evidence has never been a benchmark requirement for works of philosophy.