Not Invented Here

Post on 04-Jul-2015

314 Views

Category:

Technology

3 Downloads

Preview:

Click to see full reader

DESCRIPTION

Slides from presentation at MSDN Live talks in March 2011. Norwegian blurb:"Utviklere elsker å finne opp hjulet på nytt. Noen ganger kan det være nødvendig, men er vi bevisste på konsekvensene det har når vi velger å rulle våre egne rammeverk? Det er på tide å ta et oppgjør med “not invented here”-kulturen, og lære mer om det store økosystemet av komponenter og rammeverk som er tilgjengelig på .NET-plattformen. Ruby-verdenen har hatt stor suksess med gems, og tilsvarende verktøy på .NET-plattformen gjør det nå enklere enn noensinne å bruke 3. parts-biblioteker i prosjektene våre."

Transcript

«Not Invented Here»

culture that avoids using or buying already existing

knowledge

«When you're working on a really, really

good team with great programmers,

everybody else's code, frankly, is bug-infested

garbage, and nobody else knows how

to ship on time.»

- Joel Spolsky

“No customer should accept that the team hired (…) has spent time writing for example a grid control.”

Frans Bouma

“If you’re writing ADO.NET code by hand, you’re stealing from your employer or client.”

Jeremy D. Miller

What is your

Competitive advantage?

Business value The features that make your users more productive with your system than without it.

Infrastructure The fundamental structures valuable features are built on top of.

Example:

The cost of rolling your own ORM

Challenge:

Managing all your (new) dependencies.

Web Platform Installer (+MSDeploy+WebDeploy)

In summary…

Will building it yourself give

you a competitive advantage?

Consider doing it in-house.

Pick one of the dozen frameworks out there and get on with the important

stuff!

Yes No

Thank you for the attention!

top related