News for hackers. Stuff that matters.
Re:The shittiest project I ever worked on (2013) by CPLX on Friday May 24, 2019 @10:08AM (#20001645)
I've had this same thought, and have a pet theory about it. I think the answer is something like momentum is so unbelievably useful in business that having it is enough to be immensely wealthy and successful.

As someone who recently created yet another startup, I am reminded daily that literally everything I do has to be done for the first time. It's like molasses covering every part of the machine. When a client needs a proposal you have to write one from scratch, when someone wants payment terms or to negotiate a contract adjustment you have to figure out contract language. You don't have expense reimbursement forms, you don't have job descriptions, you don't have anything to use as a starting point or template for anything you do.

Big companies have all that. They have clients that are planning on using them again this year. They have meetings they took two years ago that are about to be a sale. They have a guy on the third floor that has seen this problem they're about to have once and knows how to avoid it. People instinctively trust them, so they don't have to explain themselves as much. People instinctively fear them, so their contracts get upheld. People that used to work for them now work at potential customers and call them up.

And on and on and on. Having a slightly busted software development process is, in fact, peanuts compared to all this.

Or, perhaps another way to say it is that there's a lot of different kinds of "software" besides the digital ones-and-zeroes kind we think about here. A group of humans all organized around a business purpose with tons of experience and momentum is a high functioning machine as well.

Re:The shittiest project I ever worked on (2013) by rossdavidh on Friday May 24, 2019 @10:17AM (#20001760)
This theory, by the way, explains why efforts to turn around failing large companies are so rarely successful. Once that momentum is a bunch of bad decisions, etc. the momentum is working against you. But, up until that point, it is extremely powerful.
Re:The shittiest project I ever worked on (2013) by eldavido on Friday May 24, 2019 @08:23PM (#20006362)
It's worth thinking about how companies become #1 in their respective industries.

A local restaurant becomes #1 by having the best food and/or location, and providing it at a price people are willing to pay.

A car dealership probably succeeds by having the best prices on cars and the best customer service.

Most banks compete on customer service and some amount of product differentiation.

Insurance is some combination of customer service, market share, and correctly pricing things.

To the extent that better software contributes to these core "capabilities", companies will invest in it. Investment means it gets management attention, willingness to spend, willingness to hire annoying top-shelf talent that demands flexible working arrangements and huge salaries.

Many -- maybe most -- business don't have competitive dynamics that software enhances. A hotel is a great example: it's location, price, service, and cost control. The software they use at the front desk has approximately zero importance to whether the place will stay in business, or fold. Owners are right to invest as little as possible in it and move on to something more important, like building a brand.

Re:The shittiest project I ever worked on (2013) by pergadad on Sunday May 26, 2019 @02:54AM (#20013530)
I think you're far too optimistic about why certain companies succeed and others don't. It's much more random than that. Why does the restaurant succeed? Rugby review at the right time, a big regular corporate client, a good cook that works for less than she'd usually take because her mother lives right next door, ...
Re:The shittiest project I ever worked on (2013) by tmaly on Friday May 24, 2019 @11:41AM (#20002690)
This idea of momentum reminds me of Jim Collins Flywheel Effect

https://www.jimcollins.com/concepts/the-flywheel.html

I have to disagree with the broad statement that a busted software development process is peanuts. In highly regulated industries like finance, bad software can cost you billions in fines from regulators.

In these industries, they have to invest in technology and good processes if they want to stay in business.

Re:The shittiest project I ever worked on (2013) by w0utert on Friday May 24, 2019 @12:01PM (#20002888)
High-tech is similar. Where I work there are literally 100s of insanely bright people with backgrounds in math, physics, etc. who struggle for years to get their ideas into results and (ultimately) products. Usually things get stuck on simple software tasks like connecting things together, driving them in a feedback loop, or just identifying that all the parts are already there, scattered around the company, and someone just needs to write a framework to put them together. I honestly think huge business opportunities are lost because of inefficient software development processes.

In a sense, this lends credence to the theory that once you’re big and powerful and have lots of clients, you can afford to lose these opportunities. But I still think that you would have a huge competitor advantage without all the molasses.

Re:The shittiest project I ever worked on (2013) by edubs25 on Friday May 24, 2019 @03:31PM (#20004625)
> In highly regulated industries like finance, bad software can cost you billions in fines from regulators.

You're assuming the regulators are low-level enough to identify a flawed system. A lot of regulations are applied at a policy level (aka process level) and auditors (internal or external) are not always able to identify severe gaps between what's documented in a policy and reality of day to day. Good people and technology matter way more than process.

Re:The shittiest project I ever worked on (2013) by bumby on Friday May 24, 2019 @04:46PM (#20005134)
A good process is supposed to protect you from not having good people (or, at least people who can't be good every day).

Sure, if we hire perfect people there's no reason to even have a process. In reality, when that breaks down you have to rely on your process to close those gaps. But, like you said, a policy/process is only as good as the paper it's printed on if nobody follows it.

Re:The shittiest project I ever worked on (2013) by edubs25 on Tuesday May 28, 2019 @12:39PM (#20031789)
edit I'm using security as an example of a regulated aspect of software/IT systems. I am aware there are others.

100% agree - My point was more that regulators tend to use policy and process artifacts as proof of security compliance. The idea that more highly regulated/audited IT sectors are inherently better at security is probably false. The audits just aren't stringent/detailed enough and there's aren't enough incentives for executives/boards to do more than the minimum. Which is why the values/opinions/ethics of those decision makers becomes key.

The most secure 'company' I worked for was a large research university because it was a priority from the director and we were constantly getting probed by overseas IP addresses. On the other hand, the worst company I worked at in terms of security was in the payment processing world. We were PCI DSS compliant and audited almost continuously by various interested parties (banks, card brands, third parties, etc.). I don't think any of our people were bad/inept but at the end of the day our policy artifacts made us sound/appear way more compliant than we were. The problem was upper management didn't care (allow us time or $$) about closing the gaps in implementation unless we failed audits or pen testing. We didn't fail but no one in IT thought we were doing enough. We didn't have enough auditing and regularly had inexplicable 'bugs' reported that honestly could have been evidence of network intrusion but we had no proof either way.

Re:The shittiest project I ever worked on (2013) by rossdavidh on Friday May 24, 2019 @03:27PM (#20004591)
It is incredibly important in those industries, BUT...it is also for those same reasons more change-averse. Most (granted, not all) of the time, using the same software that worked just ok last year, is far safer than getting new software made.

The safest decision, 99% (but not 100%) of the time, is to cancel that software project before it goes to production, because if you've been successful up to now, by definition you have software that is Good Enough (if not good). So, in highly regulated industries, changing your software may very well be an unwise decision.

Not least because, if it's the same software the regulators were ok with last year, they probably won't fine you billions for using it this year.

Caveat to all of the above: "probably". But the chance of new software getting you into trouble is still higher.

Re:The shittiest project I ever worked on (2013) by eldavido on Friday May 24, 2019 @08:25PM (#20006370)
Funny enough, I can think of very few businesses that went under due to fines from regulators.

Most businesses fail because they don't have customers, not because they're inefficient or badly-managed.

They key is right there in your statement: "have to". Good places to work don't build software because they "have to", they do it because it's viewed as an important competitive differentiator and execs WANT to spend on it.

Re:The shittiest project I ever worked on (2013) by technologic on Thursday May 30, 2019 @08:25AM (#20050433)
as a wise person once told me, go where you're appreciated, not where you're tolerated (theres obvious limits to this)
Re:The shittiest project I ever worked on (2013) by nexus2045 on Sunday May 26, 2019 @08:12PM (#20018503)
His recent podcast with someone whose name HN hates was unbelievably informative and inspiring. Also talks about the flywheel applied to his own life.
Re:The shittiest project I ever worked on (2013) by PhasmaFelis on Friday May 24, 2019 @12:46PM (#20003285)
What is a "comparison company" in that article?
Re:The shittiest project I ever worked on (2013) by tmaly on Friday May 24, 2019 @01:49PM (#20003780)
In that context, a comparison company, would be a company that tries one big push to move the flywheel. This is not enough to build momentum. You need repeated effort to build the momentum.
Re:The shittiest project I ever worked on (2013) by tarsinge on Friday May 24, 2019 @04:10PM (#20004868)
I got more involved in the sales aspect recently and I find the part about trust especially true. Company size and references has a disproportionate effect compared to the reality of their reliability. A lot of big service companies fail to deliver, yet it doesn't seem to have an impact on future buyers. We all heard the phrase "nobody ever go fired for buying <market leader>" but only recently it started to resonate for me, and experiencing first-hand that when you are buying software in a bureaucratic environment you are not incentived to buy the best solution, but to minimize your responsibility in case of failure.
Re:The shittiest project I ever worked on (2013) by HillRat on Friday May 24, 2019 @06:00PM (#20005664)
Weirdly enough, one little-stated aspect of that dynamic is that as a client you can sue a major consulting or services firm for delivery failure and expect to get something out of it, whereas that option is rarely available for smaller firms that can’t absorb the cost of a single lawsuit.
Re:The shittiest project I ever worked on (2013) by linuxftw on Friday May 24, 2019 @11:01AM (#20002229)
Good analysis.

I think for software sales, this type of thing is slowly fading as it becomes more and more commoditization. For all but the largest of businesses, you go to AWS and pay the market price for compute and other services, there's not much need for contracts and negotiations and meetings, the price is the price. Going to a competitor or doing business the old way simply costs much more. Eventually, businesses align on consuming commodities as commodities, the spending slowly moves from CapEX to OpEX.

AWS is the power company now. You agree to their terms, and you pay their bill. Unless you're doing a major industrial facility that requires mega-watts of power, you don't need to interact with their sales staff; same applies to AWS (and ironically, you can probably use power as a proxy to relative deal size here, too).

100 years from now, all the conceivable software is going to exist that could exist, at least for 'business processes.' If your business is selling potatoes as a farmer to distributor, the software you need to participate efficiently in that market will already exist.

Re:The shittiest project I ever worked on (2013) by nullwasamistake on Friday May 24, 2019 @11:25AM (#20002501)
The upper end of the market is still contracts all the way down. My company has around 250 employees and every single service we use, software and otherwise, is a negotiated old school contract.

The market price isn't what most companies pay. If you pay significant amounts to Amazon (maybe 1 employee salary worth) you're screwing yourself if you don't negotiate lower rates

Edit: Just asked the corporate overlords. It's actually against our finance rules to pay for any recurring service charge without a negotiated contract.

Re:The shittiest project I ever worked on (2013) by luckydata on Friday May 24, 2019 @12:06PM (#20002936)
You're still paying market price, just not the published one. Negotiating b2b deals is a little like ordering from the secret menu at in&out. Doing tons of that lately and it's quite the mechanical endeavor. The only really annoying part of it is deals move only as quickly as the sales drones want it to. I have to sit through their "sales process" even if I know exactly what I want, I know what I can spend and ultimately the deal will be done on my terms. It's funny to think that some guy got high fived to death for selling me a contract for about 35% the original quote.
Re:The shittiest project I ever worked on (2013) by ErikAugust on Friday May 24, 2019 @05:39PM (#20005520)
He’s being high-fived because you could have got it for 10% of the original quote.
Re:The shittiest project I ever worked on (2013) by madhadron on Friday May 24, 2019 @12:10PM (#20002976)
> It's actually against our finance rules to pay for any recurring service charge without a negotiated contract.

Your company probably also employs a professional shark whose job it is to squeeze the blood out of every stone he is pointed towards. With even a modest number of sizeable contracts, such a person would pay for themselves very easily.

Re:The shittiest project I ever worked on (2013) by mruts on Friday May 24, 2019 @12:31PM (#20003164)
At my old company we were paying millions for contracts and software we didn't use or really didn't mean. One of the analysts volunteered to be the "undertaker" and renegotiate. After a year of screaming at people on the phone (I sat next to him), he managed to save us around a million dollars, which was around a 60% savings. He pocketed maybe 30% of the money saved that year. Not bad for a year of being a dick.
Re:The shittiest project I ever worked on (2013) by nullwasamistake on Friday May 24, 2019 @05:04PM (#20005281)
Yup I know one of them, we have a couple sales sharks that do it when they're not busy attacking potential customers
Re:The shittiest project I ever worked on (2013) by linuxftw on Friday May 24, 2019 @02:02PM (#20003888)
Technically speaking, you might enter into a contract with the power company. The 'negotiation' probably goes like this: Power Company: "You'll pay public rates on the same terms as literally every other customer" Your Company: "Deal!"
Re:The shittiest project I ever worked on (2013) by Ice_cream_suit on Saturday May 25, 2019 @02:36AM (#20007467)
Power companies give significant discounts to large customers.
Re:The shittiest project I ever worked on (2013) by istjohn on Friday May 24, 2019 @04:26PM (#20004970)
>100 years from now, all the conceivable software is going to exist that could exist, at least for 'business processes.' If your business is selling potatoes as a farmer to distributor, the software you need to participate efficiently in that market will already exist.

I disagree. Unless we're talking about Artificial General Intelligence or some other general purpose technology, I think bespoke software will always be better--if not more cost effective--than off-the-shelf.

Re:The shittiest project I ever worked on (2013) by amelius on Friday May 24, 2019 @11:57AM (#20002842)
It's not just momentum in that sense; it's also the fact that wealth begets wealth. (Which you could also call momentum in a way.)
Re:The shittiest project I ever worked on (2013) by thfuran on Friday May 24, 2019 @02:44PM (#20004200)
That seems to be begging the question.
Re:The shittiest project I ever worked on (2013) by sanderjd on Friday May 24, 2019 @09:48PM (#20006631)
Having recently transitioned from small companies and start ups to a big successful corporation, this all seems right to me. A lot of things are way easier because they were just figured out already. A lot of stuff (both technical and non-technical) has already been in the pipeline for a few years and will be ready pretty soon. A related thing is that because of that pipeline thing, it's a lot easier to start thinking about things that may well take two or three years to come to fruition. These are all enormous advantages.

On the other hand, there are entire markets, even quite large ones, that you can't pursue because they're way too small. That's what I'd look for if I were thinking about starting a new business.

Re:The shittiest project I ever worked on (2013) by 317070 on Friday May 24, 2019 @01:54PM (#20003814)
I think this is indeed nailing it. Companies are inefficient, but they get away with it because the market is even more inefficient.
Re:The shittiest project I ever worked on (2013) by istjohn on Friday May 24, 2019 @04:17PM (#20004909)
I just want to point out that "Companies are inefficient, but they get away with it because the market is even more inefficient." is not at all what GP wrote.
Re:The shittiest project I ever worked on (2013) by 317070 on Sunday May 26, 2019 @05:25PM (#20017642)
Momentum and delay is a market inefficiency. The most efficient market is instantaneous.