Category: Software Delivery

Great software project teams are able to produce application features quickly that provide users with the most amount of value. If you don’t have a UI/UX designer on your team, you’re risking the design of your application experience short-changing your users.

As a coder, the builder pattern is my go-to. It makes data setup extremely easy – instantiate a class, chain some methods together, and finish by executing a build method. However, every time I write a builder class, I can’t help but wonder if there’s a more functional approach that completely removes state.

During the 1990s object-oriented programming was beginning to take the software world by storm. C++ and Java were some of the most popular programming languages. Walking into a bookstore and browsing to the computer section you would find books of all sorts on object-oriented development and design.

Globals are bad. Data should be encapsulated and only available when needed. These are some of the first things you learn when you start to program. If there are multiple actors that can write to shared data, side affects can occur.

In the world of Agile software development, a natural tension has emerged between the engineering and UX functions.

Plumbing is software is any code related to wiring things together. This could be code that listens to queue messages. The code that listens for queue messages is plumbing code that is often written over and over again in applications.

Coding standards can get a bad rap.

In the age of Twitter threads and Instagram reels, it’s easy to get caught up in wanting to try out every hot trend promising to change your life.

“We should log that.” Developers often throw this phrase around, using it as a catch-all for any type of error or information storage. Although logs are an invaluable tool, they aren’t the only option for recording and tracking events. In this article, let’s dive into the differences between logs, metrics, and audits and their ideal use cases.

When people hear a project or product is open source, they understand that to mean it’s publicly available for anyone to view, modify, and distribute. InnerSource is open source ideology applied to an organization’s internal software development processes and projects. It’s a simple idea with the potential to transform your engineering culture. 

Without validation and testing, the software development process would be a mess. Engineers would deliver a lot more sloppy, broken code, and users would run into all sorts of bugs and issues. There’s no doubt — quality assurance is a critical part of software development. But what if we told you there’s a way to do QA differently?

Scrub away the grub.

Often times we’ll hear someone say “we should log that” but sometimes they mean something more.

Maslow’s Hierarchy of Needs is a model for understanding the motivations behind why people make the choices that they do.

What do you think of when you hear Extreme Programming (XP)?

We all know the benefits of coding standards.

This week’s Lean BYTES will be presented by Scott Sauber on “JWT Fundamentals.

Want to have fewer meetings?

Many companies question the value of a solid test automation practice.

Docker is a tool for containerization, but what does that mean and what is it good for?

A new request comes in.

Brian will briefly talk about how he has used a particular approach to almost ignore the concept of null values.

In this talk, we will learn how to easily get a few meaningful integration tests up and running without running any manual docker commands.

Product teams often find themselves with a lengthy wishlist of ideas and features stemming from stakeholders, executives and others inside and outside the organization.