I normally don’t get giddy over trance these days but FFFFUUUUAAARK
dnb with a swing beat? not bad
Interesting “tip” I found here:
Agile Quality Tip #3 - Catch as Many Errors as Possible Before QA
As both a developer and a qa engineer, I am inclined to say, “well, duh.”
If you are developing something, actually test it. The less bugs your QA team finds, the less turnaround time to fix those defects and deliver a product. This is true for agile and waterfall methodology. True, QA is there for those edge cases but developing code that isn’t adequately tested by the developer to cut time out in the dev cycle will cause trouble down the line.
Standing around, chatting with some co-workers after a meeting when suddenly a wild manager appears:
“So, is this one of those stand-up meetings I’ve heard so much about?”
“Nope, just a stand around meeting.”
(Source: youhadafastlifee, via jl0ve)
![fitspo-for-me:
]](http://25.media.tumblr.com/tumblr_ly937mIYqY1rnk8feo1_500.jpg)
