Lately I've been on something of a design patterns kick, from realizing that patterns are tools, not goals [https://exceptionnotfound.net/software-design-patterns-are-not-goals-they-are-tools/] to developing and recording an extensive course for my employer and my fellow programmers at my current employer. It's been enlightening, to say the least. In fact, I
I've been working on an upcoming modeling practice [https://exceptionnotfound.net/tag/modelingpractice/] blog post and I needed (once again [https://www.exceptionnotfound.net/simulating-candy-land-in-net-part-2-programming-the-game/] ) to implement a card-shuffling algorithm. As always, I turned to the trusty Fisher-Yates shuffle [https://en.wikipedia.org/wiki/Fisher%E2%80%93Yates_shuffle] to
I went through a phase earlier in my career [http://www.exceptionnotfound.net/be-like-us-or-else-desperation-failure-and-new-job-regret/] where I thought design patterns were the be-all, end-all of software design. Any system which I needed to design started with the applicable patterns: Factories, Repositories, Singletons, you name it. Invariably, though, these systems were difficult
Use these handy memes to explain to your friends and coworkers just what it is you do all day. Here's the text-only version of this post [http://www.exceptionnotfound.net/useful-software-development-analogies]. Writing Code Image is modified from KUKA Industrial Robots IR.jpg [https://commons.wikimedia.org/wiki/File:KUKA_Industrial_
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