During my first year in graduate school, I had an epiphany about mathematics that changed my whole perspective about the field.

Looking to optimize your development pipeline? Having as much information as possible before you start developing could save you an entire iteration.

Code is the primary (but not the only) form of documentation. But like any documentation it can be clear or gibberish, programmers need to value clarity and learn how to achieve it.

Here’s a story of a team that had a serious problem which it didn’t recognize at first. The program manager and agile coach who saw the problem decided not to intervene. They provided space to the team to fail, learn from its mistake, and take action. The story shows that sometimes doing nothing can be the best thing that you can do to implement lasting change in organizations.

When you create a painting, you start with an inspiration and sketch it on paper. You then prepare your oils, brushes, and canvas, and you refine the painting until it’s just right. I follow a similar process with generative art.

In the movie Star Wars: Episode IV—A New Hope, the Death Star was designed to be the perfect weapon, with enough firepower to destroy a thousand star systems. Yet a small, ragtag group was able to blow it up. If only Emperor Palpatine had consulted with testers, all of the Death Star’s vulnerabilities could have been found and addressed!

Since I spend most of my day in the console| PowerShell also serves as my Excel. So| continuing my recent trend of PowerShell related posts| let’s dig into a quick and easy way to parse up CSV files (or most any type of file) by creating objects!

A simple example of how it can be easier to make a change by first refactoring the code to make the change easy.