Third-Party or Custom Code? The Art of Software Decisions

Do you often find yourself struggling with deciding whether to use a third-party library or write custom code? In this talk, we'll dive into the challenges and benefits of both approaches and provide practical tips for making informed decisions. You'll learn how to weigh the pros and cons of each option, consider architectural decisions, and create better products and apps.

Transcript

1. The missing guide for deciding between 3rd party and custom code @glnnrys
2. @glnnrys
3. @glnnrys
4. Glenn Reyes @glnnrys
5. Why do we love building apps? @glnnrys
7. Open Source is 💜 @glnnrys
8. Vincent van Gogh “Great things are done by a series of small things brought together.” @glnnrys
9. @glnnrys
10. What React framework? @glnnrys
11. What React framework? Next.js Remix CRA 🫡 None 🫠 @glnnrys
12. What date library? @glnnrys
13. What date library? moment dayjs date-fns luxon @glnnrys
15. Making decisions can be hard and time consuming @glnnrys
17. Just pick the next from top to bottom @glnnrys
23. Analysis Paralysis
24. Decision fatigue Decision
 Quality Decision
 Quantity
25. The Paradox of Choice 🤩 Amount of choices 🫠 Sweet spot
26. The Paradox of Choice Selecting speakers for the conference 🤩 Amount of proposals 🫠 Sweet spot 1000 30 0
27. 🤩 Amount of proposals 🫠 Sweet spot 0 40 30 The Paradox of Choice Selecting speakers for the conference
28. 🤩 Amount of proposals 🫠 Sweet spot 0 90 30 The Paradox of Choice Selecting speakers for the conference
29. 👩💻👨💻 @glnnrys
30. In any case ... @glnnrys
31. @glnnrys 🤓 👩💻 👷 @glnnrys
32. @glnnrys 🤓 👩💻 👷 🐒 👩🎤 🔮 🥑 🍌 @glnnrys
33. Architectural Decisions @glnnrys
34. Complexity Speed API Size Bugs Docs Time Environment License
35. Analyzing Complexity @glnnrys
36. // $(el).toggleClass(className) function toggleClass(el, className) { if (el.classList) { el.classList.toggle(className); } else { var classes = el.className.split(' '); var existingIndex = classes.indexOf(className); if (existingIndex >= 0) classes.splice(existingIndex, 1); else classes.push(className); el.className = classes.join(' '); } } youmightnotneedjquery.com @glnnrys
37. // $(el).toggleClass(className) function toggleClass(el, className) { if (el.classList) { el.classList.toggle(className); } else { var classes = el.className.split(' '); var existingIndex = classes.indexOf(className); if (existingIndex >= 0) classes.splice(existingIndex, 1); else classes.push(className); el.className = classes.join(' '); } } } else { var classes = el.className.split(' '); var existingIndex = classes.indexOf(className); if (existingIndex >= 0) classes.splice(existingIndex, 1); else classes.push(className); el.className = classes.join(' '); } @glnnrys
38. // $(el).toggleClass(className) function toggleClass(el, className) { if (el.classList) { el.classList.toggle(className); } else { var classes = el.className.split(' '); var existingIndex = classes.indexOf(className); if (existingIndex >= 0) classes.splice(existingIndex, 1); else classes.push(className); el.className = classes.join(' '); } } } else { var classes = el.className.split(' '); var existingIndex = classes.indexOf(className); if (existingIndex >= 0) classes.splice(existingIndex, 1); else classes.push(className); el.className = classes.join(' '); } 🧐 @glnnrys
39. @glnnrys
40. element.classList.toggle(className); @glnnrys
41. @glnnrys New libraries every day
42. Use what works best for you @glnnrys
43. Support 🤝 Contribution @glnnrys
44. @glnnrys
45. People love solving problems @glnnrys
46. How are problems solved in web development? @glnnrys
47. Is it over-engineered?
48. Confidence & Trust 😌 @glnnrys
49. The node_modules folder doesn’t byte you 🤗 @glnnrys
50. Let others know about your problem, ideas & improvements @glnnrys
51. Dealing with popularity @glnnrys
52. @glnnrys
53. ⭐ GitHub Stars 💎 Value 🛠 Active maintenance 🍃 Active community 💻 Platforms @glnnrys
54. Writing your own code 🖋 @glnnrys
55. Rolling our own code allows us to Tailor code to our exact needs @glnnrys
56. Rolling our own code gives us full control @glnnrys
57. With full control it's our responsibility to maintain and keep track of our code @glnnrys
59. Where to draw the line? @glnnrys
60. Value 💎 vs Constraints 🔒
61. Identify the sweet spot @glnnrys 🤩 🫠
62. Identify the sweet spot @glnnrys 🤩 🫠
63. Trust your Gut 😌 @glnnrys
64. Understand the importance @glnnrys
65. Understand the risks and drawbacks @glnnrys
66. Harm reduction @glnnrys
67. Try to get the best outcome but reduce potential risks @glnnrys
68. Decisions @glnnrys
69. Good decisions @glnnrys
70. Good decisions Clean decisions @glnnrys
71. Good decisions Clean decisions Right decisions @glnnrys
72. Good decisions Clean decisions Right decisions Smart decisions @glnnrys
73. Good decisions Clean decisions Right decisions Smart decisions Reasonable decisions @glnnrys
74. More code often means more possibilities for bugs @glnnrys
75. Take risks and keep moving forward @glnnrys
76. Simplicity is key @glnnrys
77. Don't let new things intimidate you @glnnrys
78. Always write the best code possible @glnnrys
79. “ ” Kent C. Dodds We should be mindful of the fact that we don't really know what requirements will be placed upon our code in the future. @glnnrys
80. Thank you! Glenn Reyes · @glnnrys