I ran into a situation recently where I accidentally merged an unfinished feature branch directly into master. I had been working on the feature and got an urgent hotfix request. Without thinking, I branched from the feature branch to perform the hotfix changes, then merged that directly into master once
I’m sure many of you have heard of Markdown, which is a plain text format for writing structured documents. Developed in 2004, it is in wide use throughout the internet and has simple syntax: Heading ======= Sub-heading ----------- h3. Traditional html title Paragraphs are separated by a blank line. Let
Remember that scene in Family Guy, where there are two guys in a coffee shop and one asks if the other will watch him work? You don’t? Okay, fine: > Guy #2: Hey, getting some writing done there buddy? Guy #1: Yeah, setting up in public so everybody can watch
Why does Microsoft insist on developing the EntityDataSource [http://msdn.microsoft.com/en-us/library/vstudio/cc488502(v=vs.100).aspx]? I really don’t see the benefit. It’s just adding bloat to Entity Framework, especially since most people are moving away from Web Forms in favor of MVC. It
One question I see around the interwebs a lot is why strong and em should be used over b and i. If we look at the HTML 4 spec [http://www.w3.org/TR/REC-html40/cover.html#minitoc], it lists b and i under the Font style [http://www.w3.