Dylan Goings at Atomic Spin

A Review of “Why Greatness Cannot Be Planned: The Myth of the Objective”

Stanley’s thesis about objectives involves this idea: intermediate discoveries may seem unrelated to an ultimate goal but are crucial.

Business Practices

Let Developers “Cheat” in Your Interviews

Love it or hate it, LLMs aren't going away anytime soon. So, let your candidates "cheat" in their coding interviews.

Development Practices

Enhance Discovery Phase Pairing: Techniques for Varied Skill Levels

I've championed the idea of "pair exploring" during the Discovery Phase. Today, I've got some strategies to amp up your discovery game.

Development Practices

Stop Pair Programming and Start Pair Exploring

Articles providing tips to pair program are ubiquitous. Instead, let's talk about pair exploring, including why and/or when to pair program.

The Software Life

All the Things That Don’t Make You a Great Software Developer

Neither graduating college with a degree in Computer Science nor working for a Fortune X company makes you a great software developer.

Artificial Intelligence

3 Strategies for Learning to Program with an AI Assistant

There's a real risk of AI becoming a necessary crutch. So, how can you take advantage of an AI assistant without becoming beholden to it?

Software Science

ChatGPT and the Value of a Computer Science Education

As someone who recruits graduates for their first jobs, I'm interested in how ChatGPT will impact the future of computer science education.

Web Apps

The Future of the Web is Hyperlocal

Hyper-specialized edge computing and WebAssembly: this is the hyperlocal future of the web, and it's right around the corner.

Project & Team Management

Rethinking Agile, Part 4: Start Estimating Value

I propose that we stop measuring throughput or velocity. Instead, companies should empower software teams to make value estimates on individual work items.

Project & Team Management

Rethinking Agile, Part 3: Stop Estimating Effort

In this third part of my Rethinking Agile series, instead of adding practices, I recommend something for you to remove. That is, stop estimating effort!

Project & Team Management

Rethinking Agile, Part 2 – The Stand Down Meeting

In Part 1 of this series, I suggested adding a “deload” period into your agile practices. In Part 2, another suggestion in the same vein: the Stand Down.

Project & Team Management

Rethinking Agile, Part 1 – Deload Periods

After sustained intense exercise, a deload gives your mind and nerves a chance to reset. I think it's time to bring this concept into software development.

Dylan Goings

Keep up with our latest posts.