1 / 47

Bare-knuckle web development

Bare-knuckle web development. NDC 2013 Johannes Brodwall, Chief scientist Exilesoft Global. Bare-knuckle philosophy Demonstration of bare-knuckle web in .NET Conclusions. Part I:. The bare-knuckle philosophy. Fear => Pair Hubris => Speed (and fun). High impact with low ceremony.

caesar
Download Presentation

Bare-knuckle web development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bare-knuckle web development NDC 2013 Johannes Brodwall, Chief scientist Exilesoft Global

  2. Bare-knuckle philosophy Demonstration of bare-knuckle web in .NET Conclusions

  3. Part I:

  4. The bare-knuckle philosophy

  5. Fear => Pair Hubris => Speed (and fun)

  6. High impact with low ceremony

  7. Framework light Test-driven No calculators

  8. Light on framework

  9. Frameworks solve 80% of the job…

  10. … and makes the rest 10 times as hard

  11. “Why did NHibernate suddenly slow down?”

  12. “How do I make IIS behave the way I want?”

  13. “Why is my routing misbehaving?”

  14. “Why is my routing misbehaving?” (what is routing, anyway)

  15. Test-driven

  16. Fast feedback cycle

  17. “I can see how TDD works for toy examples…”

  18. “… but how can we use it when we have all these really complicated technologies???”

  19. (Hint: “all these complicated technologies” I think I see your problem right here...)

  20. Don’t use a calculator…

  21. Part II:

  22. Demo: Phonebook web app

  23. .NET

  24. Part III:

  25. What the heck am I getting at?

  26. Build your app this way?

  27. Probably not

  28. I am most likely insane

  29. (And we’re all going to cloud, anyway)

  30. Understand what’s going on

  31. Are you using technology to solve your problems?

  32. Or so that you don’t have to face your problems?

  33. ... yet.

  34. Thinking in tests

  35. 1.

  36. Guiding test/ Web tests/ Acceptance test/ Usage Flow test

  37. 2.

  38. Get the infrastructure to work => separate out responsibility

  39. 3.

  40. Fine grained tests for internal logic

  41. Shallow, then deep

  42. Shallow, then deep (without changing tests)

  43. Conclusion:

  44. YAGNI

  45. No calculator until…

  46. Don’t use a framework you couldn’t have written yourself

  47. Thank you jbr@exilesoft.com http://johannesbrodwall.com http://exilesoft.com/exilee http://twitter.com/jhannes

More Related