The document discusses the importance of technical skills for designers, particularly in coding with HTML, CSS, and JavaScript, and the benefits of having a broader skill set that includes UI/UX design and front-end implementation. It highlights the advantages of prototyping and creating efficiencies within teams, while also acknowledging the challenges and unrealistic expectations in the evolving UX landscape. Additionally, it touches on the implications of being too technical and the need for balanced skill development in the profession.

1. make it better
Designing, Technically
prepared for ga uxdi
On being a “technical” designer

2. make it better
Should designers know
how to code?
designing, technically
prepared for ga uxdi
tweet @skotcarruth

3. make it better
Should designers code?
designing, technically
prepared for ga uxdi
tweet @skotcarruth

4. designing, technically tweet @skotcarruth
make it better
The Upsides
prepared for ga uxdi

5. make it better
designing, technically
The Job Market
• “Highly proficent in building prototypes in HTML+CSS
+JavaScript.”
• “First, the individual will need a broad skill set that includes UI/
UX, visual design, and, ideally, frontend implementation in
HTML/CSS.”
• “Comfortable coding in HTML/CSS for responsive web and
email design”
• “UI/UX Designer and Front-end Engineer”
prepared for ga uxdi
tweet @skotcarruth

6. make it better
designing, technically
Gauging Feasibility
• How long will this interface take to implement?
• Can we even add this feature to our existing system?
prepared for ga uxdi
tweet @skotcarruth

7. make it better
designing, technically
Prototyping
• HTML prototypes can represent interaction better in tests
• Responsive prototyping
• Templating can make it faster and less tedious
prepared for ga uxdi
tweet @skotcarruth

8. make it better
designing, technically
Chipping In
• Don’t send a design that’s impossible to code
• Get in there and close some tickets!
• Smaller teams == broader individual skill sets
• Inside jokes
prepared for ga uxdi
tweet @skotcarruth

9. make it better
designing, technically
Creating Efficiencies
• Why pay two if one can do the job
• More consistent vision
• Less documentation
• Less “telephone”
prepared for ga uxdi
tweet @skotcarruth

10. make it better
designing, technically
Understanding systems
• Interaction design usually implies interaction between:
• the user
• the system
• Real companies and processes are complex
• Underlying software very likely has inherent limitations
prepared for ga uxdi
tweet @skotcarruth

11. designing, technically tweet @skotcarruth
make it better
The Downsides
prepared for ga uxdi

12. make it better
designing, technically
Unrealistic Expectations
• “UI/UX Designer and Front-end Engineer”
• You can’t be an expert at everything
prepared for ga uxdi
tweet @skotcarruth

13. designing, technically tweet @skotcarruth
Some people can play the piano and the banjo,
make it better
but when they play them both at once it
sounds really crappy.
prepared for ga uxdi
Roger Belveal
http://www.quora.com/Why-dont-more-designers-code

14. make it better
designing, technically
UX is increasingly complex as it is
• More and more platforms to design for
• Users are less and less tolerant of poor UX
prepared for ga uxdi
tweet @skotcarruth
thanks to Sagi Shrieber https://medium.com/@sagishrieber/why-designers-should-not-code-anymore-5fc3f7d5510d

15. make it better
designing, technically
It can change your thinking
• Conway’s Law
• “Implementation Model”
• Optimizing for the code vs. optimizing for the user
prepared for ga uxdi
tweet @skotcarruth
thanks to Wayne Greenberg and Josh Seiden http://www.waynegreenwood.com/unicorn-shmunicorn-be-a-pegasus/

16. make it better
designing, technically
A threat to the profession
• The Great Unicorn Quest
• Devaluing “pure” design
prepared for ga uxdi
tweet @skotcarruth

17. designing, technically tweet @skotcarruth
When you know the constraints of
your technologies, you can save
clients money and make your
make it better
developers happy.
prepared for ga uxdi

18. make it better
Technical Documentation
designing, technically
prepared for ga uxdi
tweet @skotcarruth

19. designing, technically tweet @skotcarruth
The more technical you are, the less
make it better
documentation you need.
prepared for ga uxdi

20. designing, technically tweet @skotcarruth
If you are very technical, you can
provide insight to developers
make it better
in your documentation.
prepared for ga uxdi

21. make it better
What is helpful to know?
designing, technically
prepared for ga uxdi
tweet @skotcarruth

22. designing, technically tweet @skotcarruth
make it better
Basic Markup
prepared for ga uxdi

23. designing, technically tweet @skotcarruth
make it better
On-the-job Learning
prepared for ga uxdi

24. designing, technically tweet @skotcarruth
make it better
Popular CMS’s
prepared for ga uxdi

25. designing, technically tweet @skotcarruth
Popular E-commerce Platforms
make it better
prepared for ga uxdi

26. designing, technically tweet @skotcarruth
make it better
Mobile SDKs
prepared for ga uxdi

27. designing, technically tweet @skotcarruth
make it better
Database Design
prepared for ga uxdi

28. make it better
How do I learn?
designing, technically
prepared for ga uxdi
tweet @skotcarruth

29. make it better
designing, technically
Where to learn
• Pair with programmers (or ask for feedback)
• RTFM
• Treehouse, Lynda, Code School, Codeacademy
• GA
• Just play with stuff
prepared for ga uxdi
tweet @skotcarruth

30. Questions?
internal only make it better