4 ms·
>Management liked it because it “saved a lot of money”… as long as you ignore the cost of the time we lost to dealing with it. bean counters tend to not evalua
by dylan604 3y ago
>Management liked it because it “saved a lot of money”… as long as you ignore the cost of the time we lost to dealing with it.
bean counters tend to not evaluate your time as lost money. they are paying you anyways, so sunk cost fallacy or something. as long as they are not having to pay an invoice, they are "saving" money
- uoaei 3y agoIt's the converse of Goodhart's law -- if it's not measured/itemized, it's not part of the objective function for optimizing (costs).
- EddieEngineers 3y agoAbsolutely. The number of times I’ve pointed out a paid tool for $10pm is cheaper than a days salary per month to build in-house and maintain…
- ownagefool 3y ago10 in total or 10 per seat? SaaS mostly exists to extract profits perpetually. This doesn't mean it's not sometimes worth it, but when you add all the licenses together, there tends to be considerable savings if you're willing to self-host. In reality both sides of the debate are often wrong.
- EddieEngineers 3y agoThe one I think about was when I was building a 3D model of a new office in Unity and the options were either purchasing a material or trying to design one myself with basically 0 experience of doing so. Something like $40 for the material or however long it'd take me to work it out. The $10 option was genuine though, it was for some SaaS tool to monitor endpoints and text if things broke (about 9 years ago when I had basically zero coding experience) - so just one seat, or me trying to hack something together with text/email notifications and a nice UI. Even now I'd probably still prefer using something like that over writing something in-house, although I'd be more happy to look at self-hosting an open source option.
- deleted 3y ago[deleted]
- PragmaticPulp 3y agoI’ve had the opposite experience in recent years: Excess management and limited engineers leads to a desire to do deals, make contracts, and buy external solutions for everything. In many cases the integration costs are assumed to be $0 and we spent more time trying to make an external tool do something that could have been built in house in the same or less time.
- llanowarelves 3y agoAnd we can expect it to continue going that way for smaller companies, since the tax changes in the US wrt R&D means it's better to buy than build, all else being equal, due to the tax deduction not having to be spread over time.
- JohnBooty 3y agowe spent more time trying to make an external tool do something that could have been built in house in the same or less time. Yeah. :-/ There's also a version of the "nobody ever got fired for choosing IBM" fallacy/truism at work, right? If management picks $WELL_KNOWN_PRODUCT_XYZ and things go sideways... well, they don't look foolish. But if they rely on... some random in-house engineer and things don't work out, they look like fools. (Even though, in both cases, it actually just comes down to the same in-house engineers. Because the in-house engineers still need to do the integration work)
- xmcqdpt2 3y agoIn my thankfully short time at a company that operated this way, there was no upside either. No decent engineer would stay there because there was nothing to build and management would always just contract out everything. Management, which was promoted internally from bad engineers, couldn't shop a good SaaS product or consulting firm and instead were consistently convinced into buying shitty Oracle products. In-house products were badly done, which led to contracting out engineering, which led to no engineers, which led to getting screwed in the contracting. Fixing that company would probably involve firing the whole tech department.