-

Sean Patterson

As the size and scope of a project increase, so does the complexity of the code base. One way to maintain and stabilize your code is to adhere to the “DRY” Principle: Don’t repeat yourself. #1: Use the DRY Principle to Decrease the Size of Your Code Base If you’re writing code to do the same

This year, Team Fresh and Furious took part in its annual RAGNAR tradition, but mixed it up a little and took to the trails for the RAGNAR Trail Rainier. With this being my third time participating with the team, I was triply excited for what the weekend would hold.

Donald Knuth is famous for saying “Premature optimization is the root of all evil.” There is a lot of good advice packed into that short statement.

At first pass, building a comprehensive application or API library seems straightforward. You want to make sure that every possible scenario is covered for proper data coverage and that the user can do anything (however small) they want within the app. However, the ramifications of this approach can be larger than you think. This has led

There will always be hackers looking to get into your website. Whether it is to deface it with their branding/cause, gain access to your data, or even turn your site into a distributor of malware, it’s important to make sure your code is secure against common threats. Here are a few of the most common vulnerabilities

Documentation is often the least popular thing to create when working on a project. It might seem pointless to make note of things you already know or are easy to setup. Even worse, it can take time out of your already busy (and potentially time sensitive) development workflow. However, having good project documentation, beyond simply choosing good variable names,