Category Archives: SQL

Integrating feature requests without destroying your product

Look at feature requests as a request for a new or improved workflow, not a new feature


1. Listen to client feedback with an interpretive ear, and don’t be afraid to dig deeper to identify underlying problems

2. Sometimes feature requests are actually usability issues in disguise

3. Sometimes the product features clients request are actually new product offerings in disguise

4. Focus your energy on hearing the users’ needs, not the users’ wants

5. More features do not equal a better product

Read more from the source: InVision Blog

Going from Design to Code without Going Insane

Design and Development will find the best success if they take the time to communicate and set up clear workflows


Some tips from Adobe Creative Camp includes

1. Use software that helps avoid “Photoshop Archaeology”–Developers inspecting colors, fonts, and measurements from a Photoshop file and translating it into HTML and CSS.

2. Have a clear workflow for adding and updating assets.

3. Have lots of conversations.

4. Designers, start learning about CSS.

Read the blog article at

The best icon is a text label

Before you choose icons for your UI, have a look at real-world cases of what works and what doesn’t


Thomas Byttebier is a freelance web designer creating minimalist and easy to use websites and user interfaces. Thomas lives and works in Gent, Belgium.

He writes: Of course I can see why icons grew popular in user interfaces. Firstly, they make the UI more graphically pleasing. And when done right, they can certainly give your app visual personality. That’s two good things.

Moreover, an icon can often replace a long descriptive group of words. As screens get smaller, this is much welcomed. But herein lies the design trap, because most icons are unclear. They make people think. What good has a beautiful interface if it’s unclear? Hence it’s simple: only use an icon if its message is a 100% clear to everyone. Never give in.

Read more from the source:

James Shore gives a thumbs up to React JS, but not for the reasons you might expect

React JS is not accidentally opinionated. It is quite testable. It is SEO compatible. You should use it.


James Shore is host of the screencast Let’s Code: Test-Driven JavaScript. He gives an excellent breakdown on choosing React.

An Unconventional Review of React | Let’s Code JavaScript

Over the 5-10+ years I’ll be supporting my product, will this code cause me more trouble than it’s worth?

It’s not about how much work the library saves me in initial implementation. Oh, no. That’s trivial in comparison. No, it’s about much maintenance it costs me over the life of my app.

I have five criteria I consider.

Read more from the source: