
Be ready to explain your code
Does the mere thought of explaining your code cause anxiety? Be confident! We should all understand what we’re writing and why. It’s an opportunity (for everyone) to learn!

Does the mere thought of explaining your code cause anxiety? Be confident! We should all understand what we’re writing and why. It’s an opportunity (for everyone) to learn!

Learning a little about programming could benefit anyone. If you want a fun intro to coding and logical thinking, check out Scratch!

When you’re writing tests, you generally don’t want to write to the database, email customers, and hit third-party API’s. That’s why we need to know how to mock dependencies!

Does the idea of submitting to a code review make you sweat bullets? Or do you brush it off as a necessary evil? It should be a (hopefully positive) conversation, wherein the team agrees to the code they’re all going to have to help maintain, and maybe learns something new too.

I just deleted my coworkers code. 😱 It was good code that wasn’t needed anymore, and he understood why. The nature of coding is that it’s a progression, and any individual code is transient by nature. Today’s code is subject to tomorrow’s refactoring.

All programming languages have gotchas to trip you up, and C# is no exception. Today, let’s check out the subtle (but significant) difference between “throw” and “throw ex”.

How do you know when you’ve finally arrived, and are officially a programmer? Is it a set of skills, a certain amount of time? Can you ever really arrive, when it’s a race of one with no finish line?

A few years ago, on the 30th anniversary of the Legend of Zelda, Scott Lininger and Mike Magee open sourced a 3D version of the original LoZ. The site was taken down, but the code’s still available to run!

We’ve all seen word clouds, like in the sidebars of blogs, but let’s see how we might create our own with a little bit of code!

Windows sets certain locations aside for apps, and makes them easily discoverable for devs to use. Let’s see how.