To be or not to be...a DNN module
•
0 likes•495 views
The document discusses technical debt in DNN module development. It covers topics like what technical debt is, how developers can get into messy code, and a better way to think about content management systems. The presentation also describes services available within DNN and provides contact information for the presenter.
Report
Share
To be or not to be...a DNN module
- 1. To Be or Not to be ..... a DNN Module Tuesday, April 16, 13
- 2. Thanks to all our Generous Sponsors! Tuesday, April 16, 13
- 3. What We’ll Cover • What is Technical Debt • Other module developers code • How you get yourself into a mess • A better way to think about a CMS • DNN Services Tuesday, April 16, 13
- 4. What IsTechnical Debt n = Number of resources required R = Rate (hourly average) of resource H = Hours required C = Costs associated with benefits, payroll, recruitment (usually ~40% of hourly rate) HC = Hardware Costs SL = Software Licenses MI = Migration and Implementation expenses (e.g. consulting engagements, training, etc) Technical debit = borrow time against a future date Tuesday, April 16, 13
- 5. Other Module Developers Code Tuesday, April 16, 13
- 6. How you Get Into a Mess Tuesday, April 16, 13
- 7. Public Fans Officials Schools Coaches Staff Tuesday, April 16, 13
- 8. How long to load? Tuesday, April 16, 13
- 9. The Current Solution Tuesday, April 16, 13
- 10. A Better WayToThink about a CMS Tuesday, April 16, 13
- 11. Public Directors Staff Tuesday, April 16, 13
- 12. Services within DNN Tuesday, April 16, 13