Kat MarchΓ‘n π
I like how people often refer to open source code as not production ready considering the absolute horrors Iβve seen in proprietary code.
Thereβs some magical thinking that many of us are guilty that big-time company-owned projects somehow have all these quality processes.
gudenau
@zkat For every quality process there are at least three ways to get around it.
Kat MarchΓ‘n π
People on forced deadlines cut corners. That includes properly architecting things, automating processes, and even writing some basic unit tests.
I would go as far as to say that most production software doesnβt get tested beyond the author checking their own work.
Kat MarchΓ‘n π
Our entire industry is built by people who are in a rush or just canβt be arsed to do all these βbest practicesβ we keep talking about in public.
And thatβs not even talking about the sheer lack of ethics education across the entire industry that can and does lead to disaster.
Santa Claes πΈπͺππ°π
Hyperlink Your Heart
@zkat If it seems to run ok in the ideal scenario that's about as much testing as I have time for in many cases - I have too many bugs to fix that were introduced by the last guy who didn't have time for testing!
Kat MarchΓ‘n π
So I just find stuff like that xkcd comic about βone library maintained by some randomβ holding a huge tower up to beβ¦ honestly kinda dishonest about where things actually go wrong, in practice?
Kat MarchΓ‘n π
Laypeople would be absolutely horrified at all the explicit choices a company, its leadership, and its engineers make, if they could look under the hood and understand how much thought *actually* goes into their critical systems.
Adam Dalliance
@zkat yep. That source is closed to hide the company's unmentionables.
Daniil Baturin
@zkat In VyOS, we are still paying off the technical debt (implementation and, most importantly, architectural) it accumulated in its previous life as Vyatta, when it had millions in VC funding. As a community-driven project backed by a self-funded company, we can finally work to get it right.
Santa Claes πΈπͺππ°π
Nordnick
@zkat And don't forget, how many proprietary products make use of Open Source...
Tribbick
@zkat From the scrum master of a project that failed 15 months later: "Can you split all of these medium bugs into high mediums and low mediums? We don't have time to fix them all."
jec
Ryuno-Ki
@zkat
A few years ago, some researchers looked at how many contributors were active per project.
Median?
1
Andy Broomfield
@zkat Feeling that, because βleadershipβ doesnβt care about how robust something is as long as it looks like it works to βstakeholdersβ. Itβs very much like that βEverything is Brokenβ by Quinn Norton blog post a few years back.
Adrian Cochrane
@andybroomfield @zkat What do you mean "robust"? It looks pretty. It does what it needs. What else is there? /s
π΅πππππ πΊπ¦
@zkat Doesnt really matter. The problem is that you will get professional support by every company product, but for opensource software you are often on your own or need to pay an developer to implement a feature you need. Opensource does allow this flexiblity but in the end closed source is just cheaper and does the job. (and yeah, I'm pro OSS)
Kat MarchΓ‘n π
@fabiscafe "you will get professional support" is a damn lie, as someone who HAS worked on proprietary stuff :)
π΅πππππ πΊπ¦
@zkat Professional supports only means that "I pay money so I'm able to blame you if something is wrong". Nobody actually expects things to work in IT :D
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.