One of the topics that comes up often in web design circles is whether or not designers should code. What about the reverse? What about developers? Should developers learn more about design?
One of the topics that comes up often in web design circles is whether or not designers should code. What about the reverse? What about developers? Should developers learn more about design?
Context is everything. It shapes the meaning in all communication. Without context you can’t communicate effectively. When your message is delivered in one context, but received in another, it likely leads to miscommunication.
How do you decide what to work on next? Do you have a system for task management? Do you just do whatever you feel like in the moment? If you have a system do certain aspects of it help you more than others?
How do you know which advice given to you is worth trying? Do you try everything? Do you assume it will always work if it worked for someone else? Today I want to talk about context, mostly as it relates to your current situation and any advice you might apply to your situation.
Earlier in the week I offered some thoughts about components, design patterns, and pattern libraries. In that post I shared some things about the house I grew up in and how it was built on the same plan as other houses in the neighborhood. I want to talk a little more about the neighborhood and how it created a context for each of the houses within.