Be nice. Or else.
Germany's Best Kept Secret Joined over 3 years ago via an invitation from Yaron S.
All good. We should also find out who developed it and give that credit. Would be amazing to always have insight into who designs and builds all the great work that's shown here on DN.
Designed by Anton & Irene.
Make sure you actually need all those new shiny tools. Many of these things are industry-grade tools for big companies like Facebook, Pinterest, etc that have tons of developers and highly complex services. Most websites and smaller teams don't need all of this and you can happily live with something technically simpler. No need for a professional kitchen when all you're making is a sandwich.
CodeKit has made my life much easier working with things like SASS, Jade, JS, etc. They have a great video section with lots of tutorials.
I'd just start with one thing at a time. Maybe just build a static page in Jade and SASS and use a build tool of your choice (or CodeKit) and become comfortable in those. Then pick up some JS library you are interested in and just focus on that. You could very easily lose yourself in all this new tooling, so I'd be very strategic about what you learn and how much time you invest.
"Stealing" is the wrong term. It implies taking something from someone against their will. Makes for a nice headline though.
This is really about the "imitate, internalize, improve" learning process. First, you straight-out copy something you admire. By doing that, you understand how it it works. Then you can take your own spin on it and apply the techniques/styles/etc in the future on your own work.
Remixing others work is really great for a platform like Dribbble, where a lot of things are posted for fun.
Did you see any details on them? All I could find was the placeholder page for requesting an invite.
Congrats to your team. This is some really beautiful work all around. Great execution on the brand guide as well. I'll study this closely :)
Agree. I also got a ton of direct, harsh feedback starting out that I really appreciated, from people way more talented than me. And that's great, as long as it's valid and has the "Focus on x, y and z" part that's actually helpful. To me, Eli just has the harshness without the helpfulness. And I just find that one-sidedness useless.
While I found the overall interview really insightful, this was a super lame way to end it. People grow from insightful, constructive criticism, and not from attacks. "Honesty" does not make an attack any better.
"Activity centered design" seems to go in the same direction, but I think the "Jobs to be done" stuff goes just a little further. From what I understand from the article, activities are things people do. The jobs stuff is about what people want to achieve, the progress they want to make. So it starts even before people engage in activities and therefore goes deeper into psychology and behavior.
The classic story from the Jobs theory is that of a store selling milkshakes. They tried all kind of marketing tricks but couldn't increase sales. Then they started talking to people and realized that in the morning they had a lot of commuters stop by in a hurry. Those commuters wanted basically a breakfast replacement, something that filled them up, lasted until lunch, and was easy to drink while driving. In the afternoon they had more families stop by, maybe coming back from the playground and the kids needing a break and a refreshment. By taking that perspective, they could design and market their products very differently (e.g. healthy, filling shakes in spill-proof cups in the morning, and smaller, fruity shakes in colorful cups in the afternoon, etc).
From what I know, user centered design doesn't have a term for a "Job" in that sense. Seems like it would be good additional thing to introduce.
You may want to just approach this whole thing from a different perspective. As a developer, you're constantly focused on the technical details and with the options we have today, that can be overwhelming. But what really makes a product simple is not a lack of complexity, but just showing people the right thing at the right time. I'm currently listening to the audiobook "Competing against luck", which essentially reframes user-centered design for more business focused minds (they call it the "Jobs to be done" framework). The book explains how the whole product (and business organization) should be driven from the needs and desires of the user/customer. If you start from that perspective, a many things fall into place by themselves. This is opposite of what companies with tech blinders do. They have a piece of technology and then apply it to everything, whether it makes sense or not (e.g. Tweeting refrigerators). Hope his helps.