Frontend Dogma

“processes” Archive

  1. The Cost of Interrupted Work: More Speed and Stress · ·
  2. How to Plan Your First Successful Website · ·
  3. How (In)Efficient Are Engineering Organizations? · · ,
  4. The “10× Engineer”: 50 Years Ago and Now · · , ,
  5. How to Build a Newthing · · , ,
  6. My Design System Journey: Building the Plane While Flying · · ,
  7. “Web Design as a Process” in Charts: Maintenance, Decay, Tech Debt, and Big Bang Launching · · , , , ,
  8. 7 Effective Ways to Craft Compelling Problem Statements for UX Design · · ,
  9. Getting to an Accessibility Strategy · · ,
  10. Why I Like Scrumban · · , ,
  11. Making VPATs and ACRs More Effective in Procurement · ·
  12. Why Do Rubber Ducks Work? · · ,
  13. Onboarding · · , ,
  14. The Loss of the Process in the Name of Progress · · , ,
  15. Debunking 10 Common Objections to Incremental Delivery for Software Teams · ·
  16. Futuring With Design · · ,
  17. 7 Tips for Devs and Designers to Set Your Accessibility Efforts Up for Success · · ,
  18. The Structure of User Experience · ·
  19. Balancing Engineering Cultures: Debate Everything vs. Just Tell Me What to Build · · , ,
  20. How End-to-End Testing Moves Us Closer to Continuous Accessibility · · ,
  21. Continuous Accessibility: What, Why, How · · , ,
  22. What Is Our Design Intention? · ·
  23. 14 Things to Check Before Deploying a Website · · ,
  24. Performance and Stay Questions in 1:1s · · ,
  25. Definition of Done (DoD) Explanation and Example · · , ,
  26. Embracing the Absurd in Your Design Practices · ·
  27. Agile Anti-Patterns That Can Harm UX · · , ,
  28. Incident, Mitigate, Learn · · , ,
  29. Eigensolutions: Composability as the Antidote to Overfit · ·
  30. Good Design Is Subjective, Contextual, and Intentional · ·
  31. Stop Normalizing Unprofessional Behaviour in the Name of Agility · · , ,
  32. All Technical Debt Is a Risk to the Product and to Your Business · · , ,
  33. Accessibility-Specific Tech Requirements? It Depends! · ·
  34. My 3 Rules for Documenting Code · · ,
  35. Pen, Paper, IDE: A DevTool Founder’s Early-Stage Product Design Guide · · , ,
  36. Of Time and the Web · · , ,
  37. A More Holistic Design Workflow: Gluing Jira, Figma, and Zeplin Together · · ,
  38. Design That Scales · · , , ,
  39. Why We Don’t Like TDD: A Developer’s Perspective · ·
  40. Why You Should Curate, Not Create, a Design System · ·
  41. Shattering the Design System: Unleashing the Creative Revolution · · ,
  42. Letter and Spirit of Web Development · ·
  43. How Long Until Your Website Is Accessible? · ·
  44. Accessibility by Degrees · ·
  45. Embedding Accessibility into Code Reviews · · , ,
  46. Web Accessibility Strategies for Non-Accessible Projects · · , ,
  47. You Can’t Get Faster Than No Build · ·
  48. Return to Office Is Bullshit and Everyone Knows It · ·
  49. The Cost of Obsessing over Design Perfection · · ,
  50. Misconceptions Can Kill Accessibility Momentum · · ,
  51. Supercharge Your Repository With Code Owners · · ,
  52. Building a Core Accessibility Team: The Keys to the Kingdom · · ,
  53. From Silos to Design Systems · · ,
  54. Why Your Design System Needs a Component Process · · ,
  55. Stakeholder Management for Design Systems · · ,
  56. Getting Started in a New Codebase · · ,
  57. Why Inclusive Language Matters in Coding · · , ,
  58. Write About What You Learn—It Pushes You to Understand Topics Better · · , ,
  59. Definition of Done vs. Acceptance Criteria: What’s the Difference? · · , ,
  60. Top 7 Things That Kill Developer Productivity · · , , , ,
  61. Accessibility of the Button: Should We Fix It or the Root Cause Problem? · · ,
  62. Start by Writing Messy Code · ·
  63. Design Systems Management from Bottom–Up · ·
  64. The Future of Design Systems Is Semantic · · ,
  65. The Joy of Simplicity in Web Development · ·
  66. What to Do When Your Developers Don’t Collaborate · ·
  67. Effective Code Reviews · · , ,
  68. The Art of Looking Back: A Critical Reflection for Individual Contributors · · ,
  69. How Platform Teams Get Stuff Done · · ,
  70. The 10 Commitments of an Agile Leader · · , ,
  71. Better Roadmaps ·
  72. How to Use Your Intuition in Your Product Design Process · · , ,
  73. Developer’s Research Process · ·
  74. Mockups Explained · ·
  75. How to Improve the Release Frequency of Your Team? · · , , ,
  76. AI and the Automation of Work · · ,
  77. Combat Accessibility Decay: How to Maintain Ongoing Accessibility · · ,
  78. What’s the Perfect Design Process? · ·
  79. Why You Must Commit to Grounding Every DEI-Related Effort With Data · · , ,
  80. XML Is the Future · ·
  81. Continuous Accessibility · · ,
  82. The Art of Code Review · · ,
  83. 10 Incident Management Best Practices · · ,
  84. A Practical Overview on Architecture Decision Records (ADR) · · ,
  85. Designing a Better Design Handoff File in Figma · · ,
  86. Website Issues: On the Relevance of Audience Size and Impact · ·
  87. How to Handle Production Support When Using Scrum · · , ,
  88. The Difference Between Agile and UX Is Not About Quantity vs. Quality · · , ,
  89. Progress over Perfection: The Better Way for Communication and Accessibility Advocacy · · ,
  90. 5 Topics You Should Touch on During the Recruitment Process · · ,
  91. Why Is Scrum the Most Popular Agile Framework? · · ,
  92. Shifting Left, or: Making Accessibility Easier by Doing It Earlier · · , ,
  93. Formulating Your Product Design North Star (aka Design Principles) · · ,
  94. The Cost of Craft · · , ,
  95. Regression Testing in the Agile Universe · · , ,
  96. 7 Ways Web Developers and UX Designers Can Collaborate · ·
  97. “Design First, Then Build”: Let’s Bury This Myth Forevermore · ·
  98. What Value Does Developer Relations Bring to Other Teams? · ·
  99. The Seven Archetypes of Organizational Topologies · ·
  100. Are You Testing to Test, or Testing to Prove? · ·
  101. How to Contribute to a Project You Have No Idea About · · , ,
  102. The Importance of Adding Accessibility Design Reviews to the Design Process · · ,
  103. Where Does Developer Relations Belong in an Organization? · ·
  104. Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle · · ,
  105. All About Iterative Design · ·
  106. Technical Writing Process: How to Write a Good Technical Article · · ,
  107. The Difference Between Iteration and Prototyping · · ,
  108. Discovery in Agile · ·
  109. Front-End Is So Much More Than Building Designs ·
  110. When Stakeholders Bypass the Product Owner · · ,
  111. Shape Up · ·
  112. What’s Wrong With Code in 2022? · · ,
  113. The Science of User Experience · ·
  114. Code Ownership and Software Quality · ·
  115. How to Handle Unplanned Work in Scrum · · , ,
  116. 5 Insider Tips to Make Accessibility Part of Workflow · · ,
  117. Theory-Building and Why Employee Churn Is Lethal to Software Companies · ·
  118. Progress over Perfection: A Better Way to Accessibility · ·
  119. Usable, Useful, and Valuable · · , ,
  120. How to Build the Foundation for Digital Accessibility · · , ,
  121. Redo Websites Less Often (to Become a Better Developer) · ·
  122. Top Task Analysis: Make It Fast and Efficient ·
  123. 3 Problems Scrum Doesn’t Solve · · ,
  124. Be Good-Argument-Driven, Not Data-Driven · ·
  125. Does Accessibility Stifle the Creative Process? · · ,
  126. No Demo [Website] Reno · ·
  127. When Will Scrum Die? · · , ,
  128. How Scrum With Kanban Works · · , ,
  129. The Methods UX Professionals Use · ·
  130. Working on a New Feature as a Senior Frontend Developer ·
  131. Choosing the Right Mindset to Design Complex Applications · · ,
  132. Thoughts on an Accessibility “Get Well” Plan · · ,
  133. What Do the Developers Do in the Last Week of the Sprint? · · ,
  134. 10 Incident Management Best Practices for Streamlined Operations · · ,
  135. Why You Shouldn’t Modify Scrum · · ,
  136. Change Management for Accessibility · ·
  137. 15 Sprint Review Anti-Patterns—Scrum Anti-Patterns Guide 2022 · · , ,
  138. The 5 Golden Rules of Code Reviews · · ,
  139. Designers Are Spending Too Much Time Designing UI Variations Manually · · ,
  140. To Create an Excellent Design System, Treat It Like a Collaborative Process · · ,
  141. Technology Time-Outs · ·
  142. Git Organized: A Better Git Flow · · ,
  143. Becoming an Expert · · , ,
  144. The Process of Building a CSS Framework · ·
  145. How We Improved Our Design System Delivery · · , ,
  146. Not Releasing Late on Fridays, a Matter of Courtesy · ·
  147. How to Hand Off Accessible Designs to Developers? · · ,
  148. Definition of Done vs. Acceptance Criteria · · , ,
  149. Building an Accessibility Library · ·
  150. Goodbye, Clean Code · · ,