4 ms·

You're confusing a developing thinking their code is well written with a tech team evaluating the value, reliablity and flexibility of a system. The 'common fr

You're confusing a developing thinking their code is well written with a tech team evaluating the value, reliablity and flexibility of a system. The 'common framework' approach works great if you've solving a common problem. That's why we use libraries for certain modules or functions of a system. When your business is, even just operationally, different in some way, bespoke is often the best way. Make it good and it doesn't matter a sniff if it's an established public framework or not.

woojoo666 4y ago
> When your business is, even just operationally, different in some way, bespoke is often the best way. Make it good and it doesn't matter a sniff if it's an established public framework or not. There was a post recently on hackernews talking about how startups have an "innovation limit". That is, if you try to innovate too much, your scope grows beyond your reach. I think the idea applies here as well. Building everything yourself takes a lot of time. If you can position yourself to leverage the advancements of others, you can move much faster.
- breakfastduck 4y ago
  Absolutely. I am a big force in my place of 'just buy' when others are all 'build everything in house'. If there's no genuine advantage of having something custom then don't do custom, buy something that works.
chii 4y ago
> When your business is, even just operationally, different in some way, bespoke is often the best way. most business think themselves different, esp. in their IT infrastructure. It's closer to hubris imho. If you have an internal/back office app, it doesn't require a custom UI framework to be created. The only place where a custom framework should be created is if the domain of the software is custom.
- breakfastduck 4y ago
  I'm not talking about back office admin systems. I'm talking about genuine business operations systems. And YES, most are more different than they appear on face value.

woojoo666 4y ago

> When your business is, even just operationally, different in some way, bespoke is often the best way. Make it good and it doesn't matter a sniff if it's an established public framework or not. There was a post recently on hackernews talking about how startups have an "innovation limit". That is, if you try to innovate too much, your scope grows beyond your reach. I think the idea applies here as well. Building everything yourself takes a lot of time. If you can position yourself to leverage the advancements of others, you can move much faster.

breakfastduck 4y ago
Absolutely. I am a big force in my place of 'just buy' when others are all 'build everything in house'. If there's no genuine advantage of having something custom then don't do custom, buy something that works.

chii 4y ago

> When your business is, even just operationally, different in some way, bespoke is often the best way. most business think themselves different, esp. in their IT infrastructure. It's closer to hubris imho. If you have an internal/back office app, it doesn't require a custom UI framework to be created. The only place where a custom framework should be created is if the domain of the software is custom.

breakfastduck 4y ago
I'm not talking about back office admin systems. I'm talking about genuine business operations systems. And YES, most are more different than they appear on face value.