Frontend Dogma

“collaboration” Archive

Subtopics: , , , , ,  (non-exhaustive)

Featured on Frontend Dogma? Confirm and whitelist your domain.

  1. Agile Is Dead · · , , , ,
  2. The Root Causes for the Dev–Design Mismatch (by/via) · · ,
  3. The Importance of Giving Feedback Early: Don’t Let Resentment Fester (by) · · ,
  4. Be a Dolphin Not a Shark: Using Cooperation Over Conflict to Advance Digital Accessibility (by/via) · · , , ,
  5. The Real Cost of Meetings: What FAANG Companies Do Differently (by) · · , , , , ,
  6. The Problem of Knowledge Debt in Tech (by/via) · · ,
  7. Writing Effective Pull Request Descriptions: A Developer’s Guide (by) · · , , ,
  8. We Don’t Need a Boss, We Need a Process (by) · · , ,
  9. Types of Accessibility Approaches (by) · · , ,
  10. Figma and the Cost of Collaboration (by/via) · ·
  11. Standardization Stories (by/via) · · , , ,
  12. Closing the Designer–Developer Gap (by/via) · · , ,
  13. Collaboration, the Future of CSS, Sass, and the Web With Miriam Suzanne (by/via) · · , , , ,
  14. How to Assess Your Skill Level Before Contributing to Open Source (by/via) · · ,
  15. Consensus in Internet Standards (by) · · , ,
  16. Transforming the Relationship Between Designers and Developers (by/via) · · ,
  17. The Crucial Dance: Enhancing Designer–Developer Collaboration for Exceptional Products (via) · ·
  18. Design Systems and the Never-Ending Job of Buy In (by) · · ,
  19. We Need to Rewild the Internet (by+/via) · · , , ,
  20. Document Collaboration (With Comments!) (by/via) · · , ,
  21. Achieving Design Collegiality While Maintaining Psychological Safety (by/via) · ·
  22. My Design System Journey: Building the Plane While Flying (via) · · ,
  23. Fostering a Collaborative Onboarding Team to Design Better Onboarding Experiences (by/via) · · ,
  24. Stop Burning Out Maintainers: An Empathetic Guide for Contributors (by/via) · · ,
  25. Design Systems Teams: Understand Your Users So They Can Serve Theirs (via) · · , , ,
  26. Jimdo’s Engineering Guidelines (by/via) · · , , ,
  27. Effective Engineering Teams (by) · · ,
  28. How to Collaborate on Pull Requests for Beginners (by/via) · · ,
  29. How to Build Trust With Others by Organizing Your Figma Files (by/via) · · , ,
  30. Documentation Is a Living Thing: How We Talk Informs What We Make (by/via) · · ,
  31. Co-Authoring Git Commits (by) · · ,
  32. What to Do When Your Developers Don’t Collaborate (by/via) · ·
  33. How SEOs and UX Designers Can Work Better Together (by/via) · · , ,
  34. A Guide to Perfecting Pull Requests (by) · · , ,
  35. The Power of Git: A Guide to Collaborative Version Control (by/via) · · ,
  36. The 10 Commitments of an Agile Leader (via) · · , , ,
  37. The Art of Code Review (by/via) · · ,
  38. S.P.A.C.E. Framework—the Ultimate Framework for Measuring Your Tech Team Productivity (by) · · , , , , ,
  39. Design Patterns Are a Better Way to Collaborate on Your Design System (by/via) · · ,
  40. 7 Ways Web Developers and UX Designers Can Collaborate (by/via) · ·
  41. Designers, Use Your intuition (via) · ·
  42. Advice for Engineers, From a Manager (by) · · , ,
  43. Forging Links (by/via) · · ,
  44. Harnessing Groupthink: Fine-Tuning CSS Specifications (by/via) · ·
  45. Forging Successful Partnerships With Software Developers (by/via) · ·
  46. AI Code Completion Is Like Cruise Control—and That’s Great News for Bigger Teams (by) · · , ,
  47. How to Position Your Design System Team for Success (by/via) · · , ,
  48. 7 Collaborative Coding Tools for Remote Pair Programming (by/via) · ·
  49. Design System: How to Successfully Collaborate? (via) · · ,
  50. To Create an Excellent Design System, Treat It Like a Collaborative Process (via) · · ,
  51. How to Get a Dysfunctional Team Back on Track (by/via) · · , ,
  52. Design Systems Are About Relationships (by/via) · ·
  53. The Developer’s Fallacy of Close Collaboration With Designers (by) · · ,
  54. Behaviours That Transform Organisations (by) · · , , ,
  55. Why the Highest-Paid Developers “Fight” Their Coworkers (via) · · ,
  56. Better Collaboration by Bringing Designers Into the Code Review Process (by/via) · · , ,
  57. The Problem With Patterns (by/via) · · , , ,
  58. The Imbalance of Culture Fit (by/via) · · , ,
  59. The Foundation of Technical Leadership (by/via) · · , ,
  60. The Importance of Code Reviews (by/via) · · ,
  61. Building the UI for the New “The Times” Website (by/via) · · , , , ,
  62. How Good Are Your HTML and CSS Comments? (by/via) · · , , , ,
  63. Efficient Responsive Design Process (by/via) · · , , ,
  64. Offering Feedback (by/via) · · , ,
  65. Hey Designers: Stop Being an Afterthought (by/via) · · , ,
  66. Resetting Agency Culture (by/via) · · ,
  67. The Specialist–Generalist Balance (by/via) · · ,
  68. Migrating Your Team to Sass (via) · · ,
  69. The Specialized Web: Working With Subject-Matter Experts (by/via) · ·
  70. Why Managers Make Terrible Scrum Masters (by/via) · · , , ,
  71. People Skills for Web Workers (by/via) · ·
  72. Facilitating Great Design (by/via) · · ,
  73. Working Successfully With Contractors (via) · · ,
  74. The Importance of Standards (via) · · , ,
  75. Help the Community! Report Browser Bugs! (by/via) · · , ,
  76. How to Write CSS for Others (by/via) · · , , , ,
  77. The Battlefield of Design: Designers vs. Clients (by/via) · · , ,
  78. 5 Easy Ways to Deal With an Unhappy Client (via) · · ,
  79. 20 Ways to Keep Clients Coming Back for More (via) · · ,
  80. In Defense of Difficult Clients (via) · · ,
  81. Quick Reminder on Vendor Relations (via) · ·
  82. CSS Talking Points: Selling Clients on Web Standards (via) · · , , ,
  83. Manifesto for Agile Software Development (by+) · · , , ,