Use these analogies to explain to your friends and coworkers just what it is you do all day. Also check out the meme version of this post [http://www.exceptionnotfound.net/useful-software-development-analogies-meme-version] . Writing Code Writing code is like putting windshield wipers on your car, only if you fail to install
(AKA How To Sound Smart At Your Next Team Meeting) Occam's Razor This widely-known adage dates to a philosopher and friar from the fourteenth century named William of Ockham [https://en.wikipedia.org/wiki/William_of_Ockham]. Occam's Razor [https://en.wikipedia.org/wiki/Occam%27s_razor] is often stated
I often give technical demos at my work about various topics, and the most recent one was an introduction to ASP.NET Core 1.0 that spawned a lot of blog posts [http://www.exceptionnotfound.net/tag/asp-net-core/]. Overall, this class was well-received (at least I believe so, given that
What makes a quality programmer? In a previous post I listed out five "personas" that I believe make an effective programmer: coder, investigator, theorist, logician, communicator [http://www.exceptionnotfound.net/five-personas-of-an-effective-programmer/]. I still believe that each of these traits are essential to being an effective developer, but there's one trait
I'm doing some heavy refactoring on a project that I've recently joined but that has been underway for months. The code is a mishmash of different styles [http://www.exceptionnotfound.net/big-ball-of-mud-anti-pattern-primers/] and an uncertain architecture, so my task up to this point has been to make it more consistent,