A note from the archives
Speaking of tables, a while back we published a guide to the table element that goes into great depth about how to use them: how to make them responsive for a number of different layouts and screen sizes, how to style them nicely and how to avoid key problems that designers bump into time and time again.
A Complete Guide to the Table Element
What have you learnt this week?
Robin Rendle: This week I’ve been struggling with collaborating on a large project with a new team. And I think the difficulty here lies in what the concept of what the word “work” means for many of our team members.
If that sounds confusing and/or patronising, hear me out.
For lots of designers and developers, “work” is often the act of creating something new. When we sit down we want to be iterating in Sketch or Figma or Photoshop, or perhaps we feel that “work” is complete when we’re writing code and building fresh, shiny new things. However, there is a delicate moment in the process of designing a large web app when adding new code and implementing new designs becomes a serious detriment to the overall process of design.
In fact, “work” must also be seen as subtracting design components, refactoring code and deleting pretty much everything that isn’t entirely necessary. This is because if we don’t continue to clean up behind us then we’re bound to have problems with efficiency.
In other words, the more code that’s in our app the more inefficient we are. And the more inefficient we are as designers and developers then the longer it takes to ship new features and improve the overall user experience.
In other other words, code bloat is directly related to the user experience.
Until next time!