# Speed and tools

2018-04-10

> This emphasis on speed has also dictated the shape of our tools.

> Abstraction and modularisation enable products to be built quicker. This has led to the development of component-oriented frameworks like Angular, React and Vue. At the same, designers are starting to adopt similar modular approaches. While this alignment is encouraging, I worry that design is increasingly becoming a servant to the needs of the engineer rather than those of the user; the question is always "should designers learn to code", never the other way round.

> There is also a growing sense that these tools are being adopted primarily for the benefit of internal team dynamics – the rise of the term ‘developer experience’ being just one signifier.

> Fantasies of the Future: Design in a World Being Eaten by Software (cache)

I worry too, focusing on fancy tiny modules to avoid the ugly big picture. Today, the question must be “should designers AND coders learn about ethics?”. And the answer is yes, definitely.

At last.

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.