Building with Friction
Read OriginalThis article discusses the importance of intentionally introducing 'friction' into software development workflows to prevent poor practices. Using a personal analogy about snacking, it explains how making wrong actions (like adding unnecessary npm packages) slightly harder can lead to more intentional, higher-quality decisions. It critiques how tools like npm, while valuable, have removed necessary pauses for consideration, leading to bloat and security issues, and suggests adding friction at key stages like install and build.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser