Top Banner
37

Not Invented Here

Jul 04, 2015

Download

Technology

Fredrik Kalseth

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."
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Not Invented Here
Page 2: Not Invented Here

«Not Invented Here»

Page 3: Not Invented Here

culture that avoids using or buying already existing

knowledge

Page 4: Not Invented Here
Page 5: Not Invented Here
Page 6: Not Invented Here
Page 7: Not Invented Here
Page 8: Not Invented Here
Page 9: Not Invented Here

«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

Page 10: Not Invented Here
Page 11: Not Invented Here

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

Frans Bouma

Page 12: Not Invented Here

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

Jeremy D. Miller

Page 13: Not Invented Here
Page 14: Not Invented Here
Page 15: Not Invented Here

What is your

Competitive advantage?

Page 16: Not Invented Here

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

Page 17: Not Invented Here

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

Page 18: Not Invented Here

Example:

The cost of rolling your own ORM

Page 19: Not Invented Here
Page 20: Not Invented Here
Page 21: Not Invented Here
Page 22: Not Invented Here
Page 23: Not Invented Here
Page 24: Not Invented Here
Page 25: Not Invented Here
Page 26: Not Invented Here
Page 27: Not Invented Here
Page 28: Not Invented Here
Page 29: Not Invented Here
Page 30: Not Invented Here
Page 31: Not Invented Here
Page 32: Not Invented Here

Challenge:

Managing all your (new) dependencies.

Page 33: Not Invented Here
Page 34: Not Invented Here

Web Platform Installer (+MSDeploy+WebDeploy)

Page 35: Not Invented Here

In summary…

Page 36: Not Invented Here

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

Page 37: Not Invented Here

Thank you for the attention!