What do you think happens if you hand over a relatively well developed software to such a team? Now let a few years pass and you have today's Skype.
What do you think happens if you hand over a relatively well developed software to such a team? Now let a few years pass and you have today's Skype.
1. You are not the customer.
With ad-driven products, we have painfully realized that if we aren't paying, we aren't the customer, and when something seems awful to us, the explanation often lies in the fact that the thing that is awful to us benefits the real customer, or perhaps that the thing that benefits us is of little value to the real customer compared to things that do not benefit us.
The same is true of Enterprise Software. Most users are not the software's customer, and therefore their needs are subordinate to the needs of the individuals and departments who are actually paying for it.
2. Pricing-Driven Development
As Spolsky famously pointed out, Enterprises forcibly impose an insane cost-of-sales on software vendors. When you have to employ expensive salespeople, prepare proposals, apocryphally play golf with clients, or whatever, vendors must build those costs into the cost of the product.
Then they must justify those costs with features that sound like they produce big values. Typically these are not going to be things that make users' lives easier, they are going to be things that users may never see, like analytics and back-office integrations.
Like the "you are not the customer" problem above, this tends to create the illusion that the software sucks and that the vendor isn't improving it. In actual fact, the vendor is locked into a Red Queen's Race with competing vendors, and is improving the software constantly. It's just that users never benefit from the improvements, because UX improvements are not thought to "move the needle."
Are you implying people are paying for dropped calls and poor performance as a feature?
That's a scenario where the needs of the people making and receiving calls are subordinate to the needs of the people paying for Skype.
But sometimes it is a question of different priorities, and I did not mention that above. Good catch.
The old normal (not for business) Skype Linux client could even do active screen sharing (share your own screen) on Linux. Although it was limited to 1:1 calls IIRC. Haven't checked whether they have managed to break/remove that in the new Linux client...
Software is horrible.
Software that looked like Excel 2000 with visible accelerators was clean, easy to use, discoverable, fast, not very aesthetically pleasing but at least consistent. macOS of 5+ years ago was more human-friendly.
Linux usability is only abhorrent if you use Gnome (3). It's fine with KDE, Xfce, and others. I started using Xfce recently at work and it's great: usability is just what I expect (i.e. it doesn't do any weird UI experiments like Gnome3, Windows, etc.), it's stable and reliable, and discoverable since it was designed back when they thought discoverability was a good thing. KDE5 is pretty good too.
Stop using UIs that have been taken over by people trying to "revolutionize" UIs and you won't have the problems you're seeing. Linux has plenty of such UIs, but for some odd reason they're not the default setting of the mainstream distros.
I like my setup (i3wm), but it would be a horrible default. You have to read a manual to make it usable. Gnome is a kind of nice default - since everything looks modern and works out of the box.
root@server:~# ip route add 192.168.1.0/30 10.0.0.1
Error: either "to" is duplicate, or "10.0.0.1" is a garbage.
The "help" is literally a dump of the grammar, which doesn't contain enough detail to add a route (the syntax of PREFIX is not described). The error message is bafflingly useless. Of all the options available relating to routing, the two I use most are "route a network via a gateway IP" and "remove a route" and I'm going to guess that those are the two most common operations for most people not doing any advanced networking.
Note that this is the replacement to the old "route" command, which had a single line of help: "inet_route [-vF] add {-host|-net} Target[/prefix] [gw Gw]" which is way way more helpful for this use case!
Of course it's possible to go into `man ip` and then find routing help is elsewere and go into `man ip-route` and at the bottom of a 400 line document there is /a single example/ of adding a default route which doesn't include a subnet definition, and then to decode that the error message about duplicate/garbage means "you didn't add the word "via"" and then to backtrack into the grammar dump and trace where that was mentioned.
And of course this is but one tool.
And of course it's better for many use cases that it be stable and performant than that it be frilly.
But all over, it feels like this. Usability, quality error messages, making the common things easy and discoverable, are all afterthoughts with priorities somewhere between "caveat user" and "it's free so shut up" and "we refuse to change it because ~POSIX~" and "usability is for wimps, Linux is for clever people (where clever means 'able to edit a text file and willing to do everything the hard way')" and "we benefit from people buying RedHat Certifications so why should we make it any easier than we have to?".
I'm not saying it's incapable or unstable or useless, but I am saying usability for common tools and overall experience is really, really, really, really poor. With possible exception "install Ubuntu/Mint/flavour-of-day and run FireFox to get to your Googles".
Completely impplaussible that maybe those stupid people do not use the alternatives, because they suck even more? As in, they are non standardized, not easy to setup et etc.
The old Skype was great. But it's gone now; that's how the world works: things change, and not always for the better. You have to adapt.
>Completely impplaussible that maybe those stupid people do not use the alternatives, because they suck even more?
Given all the complaints I've seen about new-Skype? No. It's because people are just too stupid to look for alternatives when the thing they've been using turns to crap.
>As in, they are non standardized, not easy to setup et etc.
The newer alternatives are web-based and easy (or, at least, no more difficult than new-Skype). And WTF does "standardized" mean? There's no standardization for video chat programs; that makes as much sense as asking about standardization for social media websites like Facebook.
Yes, and depending on the enterprise, these "big features only there to justify high costs" may not actually be needed or useful or relevant. It might be 'OK' to have a bunch of interns slap something together, if it only needs to be "real" enough to look pretty and look functional in a few demos or in a few specific happy-day cases.
Analytics and Reporting is probably the most common example I've seen of this -- it's not a bad feature on it's own, but companies will sometimes pay top dollar for it, even in places it makes no sense and/or will never get used. If that gets delivered in a broken/unusable state, it's "ok" because the customer will never actually click that button anyway.
----
If "New Skype" is "enterprise communication support" in a corporate feature list (and not a real product filling a real need, as it used to be) then I can see how a broken or unusable Skype could still be a 'success' for Microsoft.
Note: I don't agree with any or support any of this. But I've seen this play out in real life enough to know it happens.
But actually, I meant that it is apocryphal that salespeople have to play golf to close Enterprise Sales. It's more of a stand-in catch-all term for semi-formal socializing with the client.
"When I started in sales, my boss told me, "Your job is to get to know your customer and build a relationship. Nothing is more important than building a relationship.” The second most important thing was to make sure that the customer always won when we played golf."
https://www.forbes.com/sites/salesforce/2017/01/03/the-death...
https://discuss.fogcreek.com/askjoel/default.asp?cmd=show&ix...
"With software sold in corporations, as soon as your price gets up in the $3000 level, the amount of approval it needs is so absurd that you are not going to sell products without a salesperson making a few visits. Hiring the salesperson, sending them out to make presentations, hotels, airfare -- now it costs $50,000 to get the sale done just in sales closing costs. That's why you see a lot of software products at $100,000 and a lot under $3000, but anywhere in-between and it's impossible to make sales. (It's sort of funny -- these big corporations create so much bureaucracy around purchasing in order to protect themselves against losing money, but they just force the vendors to spend a fortune on salesforces, which results in vastly higher prices for the big corporations)."
'enterprise software' is sold to stove-pipe organizations. It can be all sorts of awful for the people who actually have to use it, as long as the people making the purchasing decision come out of the deal looking good. The software vendor isn't set up to be able to iterate and improve based on customer feedback, and their customers aren't set up to be able to offer that feedback. Hence 'enterprise software' remains in a perpetual state of awfulness and anything good about it is purely accidental.
There is a similar phenomenon with hotels. Some hotels cater to people who pay with their own money, others to people on expense accounts.
The hotels that cater to people on expense accounts often have what appears to be terrible customer service, but that's only because the "guests" are not the customer, the accounts payable and event management groups are the customers.
Those users get great features they care about, like unified billing across multiple groups in multiple locations, &c &c.
Nowadays almost everyone has some kind of instant coffee machine in the room. It could be that free WiFi is the new marker for quickly delineating one from the other.
In an interesting twist, while a free continental breakfast will often be significantly lower quality than a paid higher-end breakfast, I've found that the free wifi is almost always significantly better than the paid wifi.
In fact, many business hotels have tiered wifi plans. And they all suck, even their most expensive plans will be worse than the Motel 8 down the street.
As for continental breakfast, sure it's not as good as some really good sit-down breakfast restaurant, but it's free and more importantly it's fast: you just go down to the lobby and either eat it there or grab some stuff and take it back to your room to munch on before you leave for the day. It's a big time-saver. Going to a separate restaurant and waiting for food to be made for you and delivered and then waiting and waiting and waiting for the waiter to bring you the check takes a lot of time.
I've been staying at places like Holiday Inn, Homewood Suites by Hilton, Country Inn & Suites, Courtyard, etc., which area all most certainly "hotels" and all of them have free Wifi.
The closest I've seen was a budget hotel where I stayed (not for work) after a huge party. The WiFi at that hotel was free, but it was heavily rate-limited and the rate-limits were lifted for a fee. You could use basic web pages, but Youtube wasn't possible without paying.
I've stayed in some nice hotels in the U.S. and in a wide variety of hotels internationally. The best "nice U.S. hotel wifi" would often rank around the average 3rd world "acceptable" hotel.
Agree - 5 star hotels have the worst. Clunky, shitty, login procedures and laugh out loud ridiculous pricing models.
This is similar to the situation for tourist visas in various countries. The shittiest countries that you absolutely would never want to overstay in have the most difficult to obtain visas. I once got a visa to go to bangladesh - it was expensive, took 2 months to get, and I still had to bribe 2 different people when I got to dhaka airport to get through.
We also frequently use it for video meetings on our Microsoft surface (or whatever that 80” touch screen thing is called) and it works like a charm.
Private or normal Skype is one of the worst apps I’ve tried in 2018 though.
I wonder if it’s because they tore out the peer-to-peer stuff that made Skype great in the oldendays and replaced it with azure.
We have SfB handling everything at work - including PSTN - and it works fabulously all the time.
You can blame Microsoft for the confusion since they renamed Lync to SfB in order to leech off the (non-enterprise) Skype brand. I wonder if they will rename SfB again should the "Skype" become more toxic.
From "robot voice" to poor sound quality to randomly dropped calls, to screen shares not working, have been a daily occurrence for me.
I beg to differ on this.. we use Skype for business and have heard nothing but complaints.
One personal beef I have with it is IM messages don't sync between devices. I start a chat with someone on my workstation then when I leave my desk and try to see it on my phone it's unavailable. Or same issue when switching between an RDP and local session.
It sucks... but you can still get to them if you have access to Outlook.
Newer versions do support server side logging to your Outlook mailbox too but it must be configured by the SfB and Exchange admins.
And that's just the issues we have trying to send text, don't get me started on the video and audio.
What a piece of garbage.
Seriously. On what planet is this ever acceptable. It seems like a sophomore joke.
It's like the SfB team still lives in the "everybody uses Windows" mindset of the 90's.
The only alternative on Linux is tel.red, which works, but only for an incredibly loose definition of the word "work". I've never used a buggier piece of software.
Settings revert a lot.
It's damn slow for remote sessions. Barely usable, really. File transfers don't work most of the time (and are slow).
Phone service? Call quality is really really bad.
The mobile app (Android at least) eats battery like candy, fails to send messages and is crashing a lot.
Lync/Skype for Business is a daily pain to suffer here.
From what I'm told, the Skype for Business back-end is not enterprise-ready, by which I mean the back-end is written to assume that one user or one set of users has admin control over all the lines set up in the system. So one user or set of users remains in charge of all of the telephony details (role-based accounts, response groups, etc.). A proper enterprise-ready program allows the admin capabilities to be limited to groups of users and delegate functionality to those groups for certain lines. This arrangement lets you have multiple simultaneous admins edit different non-conflicting details (such as setup for two different response groups) simultaneously with no problems. This means large organizations with lots of somewhat independent groups have to set up work queues where someone in each group files a request for the Skype for Business admin(s) to work on requests (e.g. Please make 123-555-1234 a response group set up in the following way...). This slows down an admin in any of those groups considerably as those admins wait for their work requests to be fulfilled or further questions to be sent back in response.
Also some of the limits in Skype for Business strike me as silly: one of them concerns response groups (a Skype for Business term for how inbound calls are routed to a series of receptionists called "agents" in Skype for Business parlance). If you want a response group where some of the agents are allowed to decide whether they want to receive the calls (known as a "formal login" response group in Skype for Business parlance), and other users are required to receive the calls (an "informal login") you can't have both of these kinds of agents in the same response group. You have to set it up so that, say, the informal login agents get the call first and (if they don't take the call after a few seconds) the call is passed to the formal login agents.
From what I'm told, Skype for Business doesn't handle nested directory service groups properly when those groups contain sets of agents (which I understand Skype for Business treats as distribution lists when one uses Microsoft's directory server Active Directory). If that's so, this means that organizations that keep tidy directory service hierarchies can't reuse their groups efficiently.
The company I was working for had Skype for Business, and the video calls were such a disaster that people would secretly use Hangouts for every meeting that didn't have higher-ups participating.
That had to be the most succinct description of the corporate work environment I've ever encountered. I'm shamelessly stealing that. Well said.
You will not able to get a quote without a meeting in person to discuss "features and options" of the product in order to "synergize with your existing ERP marketplace strategy".
This definitely isn't the first time (and won't be the last) this has happened in the industry. It's always sad when it does, but it also always opens a door for a new company to create a product that fills the void.
Enterprise software comes in a huge variety of quality.
Enterprise also carries the meaning (again for me) of terribly architected software, possibly designed by someone who read about microservices and took it to the extreme that they've got an AWS lambda for doing strpad.
Look at Office for an example. It's a 30-year-old code base and everything about it shows. Office is clearly designed to maximize the number of tick marks marketing can put in their materials, and very little else.
I think a lot of the flack Office catches is because of how wide it casts its net. Just because you don't use a piece of functionality doesn't mean that it is bad.
I used to think Excel was the one exception to Office being awful until I was assigned a project creating an app in Excel using VBA and found out how incredibly fragile Excel is. This was about 6 years ago.
However, I don't think anyone thinks Office is bad because it has stuff they don't use, but that the stuff they do use either doesn't work well (e.g., Outlook) or it's too hard to use (e.g., Word).
Oh yeah, this is generally where I'd say things start to fall over. A development platform, it ain't. Generally my advice around VBA is that if you're at the stage you need anything but the simplest VBA, you probably want something else (Access for DB style work or Python/R for data munging).
Outlook has got much better - most of the previous issues around lockups and poor performance have improved if not gone away entirely. Can't speak for Exchange.