Jake Trent

In Favor of Codenames

It seems to be a recurring discussion in the companies I have worked for: should we use a codename for this project or not? These are software projects. The codenames are used on things as basic as the repository name or slack channel. Later, they might be used in many other project-related things like the build server configuration. The alternative for a codename is calling the thing exactly what it is. Where’s the fun in that?

Read more

Make Software in the Estuary

An estuary is where the sea meets the river. Here, there is a mix of fresh water and salt water, sediment from the rivers and marine life from the sea. The effects of both sea and river are seen in many ways. It’s a swirl – there’s no upstream or downstream. It’s considered to be one of the most nutrient-rich, productive ecosystems on the planet. So really, who wouldn’t want to make software in an estuary?

Read more

Agile Designers

The Agile method of software creation contains many principles of development that will help create good software. Some of my most successful projects have had as a key feature an agile designer. As Jobs said, design is how it works, and that means that to really deliver well in an agile environment, design and development have to be on the agile train together.

Read more