In the previous article of this series I introduced the necessity of building flexible front-end architectures that let us adapt to changing requirements and particularly changing UX requirements that are more often than not neglected. In this article I’ll continue explaining how Lean UX practices work as a driver for that type of architecture.
Many of you may find the following situation familiar:
UX Designer: Could you improve this view so that when you make a selection here both of these charts are updated?
Software Developer: Hmm… No, I can’t.
or:
UX Designer: Could you make change X (which looks like it would be pretty straightforward) that would improve the UX of this view enormously?
Software Developer: That’s completely impossible because we didn’t design our framework to acommodate that use case. I could do it but we would need to make a major re-architecture and re-design of our application that would affect all these other views. There are also these 300 things with higher priority right now.
Well, I know I do. Particularly on the developer side of things.
Updated 16th October 2016 with Stamps v3! Yey!
The Mastering the Arcane Art of JavaScript-mancy series are my humble attempt at bringing my love for JavaScript to all other C# developers that haven’t yet discovered how awesome this language and its whole ecosystem are. These articles are excerpts of the super duper awesome JavaScript-Mancy book a compendium of all things JavaScript for C# developers.
In the last two articles of the series you learned about two great alternatives to classical object oriented programming: mixins and traits. Both techniques embrace the dynamic nature of JavaScript. Both encourage creating small reusable components that you can either mix with your existing objects or compose together to create new objects from scratch.
Object and functional mixins are the simplest approach to object composition. Together with Object.assign they make super easy to create small units of reusable behavior and augment your domain objects with them.
Traits continue the tradition of composability of mixins adding an extra layer of expressiveness and safety on top. They let you define required properties, resolve naming conflicts and they warn you whenever you’ve failed to compose your traits properly.
In this chapter you’ll learn a new technique to achieve class-free inheritance through object composition. This particular technique embraces not only the dynamic nature of JavaScript but also its many ways to achieve code reuse: prototypes, mixins and closures. Behold! Stampsstamps!
Dev Talk Monday is the series that brings you awesome dev talks every Monday… or Thursday XD
As you might know I love unit testing and TDD. I have been a little bit worse than usual at it in the last months though. Hence I said to myself, let’s look at a dev talk and get my test inspiration back up. And so, here it is, this awesome talk about how to stop hating your tests by the very charismatic justin searls.
And finally this is the last article on the books I read last year. There’s books of every size, color and topic in this one. From financial advice, to sales teachings, to biographies, mindfulness and getting things done. Take a look, you may find something you like.
