, 29 tweets, 5 min read Read on Twitter
So @opsmop is having the same adoption and traffic curve problems of @vespene_io and I don't think it makes sense to continue it either. I believe in the idea a lot, but I think the whole IT open source world is burnt out and I'm tired of trying to make people interested.
To people who say this was product/market fit or I should have waited longer - respectfully, you're wrong. I know infinitely more about this space than all but about 5 people in the world :) The causes of this are interesting...
Basically (1) agile schedule pressure means no one has time at work, (2) DevOps has failed to deliver on the original vision. Both of these took time to build up and cause damage. About 12 years, honestly.
DevOps should have been about hybrid dev/ops, but instead people make common tools and then Devs are doing a lot of what ops used to do. Ops is becoming *more* sysadmin than it was halfway through this time period!
The key to open source success is when the user audience and the developer audience (those that can contribute) overlap strongly and are also engaged and inspired.
In this case, lots of discussions show everyone is busy, has no time, and also ... increasingly they have interest in low-code/no-code type solutions. This is not open source as whole, just the IT ops vertical
Looking back at the licensing discussions (Mongo, Redis, Confluent) - they were right to defend against cloud abuse - but it also says something else - to do this, they had to see *decreasing* value in community interaction
It's true that all contributions aren't always good, but the interaction and experience of working with people is a HUGE positive. But these seem to be slowing down *everywhere*. You would think if someone wrote one of the most contributed to things on GitHub...
... people would want to try his new things and share ideas, but my forum has only about 60 members, only 10 who have logged in the last week. Each project only gets 2 clones a day, which may very well be automated
I see lots of vibrancy in other areas, like the Javascript ecosystem. I have lots of enthusiasm *FOR* open source and discussing ideas. I've talked to a lot of people *with* major config management problems. But ultimately, the interaction still doesn't happen.
Open source software feeds off interaction. And this is my diagnosis basically - widescale burnout. It's been coming in slow but we didn't see it. Agile and DevOps are the burnout. IMHO we are *poorer* technologically than we were 6 years ago in some areas. Why?
We get tired, and we let things just go. We use what other people are using. We run clouds on top of our freaking clouds for no reason, and we are much more interested in tech fashion than what makes us productive. We tolerate software with thousands of bugs.
We've essentially let all of our management software become a joke. Rather than insisting on space-shuttle level craftsmanship, we just bolt more layers on top. And nobody has any power to say no. IT Software has progressed very far from any shadow of being an engineering.
I want to help fight this, but ultimately, engagement and brainstorming is my fuel. If the engagement is not there, and I can't fix the engagement, I don't get anything out of it. So, here's me being the canary, more or less.
I still like writing software, but I'm going to try to build projects that personally interest me, and turn my back on servant leadership a good bit. This means things like my music sequencer project. Because I think people do care about hobbies...
I'm hoping the engagement will be there in great numbers. If it's not, it can still be used to crank out some cool tunes. I may also chase some interesting data analysis things, because that seems interesting to me too.
How can we fix open source in general for IT? Look to what devops should be... you should be as much dev as your devs are being ops. Fight agile eating your schedule. Try new things, imagine, explore variations and don't try to be like everyone else.
Block developer advocates on twitter. We like to talk about representation, but think about what "buy local" might mean for tech. Support smaller projects and ISVs. Interact. Most of us seem to feed more on interaction than anything else.
A future where we just consume software made by one of four different brands feels pretty dull to me, especially where there isn't a lot of code in that future. To survive that consolidation, we need variety. And to get there, we must reject consolidation of practice.
Very few of the things we do are the best way to do them, they are just the ways everybody does them. Much of the software everybody wants to use sucks. What fun is that, really? Reject mediocrity and do what feels right.
As for the depression/burnout thing, care about your craft. Enjoy performance. Making things bulletproof. Sharing scripts you wrote. Blogging. Anything. Communicate and share more. Maybe slowly, we can change this.
But the next time some talk comes up about a paradigm shift like "agile" or "devops", given by someone who hasn't actually written or built anything meaningful, be polite, but don't take what they are selling.
We must value *engineering* work, what we create, specific actual things, not bullshit sayings or repeating mantras about processes. That is the metric of our value and how we make things better.
We let the movements in that did this to us, and we're still doing it. This accepting of consolidation and not caring about software quality in the tools we all endorse simply must end. IT is engineering, treat it like it.
If this is hard for *ME*, imagine it is like for someone without the platform. For me, OSS was a great way to connect with a lot of people and lots of fun, and ... if *I* can't do it today, ouch
All the kinds of cool aid we drank back at Red Hat in 2006 about the OSS movement are things I simply can't believe in anymore today. The movement wasn't wrong, but something around the culture shifted that killed it.
I can't help but wonder if that is why Red Hat was sold not for the distro, but (per IBM announcement) for a Kubernetes distribution and OpenStack. Did they see this too? What is every big company with an OSS project thinking about engagement but unable to say?
Of course, they'd probably say something different, but I'm interested in what they are thinking. And I'm thinking they are all thinking it's a good freemium download model, but the actual code and collaboration doesn't matter anymore because people don't engage with it.
(to whoever clicked "like" on this, ugh... thanks?)
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Michael DeHaan
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!