Live data from Hacker News

Why Enterprise Software Sucks

twitter.com

501–510 of 570 posts

Re: Why Enterprise Software Sucks

#501
post #407

> Other baby outfits are meant for parents. They’re marked "Easy On, Easy Off" or some such, and they really mean it. Zippers aren't easy enough so they fasten using MAGNETS. A busy parent (i.e. a parent) can change an outfit in 5 seconds, one handed, before rushing to work. Magnets? That sounds like a terrible idea, since babies are not supposed to be around little magnets that they could swallow (and after a few ti…

> More importantly, we wouldn't think of buying anything for a baby that has little magnets sewn into cloth. This attitude is insane and why so many people refuse to have kids.

Can you elaborate? There’s no need to put magnets in baby clothing, and there is some risk to doing so. Why do it then?

Also, zippers take 3 seconds to do...if you don’t have 3 seconds to zip up the kid, you probably don’t have time to change the diaper underneath...

Re: Why Enterprise Software Sucks

#502
post #391

Earlier quoted context omitted.

> UX isn’t valued Good UX drives costs down for training and draining of human capital. That should be the pitch. Next question, who in the fortune 100 should hear that pitch?

You're assuming that the cost of human capital actually matters in big corporations. As someone who has worked for several Fortune 100s and a couple of government agencies, I assure you, that is not the case. Employee time is treated as having no value, and things that damage the efficiency of employees are not relevant. I once saw a "cost saving" round prohibit our team's QA engineer from getting a new SoapUI licens…

Labor costs are usually the biggest expense at most companies. Management cares a lot about human capital, they are just bad at managing it.

Re: Why Enterprise Software Sucks

#503
Ok, so this has been locked in as one of the top posts on the front page for a day or two now. I'm sure there is a good reason. Maybe it's an interesting topic, or a lot of people agree with the particular message.

But can we talk about Twitter "essays", as I like to call them, for a minute?

As soon as I see someone chaining together 3-4-5+ (let alone) 10 tweets in a row, I immediately check out & hit the back button. That's not what Twitter is for.

It has a short character limit for a reason. It's meant for SMALL, quick thoughts. Things I can scroll through quickly, consume, and move on to the next bit in my feed. Not long, drawn out opinion pieces.

If you have that much to say, write a blog post about it. Write a post in a relevant sub-reddit. Send an OP-ed piece to your local newspaper for all I care. ANYTHING, buy try to make me follow your meandering, 10+ tweet long, stream of consciousness.

I admit I didn't read past the second tweet in the chain. I read enough to learn this twitter 'essay' was spurred by his college droping blackboard. I remember blackboard in college. It's was pretty mediocre but served it's purpose for it's time & place.

Anyway... I get the reason people do this. It's typically people with a lot of followers (like this guy, with 50 thousand) and they know this is the platform that will get the most reaction for whatever undeveloped, spur of the moment, rant they want to spew out.

Which is my point. Twitter is for undeveloped, spur of the moment rants. And if it spans more than two tweets, then tweeet us a link to your blog post. Or else don't get mad when I get distracted by comments in the third tweet, and go down a rabbit hole of shit talk before I make it to the end.

Well, sorry for the HN comments rant here. I got a little to angry I guess, but at least this is a place where long form comments are acceptable. Twitter is not.

Re: Why Enterprise Software Sucks

#504
post #503

Ok, so this has been locked in as one of the top posts on the front page for a day or two now. I'm sure there is a good reason. Maybe it's an interesting topic, or a lot of people agree with the particular message. But can we talk about Twitter "essays", as I like to call them, for a minute? As soon as I see someone chaining together 3-4-5+ (let alone) 10 tweets in a row, I immediately check out & hit the back button…

They do this because it drives more engagement than tweeting a blog post link.

Re: Why Enterprise Software Sucks

#505
post #503

Ok, so this has been locked in as one of the top posts on the front page for a day or two now. I'm sure there is a good reason. Maybe it's an interesting topic, or a lot of people agree with the particular message. But can we talk about Twitter "essays", as I like to call them, for a minute? As soon as I see someone chaining together 3-4-5+ (let alone) 10 tweets in a row, I immediately check out & hit the back button…

They do this because it drives more engagement than tweeting a blog post link.

Yeah you're right. It's just been driving me crazy for a while now.

It just feels so clunky. It feels very self-gratifying.

Part of my point is you typically only see this from folks who have a large amount of followers. Of which, a good percentage would be happy to click on a link to writing from someone they're ibterested in.

Seems like they are doing it because they enjoy the reaction from their follower base on the platform.

Don't make us try to follow a 1000 word thesis, in disjointed, 240 character increments... which might all have their own chain of comments.

Let us read the whole argument uninterrupted, & comment @ the end together. I'm only saying the platform isn't suited for long form ideas & discussion.

Again, sorry for ranting. Maybe I'm just in a mood tonight haha.

Re: Why Enterprise Software Sucks

#506
post #152

I think this gets it wrong. The real reason enterprise software sucks is that enterprises have complex and unique workflows and would prefer to buy software that they can fit to their workflow rather than change the workflows of their profitable business with tens of thousands of staff who will need retraining. If you look at all of the most successful software of all time they are the complete antithesis of the Unix…

No, this does completely get it right. Enterprises thought they needed all the control and security features of Blackberry until the iPhone came along and made the UX gap unsustainable. Enterprises thought they needed on-premise hosting of Exchange, Office and SharePoint instances under their control for email and productivity, until GSuite came up with a better, less configurable user experience based on consumer fe…

There’s supposedly an axiom for salesforce that it’s easier to be successful with salesforce if you adapt your business practices to match salesforce instead of the other way around.

Re: Why Enterprise Software Sucks

#507

I think this gets it wrong. The real reason enterprise software sucks is that enterprises have complex and unique workflows and would prefer to buy software that they can fit to their workflow rather than change the workflows of their profitable business with tens of thousands of staff who will need retraining. If you look at all of the most successful software of all time they are the complete antithesis of the Unix…

> The real reason enterprise software sucks is that enterprises have complex and unique workflows and would prefer to buy software that they can fit to their workflow rather than change the workflows of their profitable business with tens of thousands of staff who will need retraining.

Call me cynical, but as I see it the complexity of the problem grows to fit the number of dollars available. If it's a large organisation they will invariably choose something that takes a colossal number of people to install and maintain it.

I've seen this as a person who designed and built cash registers. Supermarkets selling 10's of thousands of products can only tolerate a limited amount of complexity - so they have the simplest systems. Liquor markets has less products, and so they start branching out into weird pricing scheme (eg, mixed dozen of certain wines - something a supermarket would never contemplate). Go to a restaurant and limited products, and hell even McDonald's will even create a product especially for you on the spot - how many patties would you like on that quarter pounder Sir? A regular restaurant creates the most insane products you've ever seen - how would like it cooked, what sauce, kids meal, and even "which of the items on this bill will your friend be paying for?"

You could argue this complexity does help sales in some way. Bureaucracies are special they add totally unnecessary complex to justify their existence. So the article gets it right in one way: in order to justify that ongoing money in people needed to maintain it they need a product that cost a lot, and so justify that it needs to have a lot ticked boxes. It is in the products makers interest to make the task seem as complex and yet attractive as possible.

Or to put it another way, a big organisation invariably consists of a number bureaucratic fiefdoms whose evolutionary imperative is to make themselves indispensable as possible by ensuring their is work that must be done by them in order for the corporation to function. They are constantly trying to grab work from each other in a dog eat dog world. The worst at it get eaten by the best.

I recently saw this first hand. An organisation is installing SAP for payroll. It's taken a team of 10 or 20 3 years so far, and it's not done. Hmm, I thought, they must be big. Nope - turns out they have a total of two offices. I could write a system that serves the payroll needs of 200 people in 2 to 3 years, and it would be customised to their exact way of operating and would only take one person to maintain it. So why SAP? They only reason I can see if a bureaucratic mandarin can pull getting it installed, he's got a guaranteed job managing 20 people for years with plenty of opportunity to grow it.

IT bureaucracies seem to be particularly cancerous. I suspect that is because most companies core competency isn't IT, yet reducing head office staff through automation depends on IT and everybody knows that. So IT can get away with more in the way of snow jobs than most.

Re: Why Enterprise Software Sucks

#508
post #407

Earlier quoted context omitted.

> More importantly, we wouldn't think of buying anything for a baby that has little magnets sewn into cloth. This attitude is insane and why so many people refuse to have kids.

Can you elaborate? There’s no need to put magnets in baby clothing, and there is some risk to doing so. Why do it then? Also, zippers take 3 seconds to do...if you don’t have 3 seconds to zip up the kid, you probably don’t have time to change the diaper underneath...

Magnetic closures are usually enclosed in seams, and address a very real need (ease of one-handed or even two/three-fingered operation). Zippers are an actual hazard for baby skin and also tend to take more hands to reliably do/undo than the typical parent trying to manage a screaming, possibly wet baby (or babies!) has available. Even if you're sticking with more traditional fasteners, snaps and Velcro are way more sensible options.

Re: Why Enterprise Software Sucks

#509
post #391

Earlier quoted context omitted.

You're assuming that the cost of human capital actually matters in big corporations. As someone who has worked for several Fortune 100s and a couple of government agencies, I assure you, that is not the case. Employee time is treated as having no value, and things that damage the efficiency of employees are not relevant. I once saw a "cost saving" round prohibit our team's QA engineer from getting a new SoapUI licens…

It works in the other direction, too. I've seen (and been in charge of) a depressing number of projects that spent hundreds of thousands of dollars' worth of people's time on writing an in-house replacement for a piece of software that cost, at most, tens of thousands of dollars. My working hypothesis is that management types don't really think the costs are comparable, because licensing fees are an operating expense…

Cutting costs gets you a raise. Delivering a big project is a path to promotion.

Re: Why Enterprise Software Sucks

#510

Earlier quoted context omitted.

> just give me ISO8601 dates, please; HackerNews, you, too! Strongly seconding. It's an annoying UX antipattern, especially as it loses precision over time ("28 minutes ago" is fine, but "yesterday" or "5 days ago" or - even worse - "2 years ago" is not; having the date specified to hours or minutes is actually useful, especially in context of a site with international audience). Doubly so on HN, which doesn't even b…

Definitely agree about the loss of precision. It's also a problem for machine readability and SEO. The solution I like is using the HMTL5 element for semantic markup of timestamps. If you do something like this: 2 minutes ago Then you get what in my opinion is the best of both worlds: machine readable timestamp in the datetime field, human-friendly detailed timestamp as a tooltip (the title field shows when you hover…

"when you hover over the element"

On the website I'm looking at Google Analytics for right now, fewer than 35% of the visitors are from devices where "hover" means anything...

Post reply on HN