Many of us fall victim to constantly consuming content, rather than creating our own. This is the guaranteed stagnation, or worse, the slow death of your business taking place right in front you. And no one will change it for you. So, what can you do about it?
We spend a lot of time asking ourselves the question "How do we build a great product?" It's easy to get consumed by just the core building blocks of a product, such as the code, the interface, and the infrastructure. We rarely consider marketing and support from the very beginning. Why should we? Marketing and support aren't a core part of our product, right? Or, are they?
The concept of prototyping is nothing new. Prototyping for a better User Expereince (UX) is still gaining traction in some businesses, especially in Enterprise space. Let's explore the benefit that introducing something as simple as prototyping can bring to your company.
There are a ton of articles and lessons out there on how to get started with Gulp and the various ways you can use it, but there aren't many on how to add the basics you need for a new project. So, if you already have Node and NPM set up, here's a quick guide on adding the files you need to start a new project using Gulp for frontend tasks. You can also use these steps to add Gulp to an existing project.
With all the craziness around web design lately, it seems like everyone's scurrying to play catch-up, especially where Responsive Web Design (RWD) is concerned. I know I constantly feel like I'm behind the curve. We're all still trying to hone the intricacies of designing for various devices and contexts. I don't know anyone yet who's mastered it or who claims that they have a far superior approach, and there's nothing wrong with this. As we tackle these problems, we're constantly faced with the shortcomings that browsers and devices still have, or the many open issues that the industry is still trying to figuring out. In all of this craziness, it's easy to forget about the perspective of users, especially with responsive design.
We could all probably write about some bad client experiences, but I bet we can all write an equally long list of really positive things that we've learned from working with clients. Working with clients have made me better at a lot of things. Here are just a few of the ways I believe clients make us better.
Process feels pretty good. It’s like a dependable bus route, with all these little stops, and you can measure how long it takes to get to each one. Then, the transportation service can tweak it and tune it so it becomes more efficient over time. They can document it and refer to it each time they have questions. They can add and remove stops. Passengers can build expectations around it, and even make predictions because of it, and because of this, they can feel confident.
We’ve all spent a lot of time over the last year or so debating (or watching others debate) about this idea that designers need to learn to code. This argument sometimes makes it sound like we as “coders” are already impeccable designers who would never need to consider brushing up on our design skills. It also continues to imply that a designer and a coder are different roles. I believe that it depends.