| From Designing Things to Designing Change (uxd) | | 99 |
| design, principles |
| The Professional Standing of Frontend Developers (mar) | | 98 |
| guest-posts, career, learning, html, css, javascript, communication, community, ai |
| The Figma Dilemma: Too Many Cooks, Too Few Decisions (web) | | 97 |
| design, figma |
| 11 Practical Tips to Make Code Reviews Easier as a Developer (anm) | | 96 |
| code-reviews, tips-and-tricks, ai, principles, linting, formatting, quality |
| Getting the Relationship Between UX Design and Business Strategy Right (sil/uxm) | | 95 |
| design, user-experience, product-management, strategies, economics, business-relations |
| When an Engineering Manager Marries a Product Manager: Planning, Roadmaps, and Bug Fixes (dar/cod) | | 94 |
| engineering-management, product-management, career, processes |
| Figma Branches Best Practices (hp) | | 93 |
| design, figma, best-practices, naming, processes |
| My 18-Months Rule for Open-Source Contributions (j9t) | | 92 |
| foss, communication, community |
| The 20 Commandments of Software Engineering | | 91 |
| principles, programming, complexity, documentation, commit-messages, code-reviews, dependencies, maintenance |
| The Bad Apple Effect: How Negativity Can Sabotage Teams’ Performance (uka/scr) | | 90 |
| culture, engineering-management |
| Agile Is Dead | | 89 |
| websites, manifestos, agile, processes, communication |
| The Root Causes for the Dev–Design Mismatch (ere/uxd) | | 88 |
| design, processes |
| The Importance of Giving Feedback Early: Don’t Let Resentment Fester (cwo) | | 87 |
| communication, culture |
| Be a Dolphin Not a Shark: Using Cooperation Over Conflict to Advance Digital Accessibility (lfl/par) | | 86 |
| videos, accessibility, advocacy, strategies |
| Don’t Do Agile, Be Agile (www) | | 85 |
| agile, scrum, kanban, processes |
| The Problem of Knowledge Debt in Tech (bek/ope) | | 84 |
| documentation, version-control |
| The Real Cost of Meetings: What FAANG Companies Do Differently (tre) | | 83 |
| processes, efficiency, aws, facebook+meta, google, apple |
| Writing Effective Pull Request Descriptions: A Developer’s Guide (fyv) | | 82 |
| guides, version-control, documentation, code-reviews |
| We Don’t Need a Boss, We Need a Process (mia) | | 81 |
| design, leadership, processes |
| Types of Accessibility Approaches (a11) | | 80 |
| accessibility, processes, career |
| Figma and the Cost of Collaboration (rho/uxd) | | 79 |
| figma |
| Standardization Stories (fan/css) | | 78 |
| videos, web-platform, css, standards |
| Closing the Designer–Developer Gap (kat/tel) | | 77 |
| design, career, processes |
| Collaboration, the Future of CSS, Sass, and the Web With Miriam Suzanne (mia/sch) | | 76 |
| videos, interviews, css, sass, outlooks |
| How to Assess Your Skill Level Before Contributing to Open Source (bek/ope) | | 75 |
| how-tos, foss |
| Consensus in Internet Standards (mno) | | 74 |
| communication, standards, web-platform |
| Transforming the Relationship Between Designers and Developers (chr/sma) | | 73 |
| design, processes |
| Designing Design Systems: How to Lay the Groundwork That Drives Decision Making (ado) | | 72 |
| how-tos, design-systems, processes, maintenance |
| The Crucial Dance: Enhancing Designer–Developer Collaboration for Exceptional Products (uxm) | | 71 |
| processes |
| Design Systems and the Never-Ending Job of Buy In (pjo) | | 70 |
| design-systems, communication |
| We Need to Rewild the Internet (mar+/noe) | | 69 |
| web, standards, creativity, outlooks |
| Document Collaboration (With Comments!) (chr/fro) | | 68 |
| documentation, comparisons, link-lists |
| Achieving Design Collegiality While Maintaining Psychological Safety (jog/uxm) | | 67 |
| design |
| My Design System Journey: Building the Plane While Flying (uxd) | | 66 |
| design-systems, processes |
| Fostering a Collaborative Onboarding Team to Design Better Onboarding Experiences (hsp/uxm) | | 65 |
| onboarding, user-experience |
| Stop Burning Out Maintainers: An Empathetic Guide for Contributors (bek/ope) | | 64 |
| guides, foss |
| Design Systems Teams: Understand Your Users So They Can Serve Theirs (deq) | | 63 |
| design-systems, leadership, accessibility, user-experience |
| Jimdo’s Engineering Guidelines (pez/jim) | | 62 |
| guidelines, processes, onboarding, case-studies |
| Effective Engineering Teams (add) | | 61 |
| career, engineering-management |
| How to Collaborate on Pull Requests for Beginners (cod/ope) | | 60 |
| how-tos, code-reviews |
| How to Build Trust With Others by Organizing Your Figma Files (raq/uxd) | | 59 |
| how-tos, figma, conventions |
| Documentation Is a Living Thing: How We Talk Informs What We Make (lc/sup) | | 58 |
| documentation, communication |
| “Good Commit” vs. “Your Commit”: How to Write a Perfect Git Commit Message (vic/git) | | 57 |
| how-tos, commit-messages, version-control, git |
| Co-Authoring Git Commits (cas) | | 56 |
| git, documentation |
| What to Do When Your Developers Don’t Collaborate (dur/scr) | | 55 |
| processes |
| How SEOs and UX Designers Can Work Better Together (hel/moz) | | 54 |
| seo, user-experience, design |
| A Guide to Perfecting Pull Requests (kar) | | 53 |
| git, code-reviews, foss |
| The Power of Git: A Guide to Collaborative Version Control (bek/ope) | | 52 |
| guides, git |
| The 10 Commitments of an Agile Leader (scr) | | 51 |
| agile, processes, leadership, engineering-management |
| On Feedback (fri) | | 50 |
| communication, culture |
| The Art of Code Review (j47/doc) | | 49 |
| code-reviews, processes |
| S.P.A.C.E. Framework—the Ultimate Framework for Measuring Your Tech Team Productivity (pio) | | 48 |
| productivity, metrics, engineering-management, culture, communication, efficiency |
| Design Patterns Are a Better Way to Collaborate on Your Design System (ben/sma) | | 47 |
| design-patterns, design-systems |
| 7 Ways Web Developers and UX Designers Can Collaborate (abd/uxm) | | 46 |
| processes |
| Designers, Use Your intuition (uxd) | | 45 |
| design |
| Advice for Engineers, From a Manager (pol) | | 44 |
| tips-and-tricks, career, communication |
| Forging Links (mat/9el) | | 43 |
| videos, css |
| Harnessing Groupthink: Fine-Tuning CSS Specifications (ric/cle) | | 42 |
| css |
| Forging Successful Partnerships With Software Developers (jon/uxm) | | 41 |
| design |
| AI Code Completion Is Like Cruise Control—and That’s Great News for Bigger Teams (cod) | | 40 |
| ai, code-completion, productivity |
| How to Position Your Design System Team for Success (bik/vig) | | 39 |
| how-tos, design-systems, productivity |
| How to Professionally Say (aka) | | 38 |
| websites, how-tos, communication, professionalism, career |
| 7 Collaborative Coding Tools for Remote Pair Programming (joe/sit) | | 37 |
| tooling |
| Design System: How to Successfully Collaborate? (uxd) | | 36 |
| how-tos, design-systems |
| To Create an Excellent Design System, Treat It Like a Collaborative Process (uxd) | | 35 |
| design-systems, processes |
| How to Get a Dysfunctional Team Back on Track (lia/ali) | | 34 |
| how-tos, engineering-management, culture |
| Design Systems Are About Relationships (rcd/sma) | | 33 |
| design-systems |
| The Developer’s Fallacy of Close Collaboration With Designers (j9t) | | 32 |
| design, creativity |
| Behaviours That Transform Organisations (bla) | | 31 |
| engineering-management, culture, communication, leadership |
| Why the Highest-Paid Developers “Fight” Their Coworkers (sit) | | 30 |
| career, culture |
| Better Collaboration by Bringing Designers Into the Code Review Process (ida/sma) | | 29 |
| design, code-reviews, processes |
| The Problem With Patterns (cat/ali) | | 28 |
| design, design-patterns, processes, user-experience |
| The Imbalance of Culture Fit (ele/ali) | | 27 |
| culture, communication, engineering-management |
| The Foundation of Technical Leadership (aut/ali) | | 26 |
| career, leadership, communication |
| The Importance of Code Reviews (kit/sit) | | 25 |
| code-reviews, quality |
| Building the UI for the New “The Times” Website (ped/gro) | | 24 |
| design, architecture, css, documentation, case-studies |
| How Good Are Your HTML and CSS Comments? (hey/sit) | | 23 |
| html, css, comments, maintainability, examples |
| Efficient Responsive Design Process (ben/sma) | | 22 |
| responsive-design, processes, communication, business-relations |
| Offering Feedback (rac/ali) | | 21 |
| business-relations, communication, product-management |
| Hey Designers: Stop Being an Afterthought (rhj/sma) | | 20 |
| design, processes, communication |
| Resetting Agency Culture (pse/ali) | | 19 |
| culture, communication |
| The Specialist–Generalist Balance (mrg/ali) | | 18 |
| career, communication |
| Migrating Your Team to Sass (sit) | | 17 |
| sass, migrating |
| The Specialized Web: Working With Subject-Matter Experts (ama/ali) | | 16 |
| communication |
| Why Managers Make Terrible Scrum Masters (mda/sit) | | 15 |
| agile, scrum, processes, engineering-management |
| People Skills for Web Workers (luc/ali) | | 14 |
| engineering-management |
| Facilitating Great Design (kev/ali) | | 13 |
| design, processes |
| Working Successfully With Contractors (sit) | | 12 |
| communication, business-relations |
| The Importance of Standards (sit) | | 11 |
| conventions, formatting, maintainability |
| Help the Community! Report Browser Bugs! (lea/sma) | | 10 |
| community, browsers, documentation |
| How to Write CSS for Others (css/sma) | | 9 |
| how-tos, css, maintainability, comments, sorting |
| If You’re in Online Marketing and Strategy, This Will Piss You Off (tim) | | 8 |
| design, marketing, processes |
| The Battlefield of Design: Designers vs. Clients (boa/sit) | | 7 |
| design, business-relations, processes |
| 5 Easy Ways to Deal With an Unhappy Client (sit) | | 6 |
| business-relations, communication |
| 20 Ways to Keep Clients Coming Back for More (sit) | | 5 |
| business-relations, communication |
| In Defense of Difficult Clients (ali) | | 4 |
| business-relations, processes |
| Quick Reminder on Vendor Relations (sit) | | 3 |
| business-relations |
| CSS Talking Points: Selling Clients on Web Standards (ali) | | 2 |
| css, standards, communication, business-relations |
| Manifesto for Agile Software Development (ken+) | | 1 |
| manifestos, programming, processes, agile |
