9 ms·

This is a variation on the "build vs. buy" question that has been active in IT for decades. And answered for decades, too. Building something yourself makes sen

This is a variation on the "build vs. buy" question that has been active in IT for decades. And answered for decades, too. Building something yourself makes sense only when that something drives the unique value prop from your business. But if your needs are something that is more generic, buy it. So it all comes down to what you said about operating in a specific niche. If that niche is your value prop, and the reason software is difficult for you, then yes, in-house it and build what you need. As far as retaining talent, money talks. Put a number on the value that solid software would bring to your business, and if that number can support compensating a software team at market rates or higher, you have the potential to retain a team. However, it also needs to be a good team -- solid leadership, with a culture that matches what is expected by software devs: respect, autonomy, flexibility, and trust. If all of that sounds reasonable, go forth and build. If not, accept the struggle of having to buy.

from-nibly 2y ago
Yes, and also when you hire software developers you want someone who understands that they are running internal tools which is COMPLETELY different from building consumer apps. Simplicity is key. Keep the team small and lean. Also the build vs buy decision has to be made with every feature. If its not your competitive advantage just buy it. Dont make a new database, just use postgres etc. There are a different set of developers that can navigate through this than the ones who will reinvent the wheel if they can.
- theshrike79 2y ago
  This is a huge thing. Way too many internal teams build their tooling "too well", to a point where it could be a separate startup product in itself with a tiny amount of extra work. Like game companies writing their own engine and ending up as a game engine company eventually =)
  - heraldgeezer 2y ago
    >Like game companies writing their own engine and ending up as a game engine company eventually =) This used to be standard. PS1 and PS2 was coded in Assembly basically. No OS. All games had "drivers" in them. There was only renderware as a ready-made engine. Every Final Fantasy game was a new engine, FFX and FFXII are 2 very different engines. Bespoke only for that game. And beautiful. Same with RE4. Same with God of War 1 and 2. Unbelievable. Same with xbox and gamecube. Even in the 365 era, the Halo games were its own engine. Look back at the dark Unreal 3 period 2006-2010. Most UE3 games looked like shit. A brown bloomy mess.
- codingdave 2y ago
  Yes, those are great points. You'd really want a team of devs who have worked in the enterprise IT world, as that is the business environment we're talking about here. You'd want a group who will get everything working, coding only what is needed, and integrating other solutions when the feature is a commodity. Code is an important tool, and also a liability. Hire devs that understand that.
loa_in_ 2y ago
Software developers are the blacksmiths of this century.

from-nibly 2y ago

Yes, and also when you hire software developers you want someone who understands that they are running internal tools which is COMPLETELY different from building consumer apps. Simplicity is key. Keep the team small and lean. Also the build vs buy decision has to be made with every feature. If its not your competitive advantage just buy it. Dont make a new database, just use postgres etc. There are a different set of developers that can navigate through this than the ones who will reinvent the wheel if they can.

theshrike79 2y ago
This is a huge thing. Way too many internal teams build their tooling "too well", to a point where it could be a separate startup product in itself with a tiny amount of extra work. Like game companies writing their own engine and ending up as a game engine company eventually =)
- heraldgeezer 2y ago
  >Like game companies writing their own engine and ending up as a game engine company eventually =) This used to be standard. PS1 and PS2 was coded in Assembly basically. No OS. All games had "drivers" in them. There was only renderware as a ready-made engine. Every Final Fantasy game was a new engine, FFX and FFXII are 2 very different engines. Bespoke only for that game. And beautiful. Same with RE4. Same with God of War 1 and 2. Unbelievable. Same with xbox and gamecube. Even in the 365 era, the Halo games were its own engine. Look back at the dark Unreal 3 period 2006-2010. Most UE3 games looked like shit. A brown bloomy mess.
codingdave 2y ago
Yes, those are great points. You'd really want a team of devs who have worked in the enterprise IT world, as that is the business environment we're talking about here. You'd want a group who will get everything working, coding only what is needed, and integrating other solutions when the feature is a commodity. Code is an important tool, and also a liability. Hire devs that understand that.

loa_in_ 2y ago

Software developers are the blacksmiths of this century.