POST DIRECTORY

Agile

 

DRY is excellent coding advice: “Don’t Repeat Yourself.” Repetition in code means if something needs to change, all that repetition may need to change with it. This advice often comes with warnings, though, that you don’t want your code to become too DRY.

Somewhere along the way, we understood that a one-liner in our code is a liability if it’s...

 

Earlier this year, I was discussing features for a project with the team. I casually mentioned YAGNI in response to one aspect of a feature that seemed unnecessary. It had been a while since I’d brought up this term and a couple newer developers on the team were puzzled. I paused and realized this wasn’t something they were familiar with. So...

 

When we decided to make a company t-shirt, we didn’t just want it to be our logo and company name. We felt it needed something more, but nothing stood out to us. We worked through different concepts, pondering what our message should be. As elements of the design started to come together two ideas bubbled up that not only resonated with how we...

 

I recently read a post by Jocelyn Goldfein on The Right Way to Ship Software. It’s a great article that covers how different companies ship software. It’s well worth the read if you haven’t done so already. Over the last 17 years of shipping software, I can relate to her take on things.

At Haught Codeworks, we’ve had many types of clients and...

 

On a daily basis, developers are called upon to make decisions about the exact details of how to implement a feature request. For a small feature that takes 1-2 days, there may be a dozen tiny decisions and a few big ones. As developers, we try to anticipate these decisions when discussing the feature request with the client. Even so, we always...