News for hackers. Stuff that matters.
Re:The hard part of Enterprise Software is the Enterprise, n... by lbriner on Thursday May 20, 2021 @11:05AM (#27222074)
So true. I commented earlier on another thread about enterprises being intent on very specific implementations and premature optimisation, which leads to very bespoke and therefore expensive software.

We have a customer who "needs" to see their branches "scores" on the main dashboard regardless of the fact they could get that data somewhere else. We had to build a feature to win this customer that is only used by them and now have to maintain it forever.

The small ongoing cost of maintenance never appears to be enough to say that we're not going to support it anymore and instead concentrating on the wider market and telling this customer to click another button!

Re:The hard part of Enterprise Software is the Enterprise, n... by acwan93 on Thursday May 20, 2021 @11:58AM (#27222867)
The crazy thing is when customers demand something that inevitably breaks no matter how much we push back, like:

-Years must be in two digits since apparently nothing is built before 2000

-Not require postal codes or the city field for non-USA addresses since "we don't ship there anyway"

-Require names be in the format of first initial, last name since "everyone has a first and last name and that's how we keep track of purchases"

Things like this is what drives the cost of software up, since eventually we have to rollback changes.

Re:The hard part of Enterprise Software is the Enterprise, n... by MattGaiser on Thursday May 20, 2021 @12:35PM (#27223399)
So many of the problems in enterprise software are grafting tech onto a haphazardly developed manual process in this way.

They didn't bother collect more than two digits when starting out, so just carry that error forward forever.

Re:The hard part of Enterprise Software is the Enterprise, n... by briffle on Thursday May 20, 2021 @12:53PM (#27223675)
I wish I could remember where I read it, many, many years ago, but a blog was talking about automating systems in a government entity.

They spent much work customizing a workflow, where all requests would go to Judy, and she would decide who to route it to. They spent weeks trying to map it all out, and the logic used, etc. They eventually found out the reason this was hard-coded into their proceses, was 15 years earlier, in the days of paper based forms, Judy had the first laser printer in the building, and it was cheap to print compared to the other printers. It had nothing to do with her main job. So the printer next to her desk would hum, and then Judy would walk it to the person that needed it. Over the years, this just became accepted, and then later, incorporated into workflows/policies, and became Judy's full time job.

Re:The hard part of Enterprise Software is the Enterprise, n... by dmingod666 on Thursday May 20, 2021 @01:11PM (#27223935)
My god, the staleness and overwhelming apathy of all people involved is just something else..
Re:The hard part of Enterprise Software is the Enterprise, n... by PascLeRasc on Thursday May 20, 2021 @02:30PM (#27225176)
Well the issue is that at this time we aren’t in a position to accept new business logic change request proposals. You’re welcome to bring your issue up at the bi-quarterly documentation stakeholders meeting, oh but I’m seeing here that you actually haven’t been trained to attend that meeting. I’ve CC’d your manager to ask why they assigned this work to you, since as we know the human capital utilization policy is to only work on assigned projects.
Re:The hard part of Enterprise Software is the Enterprise, n... by acwan93 on Thursday May 20, 2021 @02:07PM (#27224815)
I don't know if it's apathy or rather just an inability to fight the system. The DMV is what immediately comes to mind.
Re:The hard part of Enterprise Software is the Enterprise, n... by anoncake on Thursday May 20, 2021 @02:30PM (#27225174)
> -Require names be in the format of first initial, last name since "everyone has a first and last name and that's how we keep track of purchases"

Also there is only one John Doe in the world, and he sometimes goes by Jeffries or Jane.

Re:The hard part of Enterprise Software is the Enterprise, n... by pixl97 on Thursday May 20, 2021 @12:56PM (#27223740)
Heh, sounds like this list (not sure if this is the orginial)

https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...

People have exactly one canonical full name.

People have exactly one full name which they go by.

People have, at this point in time, exactly one canonical full name.

People have, at this point in time, one full name which they go by.

People have exactly N names, for any value of N.

People’s names fit within a certain defined amount of space.

People’s names do not change.

People’s names change, but only at a certain enumerated set of events.

People’s names are written in ASCII.

People’s names are written in any single character set.

People’s names are all mapped in Unicode code points.

People’s names are case sensitive.

People’s names are case insensitive.

People’s names sometimes have prefixes or suffixes, but you can safely ignore those.

People’s names do not contain numbers.

People’s names are not written in ALL CAPS.

People’s names are not written in all lower case letters.

People’s names have an order to them. Picking any ordering scheme will automatically result in consistent ordering among all systems, as long as both use the same ordering scheme for the same name.

People’s first names and last names are, by necessity, different.

People have last names, family names, or anything else which is shared by folks recognized as their relatives. People’s names are globally unique.

People’s names are almost globally unique.

Alright alright but surely people’s names are diverse enough such that no million people share the same name. My system will never have to deal with names from China.

Or Japan.

Or Korea.

Or Ireland, the United Kingdom, the United States, Spain, Mexico, Brazil, Peru, Russia, Sweden, Botswana, South Africa, Trinidad, Haiti, France, or the Klingon Empire, all of which have “weird” naming schemes in common use.

That Klingon Empire thing was a joke, right?

Confound your cultural relativism! People in my society, at least, agree on one commonly accepted standard for names.

There exists an algorithm which transforms names and can be reversed losslessly. (Yes, yes, you can do it if your algorithm returns the input. You get a gold star.)

I can safely assume that this dictionary of bad words contains no people’s names in it.

People’s names are assigned at birth.

OK, maybe not at birth, but at least pretty close to birth.

Alright, alright, within a year or so of birth.

Five years?

You’re kidding me, right?

Two different systems containing data about the same person will use the same name for that person.

Two different data entry operators, given a person’s name, will by necessity enter bitwise equivalent strings on any single system, if the system is well-designed.

People whose names break my system are weird outliers . They should have had solid, acceptable names, like 田中太郎.

People have names.

Re:The hard part of Enterprise Software is the Enterprise, n... by dmingod666 on Thursday May 20, 2021 @01:12PM (#27223952)
This was the list Elon Musk used to name his kid.
Re:The hard part of Enterprise Software is the Enterprise, n... by tompazourek on Friday May 21, 2021 @12:22PM (#27236088)
All models are wrong, but some are useful.
Re:The hard part of Enterprise Software is the Enterprise, n... by kspacewalk2 on Thursday May 20, 2021 @11:22AM (#27222334)
>I commented earlier on another thread about enterprises being intent on very specific implementations and premature optimisation, which leads to very bespoke and therefore expensive software.

This is often because enterprises look at total cost, whereas you're focused on software cost.

>We have a customer who "needs" to see their branches "scores" on the main dashboard regardless of the fact they could get that data somewhere else. We had to build a feature to win this customer that is only used by them and now have to maintain it forever.

Depending on the size of this customer, the frequency of an employee needing this stat, and the amount of seconds/minutes saved per lookup, productivity/salary costs of not implementing this feature might easily dwarf paying someone to maintain it.

Re:The hard part of Enterprise Software is the Enterprise, n... by orev on Thursday May 20, 2021 @11:58AM (#27222863)
> the amount of seconds/minutes saved per lookup, productivity/salary costs

Let’s not kid ourselves into thinking that decisions like this are made using an objective cost/benefit comparison with all data fully and accurately collected. The fact is that things like this happen because a decision-maker just demands it. It doesn’t mean it makes logical sense, other than the salesperson needed to agree to it in order to close the deal.

Re:The hard part of Enterprise Software is the Enterprise, n... by knightofmars on Friday May 21, 2021 @11:10AM (#27235050)
Yes, 100%. A salesperson on commission does not care about the long-term maintenance costs of a decision of this nature. And I don't blame them, it's not something they should care about. A product owner? They may care if they're actually invested (stock options, co-ownership, etc) but they also may just leave after a few years after a better offer comes along or a buyout happens. A software engineer? It's the same as the product owner, they may care for some period but why not just leave when a better offer comes along.

I've pondered this issue as the "Peter Gibbons" problem. Why would anyone in the chain of software development care about the software itself? There's no incentive to consider the long-term cost impact of implementing a custom feature because you can always just find a new job if the product gets unwieldy.

Re:The hard part of Enterprise Software is the Enterprise, n... by atatatat on Thursday May 20, 2021 @11:36AM (#27222523)
Right. That requires a slight increase in cost. One time very large, or ongoing.
Re:The hard part of Enterprise Software is the Enterprise, n... by jfengel on Friday May 21, 2021 @11:39AM (#27235453)
The aggravating thing is that often, having demanded the feature, they discover that they didn't really want it in the first place.

I try not to argue with a customer, because they do know their business better than I do. But I know the software better than they do, including its intended use model. The former usually takes precedence over the latter, if for no other reason than that they have the money and I don't. But if they're not paying for it directly, and want me to do it on spec... hard decisions get made.