Next, ask if they’ve scoped out third-party libraries (i.e., plug-ins and APIs) that can be used off the rack, so the programming team isn’t reinventing the wheel on your dime.
I have heard this myth over and over again. Taking things off the rack in a lot of cases creates does not guarantee good end result. Sometimes the 3rd party libraries causes more problems than if you would have built it yourself.
Sometimes you need to reinvent the wheel because none of the wheels are designed to fit your specific needs.
The choice to use 3rd party libraries or design it yourself all depends on the nature of the project and the quality of the developers. Now how do you know when to build it yourself or use 3rd party libraries, you look how your project proceeds. If the 3rd party library slows you down or it takes too long to find one that fits your need then reinvent the wheel.
It says scoped out, meaning evaluated what was there and decide if you need to do it yourself or not. Just because you've checked what's available doesn't mean you have to use it... but it's important that you know what's out there.
Better advice on how much you need to know about tech, everything or nothing. If your IT isn't critical outsource it or buy services, your business is something else do that instead. Also if IT isn't critical to your business be aware that at some point someone has or will solve the fundamental technical problem of your business and will out compete you so thoroughly that it will be like you aren't even there, hope this happens not in your lifetime. If your business revolves around tech the minimum amount you need to know is everything. Otherwise its not your business it belongs to your IT, they leave then you're boned, they're incompetent you're boned, they decide to go into business for themselves you're boned. Figure out which category you are in and then embrace it.
7 comments
2 u/roznak 11 Oct 2015 03:27
I have heard this myth over and over again. Taking things off the rack in a lot of cases creates does not guarantee good end result. Sometimes the 3rd party libraries causes more problems than if you would have built it yourself.
Sometimes you need to reinvent the wheel because none of the wheels are designed to fit your specific needs.
The choice to use 3rd party libraries or design it yourself all depends on the nature of the project and the quality of the developers. Now how do you know when to build it yourself or use 3rd party libraries, you look how your project proceeds. If the 3rd party library slows you down or it takes too long to find one that fits your need then reinvent the wheel.
2 u/Chris_E 11 Oct 2015 04:51
It says scoped out, meaning evaluated what was there and decide if you need to do it yourself or not. Just because you've checked what's available doesn't mean you have to use it... but it's important that you know what's out there.
2 u/nicky_haflinger 11 Oct 2015 05:27
Better advice on how much you need to know about tech, everything or nothing. If your IT isn't critical outsource it or buy services, your business is something else do that instead. Also if IT isn't critical to your business be aware that at some point someone has or will solve the fundamental technical problem of your business and will out compete you so thoroughly that it will be like you aren't even there, hope this happens not in your lifetime. If your business revolves around tech the minimum amount you need to know is everything. Otherwise its not your business it belongs to your IT, they leave then you're boned, they're incompetent you're boned, they decide to go into business for themselves you're boned. Figure out which category you are in and then embrace it.
0 u/DickHertz 21 Oct 2015 09:57
A+
0 u/clickbot 11 Oct 2015 10:07
TL;DR: Nothing, ask your devs.