@Grey said in What Are You Doing Right Now:
@NerdyDad said in What Are You Doing Right Now:
Kind of lost hope and faith in Spiceworks, as a company.
It's really sad that so many people are leaving Spiceworks due to so many fixable problems. Interestingly, it's all the fault of the CEO because that's where all blame eventually lies in a company, despite the 3 envelope joke. Since we know that Jay has a marketing background, it's super obvious to see why things are failing at a company that, at it's core and slogan, was designed for IT. They've shifted to marketing their mistake, the community, and it's clearly hurting them. I predict that, unless Jay realizes that his boat is headed for Davy Jones' Locker, that ship is going to sink before anyone realizes it, if it hasn't already. People are already leaving the app and community in rafts and competitors like ManageEngine are just cheering.
At the very least, we can thank them for bringing people like Scott and most of the people in this community together. I hope that MangoCon picks up steam and is a viable event to replace SpiceWorld when it finishes circling the drain.
Should we start a deadpool on their community?
It was once a good community with people that I could learn from and ask for help if having problems. At one time, I could go to the community and learn something new about real world problems and some best practices, such as why not to use RAID5 with the exception of SSDs.
Application was good (not great), especially for the price tag. You paid for it through the advertisements, but they made money either way. Devices scanned well along with associations. Network Monitor never really worked for me well, but I figured that it was probably more of my environment and less on the product.
Then within the last year or 2, it was like, they weren't focused on the application anymore and began focusing on cloud products and tools. The tones and mood of the community started to subtly change. CTRL+ALT+TECH went away with no notice or reason. On The Air started to get very cheesy and just hard to watch with all of the bad cliches. We started to see the same questions come back around every so often, usually because the poster believed that their environment was too uniquely different to comply with best practices and thought that they were more of the exception than the norm. As time progressed, questions and posts were becoming the same over and over again and nothing was really grabbing my attention anymore. I started to answer the daily question just to keep my streak up and that would be all that I would do within the community. Then there was the layoff. Not a good day.
One day, I finally run into @scottalanmiller and was able to finally understand what was going on behind the scenes, as if he pulled the curtain revealing the wizard. And he eventually introduced me to ML when I was having a problem with a SAN 3 months ago.
The updates for the on-premise application seemed to get further and further apart. For a while it was like, every other week, then once a month, and eventually once every 3-months. This last update shows me that they are more compromising their application in order to either get them to the cloud or find something else. Plus, November's outage was not a good indicator on their part either. They were not following best practices when they're trying to teach us best practices. They failed to communicate except for through key people such as Scott via ML.
Since that day I met Scott at the Spicecorps meeting, we have been on the search for another helpdesk/asset management system. and have finally settled on one that fits our needs.
Its sad to see Spiceworks go down this path, but this is like watching your friend drink them self to death after you've tried to warn them to not go down that path.
Scott, you are absolutely right. It is a marketing company that centers around IT. It was hard for me to see it as I was wondering why a software company sells advertising. Sometimes its just difficult to get around the stones that are right in front of our noses.