I've been working on a few small AngularJS applications at work, and the last one I would say was a relatively small-medium one. The concept is how you should store the data and state of your webapp is something that can help you down the line or screw you over. "When you use regular two-way data binding with an object reference, when some data changes you don't know what changed it".
I've been doing a lot of automated testing lately, I just finished reading these excellent articles from Sauce Labs, Why is Manual QA Still So Prevalent? and Kickstart Your Automation Efforts which totally bash manual testing and prescribes that even the QA analysts run tests from that are automated scripts. I've distilled out the key points here to why a company should adopt automation over manual QA.
I was looking for a nice twitter bird outline today, and someone commented with a link to this great site that allows you to search for glyphicons: http://glyphsearch.com/. I had stumbled across this site before and forgot about it so I'm writing this blog post to help burn it into my memory. ;)
There are tons of different charting types to choose from, so how do you decide what's the best way to visualize your data? Well, I just found this excellent info-graphic while creeping around on Linkedin. Enjoy! :)
So I'm almost finished reading this book, BDD in Action, by John Ferguson Smart, and I think it is really a fantastic book. Despite the wacky, ugly-looking cover, this is a super-awesome software development book that pretty much revolutionized the way I think about unit testing- and I think a LOT about unit testing so this must be a pretty big deal. I would highly recommend this book to anyone trying to wrap their head around behavior driven development, but in this post I'm going to reveal the crux of BDD- spoiler alert!
The posts on this site are written and maintained by Jim Lynch. About Jim...