If you’ve written front-end code for more than a year or so, some of the items on this list might seem obvious to you. However, I suspect this will not be the case for everyone. I have discovered that many very experienced developers have made conscious decisions to avoid styling. Continue reading 7 Tips for Writing Better CSS/SCSS
This is adapted from a talk I gave at DenverScript last year. It covers basic testing principles, introduces Angular and a little bit about how to put the two together.
We’re going to be starting from the conceptual basics of testing. I hope that starting at the beginning will be helpful to newer developers and put this all into context.
At the end of this post, you will be able to…
- Talk about foundational testing concepts using the right terminology
- Talk about an Angular application at a high level
- Discuss the differences between isolated unit tests and integrated unit tests, and when to use each in the context of Angular
- Know the difference between shallow and deep integrated tests
- Go back to your own Angular code and get started with writing unit tests
I make web applications for humans. In theory, these applications are designed for all kinds of humans. Yet, for some time, I’ve had this uneasy feeling that I haven’t been doing enough to make the products that I work on accessible for more than one kind of person – a person like me.
With that in mind, I recently attended a few workshops and talks on accessibility. I am taking what I learned in those sessions, combining it with some additional research and ideas, and presenting it to you here.
There used to be professions, and I suppose there still are, where one could complete a curriculum that would cover almost anything that they might have to do throughout their career. One could, for the most part, be trained to do a set of tasks and repeat them over and over until retirement. That type of work is rarer these days. Repetitive tasks tend to get automated and we humans are left to do the tough stuff – you know, thinking. I believe this is becoming true in most modern professions, but nowhere is it more in-your-face than in the world of programming.
Continue reading Learning to Learn
I started learning Ember about two weeks ago. It’s been an interesting process to figure out how the pieces work together and, in a lot of cases, what the pieces actually are. In this post, I am going to focus on those individual pieces of an Ember project and how they work together. Spoiler: It is probably witchcraft that makes the Ember magic happen. That’s where I’m at right now.
First, let me just say that Ember is a simple, straight-forward, intuitive MVC that is easy for beginners to jump right into…
Developers are lazy.
At least the good ones are. Beyond that, we have too much to do and too little time. For both of these reasons, we are constantly searching for ways to use less effort to create more results and we do this by finding patterns in the way that we build things. We then use those patterns to invent ways to build those things faster.