News for hackers. Stuff that matters.
Re:Build versus Buy by teddyh on Monday April 13, 2020 @02:05PM (#22858267)
“If it’s a core business function — do it yourself, no matter what.”

— Joel Spolsky, In Defense of Not-Invented-Here Syndrome: https://www.joelonsoftware.com/2001/10/14/in-defense-of-not-...

Re:Build versus Buy by kstrauser on Monday April 13, 2020 @02:44PM (#22858664)
I've worked at Not-Invented-Here shops and it was annoying that the Powers That Be didn't want to use a COTS solution. As much fun as it would be to reinvent DynamoDB, that's not actually going to help our business.

However, even more annoying is working at a Never-Invented-Here organization. I've been at a place which hired brilliant people, but then didn't let them innovate on pretty much anything. Write a simple TCP listener in Python to read a stream of data and then reply to it? That's crazy talk! We need to write a full Django app and deploy it behind Nginx behind a load balancer so that we can pretend it's highly available!

Don't get me wrong: the off the shelf approach is usually the right thing, but sometimes it just adds complication where it didn't need to be. It's insulting to be told you were hired for your expertise, but then not be allowed to actually use it.

Re:Build versus Buy by Ididntdothis on Monday April 13, 2020 @03:08PM (#22858976)
“Write a simple TCP listener in Python to read a stream of data and then reply to it? That's crazy talk!”

This has infected my company quite a bit. People get really nervous as soon as you write something that’s little novel. Writing everything from scratch is bad but you also need room for people to innovate.

Re:Build versus Buy by pm90 on Monday April 13, 2020 @08:40PM (#22861722)
It’s shifting the complexity from development to operations ( or “gluing shit” as a sibling has pithily observed.

I’ve found this to be common in places with lower engineering skills. The “engineers” are mortally afraid of building anything novel for fear of failure; the COTS approach can get many clever folks pretty far in their career.

Re:Build versus Buy by TurboHaskal on Tuesday April 14, 2020 @05:55AM (#22864187)
NIH and concrete over generic solutions all the way, before you end up in the soulless hamster wheel of constantly upgrading 3rd party software.
Re:Build versus Buy by jedberg on Monday April 13, 2020 @02:09PM (#22858309)
Don't take the wrong message from Joel here though. Make sure it's actually a core business function. Is it something that will actually give you a competitive advantage if you do it better than everyone else?
Re:Build versus Buy by jpdb on Monday April 13, 2020 @03:31PM (#22859177)
> Is it something that will actually give you a competitive advantage if you do it better than everyone else?

I think you also need to evaluate if it can even be done better than everyone else, and the effort required to do so.

Re:Build versus Buy by ska on Monday April 13, 2020 @04:55PM (#22859862)
Sure, but that's sort of the entire point of your business.

Joel's quote is more narrow, which is a subset of the dangers of being completely reliant on someone else for your business.

Re:Build versus Buy by ternaryoperator on Monday April 13, 2020 @03:20PM (#22859075)
Except encryption. You don't want to roll your own at all.
Re:Build versus Buy by yjftsjthsd-h on Monday April 13, 2020 @03:58PM (#22859394)
I think the advice holds. Cryptographic primitives are vanishingly unlikely to be your core business, even if the things built on them are. Therefore, almost nobody should be building them.
Re:Build versus Buy by kstrauser on Monday April 13, 2020 @04:00PM (#22859415)
Super important exception. Thanks for mentioning it!

Unless you've spent the last 10+ years working on encryption full time, please don't try it yourself.

I used to think I could write crypto. Then I learned more and realized it needs specialized knowledge I don't have the time to acquire. Then I spent some time trying to acquire it and figured I was OK to try again. Then I watched many other more experienced organizations crash and burn. My current position is that I know enough about crypto to know I never want anything to do with authoring it.

Re:Build versus Buy by ska on Monday April 13, 2020 @05:01PM (#22859911)
I don't think that's an exception. It's just that encryption isn't actually core functionality for most businesses (even some that think it is).

And if it is core functionality, you should have staff qualified to roll their own, and you should all know why you are doing this (i.e. what differentiation you are going after). This really isn't limited to encryption, it's just a hard domain that bumps up against a lot of other domains, so you see more failures than some others.

Basically if you are going to build a startup or new program in a hard domain, you need to have the resources to do it properly, and you need to know what those are before you start. This is where being a team of smart and motivated individuals may just not be enough.

Re:Build versus Buy by aledalgrande on Monday April 13, 2020 @04:33PM (#22859708)
I'd argue that in a startup, at a very early stage, you can use external services even for core functions, if they work well enough.

Look at Intercom: now it's a juggernaut, but it started as an API mashup with a UI in front of it. If you can hit the market and start getting revenue faster you should. Many services have pay as you go and/or startup discounts.

That's your launch platform, then you start working from there.