Proper Code Styling
·
I look at a lot of code. In my job, recreationally on weekends. Everywhere I see people using a specific coding style and, upon pushback, defend it in the sake of brevity. I’m talking about braceless one-line conditionals.
·
I look at a lot of code. In my job, recreationally on weekends. Everywhere I see people using a specific coding style and, upon pushback, defend it in the sake of brevity. I’m talking about braceless one-line conditionals.
·
If you’re reading this, you’re probably in my target reader group. If you have left a comment previously, you’re definitely in that group. So, unscientifically, what prompts you to leave a comment and engage in the conversation?
·
Today, I wanted to share some tips for picking article topics when you’re otherwise faced with writers’ block.
·
How secure are you? Really?
·
While Git (and Mercurial) is a lifesaver when it comes to easily branching, tagging, and resolving merge conflicts, Subversion (and TFS and the like) is superior when it comes to sub-project management.
·
My ideal blogging app/content management system/application platform would take the entire stack into account.
·
I get to keep telling stories for my customers, and I get to keep writing my own as I go.
·
I speak at conferences not just because there’s something cool I want to present, but because there’s something cool I want to learn.
·
When I explain to people that I enjoy writing code in C# more than PHP, they scratch their collective heads and, with a quizzical look, always respond, “why?” My biggest reason: I really enjoy working with parallel processing.
·
I write every day. I also publish a blog every day – even if what I wrote that day wasn’t publishable.