@scholrlea said in The Ideal Software Development Environment:
you really haven't sat down and explained it all
Maybe the post quoted below isn't all of it, but it's enough:
@blakeyrat said in Microsoft fucks their developers in the ass... AGAIN:
@Bulb said in Microsoft fucks their developers in the ass... AGAIN:
There is no such thing as “open source development methodology”.
I'm talking about those meme-y pieces of shit like:
- Release early, release often
(Aka release broken shit so your users will hate you and never use your product again.)
- Do one thing and do it well
(No actual real life successful software has ever been made this way, ever. In the history of ever. What is the "one thing" Microsoft Excel does? How do you explain its success? How do you explain how it became far MORE successful when it added features that were useless for financial spreadsheets, but very useful for people making lists? Like Mail Merge. Remember what a horrible failure Napster was because it both downloaded files and played MP3s? It did TWO THINGS!)
- All eyes make bugs shallow
(I think this has been thoroughly disproven in the last few years. Just because someone is capable of looking at the code and verifying its correctness doesn't mean anybody actually will. They had to hire developers to fix OpenSSL, volunteers didn't do jack.)
There's no memes, but a few other behaviors common to open source projects:
-
Ignore bug reports from users (while simultaneously telling non-technical users that their best way to contribute is to file bug reports).
-
Refuse contributions from anybody who can't work Git, including usability experts, graphic designers, etc. Generally treat them like dirt so that all leave and do something more fun than interacting with the open source community, like for example pulling tree trunks with their teeth.
-
Do all your communication on obsolete 1970s mediums, like email or IRC, despite the fact that far superior alternatives have existed for years.
-
Have zero respect for backwards compatibility.
-
Have zero respect for software accessibility. (You're blind? Fuck you, you can't use my beautiful open source program! Yes I would have gotten text-to-speech for free if I'd just used the OS' native controls instead of that GTK+ monstrosity, but fuck you!)
-
Have zero respect for the user in general. If a person can't use Git, they're human garbage good only for jeering at.
-
Write software by just plugging together 40,000 other pieces of buggy open source software instead of writing new code, even if writing the new code would be significantly quicker and easier than managing your new dependency. (Given: mostly a JavaScript thing.)
-
(Apparently) do a somehow successful campaign to promote these bullet points to companies like Microsoft that previously had actually-healthy development practices and built reliable software.
I'm sorry that I'm not using your approved term to describe all this. Let me know what term you'd prefer.
I was going to respond to the rest of your post, but while trying to use my scroll wheel to read it this lovely open source forum software, which exemplifies the rules listed above, decided to scroll all the way to the footer of the page instead.