I have spoken a couple of times at user groups, many times at a company but I never ever had spoken at a conference before until this week at Swetugg 2016. It was awesome!! Cecilia, Anders and all the organizers did a great job! Thank you very much to them, the sponsors and all the participants that made it such a cool experience. Thank you!!
Here is a photo of me in the middle of the fray (hehe). There was a tooon of people there but luckily the 10000000 Watt spotlight strategically directed right into my face made me feel as comfortable as sitting in my living room’s couch.
The talk was recorded so I’ll give you a shout whenever the recording is released. I’ll also record a three-part director’s cut with a slower pace and probably slight more content and put it up in the upcoming days.
I was doing some code katas last week and it suddenly dawned up on me how awesome data structures and algorithms problems are to practice TDD. They provide such a well defined problem space and expected API that you can fully concentrate in the red-green-refactor flow until it becomes second nature. One pass and you focus on the red-green-refactor, another pass and you can improve your knowledge of jasmine, another and you focus on sinon, another and you try to improve your abstractions, another and you concentrate on writing the most readable of tests, and so on until eternity :)
Not interested in practicing TDD? Don’t panic! You can use any of these exercises to practice other stuff, becoming more proficient and productive using your favorite IDE or text editor, learn new ReSharper shortcuts, new vim commands, functional programming, other languages, etc. Just decide what you want to practice in each session and be awesome.
And here are some other places where you can find lots of different exercises and katas:
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.
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.