The document discusses the author's experiences and lessons learned while creating the enki.js library, motivated by dissatisfaction with existing options. It emphasizes a design philosophy favoring simplicity and minimalism for modern browsers, as well as highlights the benefits of test-driven development. Additionally, it notes challenges such as feedback, scope creep, and the difficulties in documentation.

1. Enki.js
Lessens learned while writing a libray

2. Ok, so what is it?

3. Why did I write it?

4. I disliked existing libraries

5. Disillusioned with my work

6. Bored

7. Wanted to see if I could do it

8. Design philosophy

9. For modern browsers (IE9+)

10. No boilerplate code

11. No boilerplate code

12. No code in the view

13. Keep it simple

14. Keep it simple

15. Keep it simple

16. Keep it small

17. Keep it small

18. No defensive programming

19. Things I’ve learned

20. TDD is fun when not at work

21. TDD is fun when not at work

22. Big things with little code

23. JavaScript is seriously powerful

24. Dynamic types + functional = 💣

25. Dynamic types + functional = 💣

26. Feedback is hard to come by

27. Scope creep

28. Documentation is harder than it
should be

29. Things that it’s missing

30. Speed tests

31. Memory tests

32. Async loading

33. Questions?

34. Links
Enki.js:
https://github.com/linkerro/enki.js
TodoMVC implementation in enki:
https://github.com/linkerro/todomvc/tree/master/e
xamples/enki