Tag Archives: Programmer

The Things We Say

I want to retire certain phrases from programmer parlance.

TL; DR

We are not clear in what we say. We use incorrect metaphor. We choose vague terms instead of better ones. Let us trim some of the excess terminology and jargon.

We use incorrect metaphor. We choose vague terms instead of better ones. Click To Tweet

Technical Excellence

This terms vagueness is its undoing. Almost everyone I meet has a different definition of what Technical Excellence means. To some it is a synonym for Extreme Programming. To others it is learning design patterns or continuous improvement.

The above assumes that the person saying the term has good intentions. I have also heard this term used as a passive aggressive way of saying that someone is a poor programmer, by telling them to strive for technical excellence without specific feedback. Calling someone a poor programmer without giving guidance on what needs improvement is useless at best, discouraging and defeating at worst.

Instead of using technical excellence, let’s say what we mean. If that is Extreme Programming, let’s say Extreme Programming. If it is adherence to corporate coding standards, then document the standards and talk about the standards document. If we want to critique someone, take the time to critique them in a way that is helpful. Encourage growth and improvement rather than attacking.

Simple

Again, simple is an extremely vague term. What is worse is that we acknowledge how vague this term is by modifying it with: Simple isn’t easy. As if this sound byte could explain what we mean. This suffers from all the problems of “Technical Excellence” and really doesn’t say anything useful.

We spend so much time talking about making things simple and then engaging in a long conversation quantifying what we mean. Why do we do this? The term “simple” just causes confusion, debate and eventually is shortly forgotten.

It is amazing to me how much energy we spend saying nothing rather than what we mean. If we could talk specifically about the types of complexity we want to avoid, we allow for improvement. We start the conversation that moves us into a better place.

Remove confusion, add clarity and forget simple.

Technical Debt

Technical debt was a good metaphor. Past tense. It was created for a specific reason, it was to explain the causal effect of decisions to bankers. It was not created to discuss the state of the code between developers. So, let’s stop using it for such communications!

Instead of technical debt, let’s talk about Anti-patterns or Code Smells. Both have names for specific things that can be addressed. They can be researched and understood. Better yet, there are know ways to move from these potential problems to good patterns.

Lastly if we are talking about the state of code caused by a ignoring problems over a long time, then even the team “Code Rot” is better at describing what needs to be said. There is real meat in using directed language to discuss the state of a codebase between developers.

In Short

Stop being vague right now. Don’t mix your metaphors. Be clear and intentional. If there is better language that can be used to describe what you want to say, then use it. Increase your ability to be understood by thinking about what you are saying.

Stop using 'Technical Excellence', 'Simple', and 'Technical Debt'. Start communicating effectively. Click To Tweet

About

R. Jason Kerney

Working For: Some Company, San Diego

Position: Agile Technical Coach

Experience: Around 17 years

Hobbies: Programming, Playing Board Games, Reading, Public Speaking, Spending time with my family

Note: Oh by the way, all opinions and ideas are my own and do not represent the place I work.

I am a developer who has benefited greatly from the programming communities of San Diego. Now I try to give some of that back. I have been a programmer for many years and have recently (2yrs) been focusing on the soft side of software; the people and the business.

Contact me, we are only a community if we communicate. I am most easily reached on twitter: @JasonKerney

Me

Twitter

https://speakerrate.com/speakers/177671-jason-kerney

https://www.linkedin.com/in/jasonkerney/

https://registry.jsonresume.org/JasonKerney

Current Talk

None at the moment

Git Hub

https://github.com/jason-kerney

Twitter

How to find me on the web

Publications:

Talks

2017

2016

2015

2014

2010

2009

2008

Places I Have Contributed:

Programming Contributions:

Tutorials I Contributed to:

Contribution as a Conference Reviewer:

Meetup Session I Helped Run:

RPG to Learn Mob Programming

Tuesday, May 8, 2018, 5:30 PM

Hunter Industries
1890 Diamond Street San Marcos, CA

20 Members Went

Have you heard of the Mob Programming RPG? Learn the roles that best support the mob programming paradigm including Navigator, Driver, and even the Rear Admiral. For those who can make it early, the first 30 minutes (5:30 – 6:00) we’ll be networking. There will be light snacks. Since this meetup doesn’t have a sponsor yet, we’re depending on the ge…

Check out this Meetup →

People Who Took Interest:

Blogs about Me:

Interviews I Have Given:

Interviews I Have Given on Pod Casts:

Places Where I am mentioned:

Slides: