Coding Philosophy

A collection of 120 posts

Coding Philosophy

Simplest Thing That Could Work

It seems like I have been giving the same piece of advice lately: Start with the simplest thing that could possibly work and only add complication as you need it. Sometimes our natural tendency is to plan for all eventualities. We get so caught up planning for what might happen,

Coding Philosophy

Forget the word but

In improv, there is this idea called “yes and”. The idea is that the first person goes and starts telling a story. The second person (and everyone after them) picks up with “yes and” and then continues adding to the story. What you want to avoid doing is using the

Coding Philosophy

The Freedom of Refactoring

Let’s talk about software design and refactoring in LabVIEW. When I first read Martin Fowler’s Refactoring book several years ago, it was very liberating. Prior to that, I had always had the idea that I had to get things right up front. It was kind of paralyzing. I

Sam On Joel , Coding Philosophy

Choosing a Language

I’ve decided to start a new series. I recently bought the book “Joel on Software” by Joel Spolsky. It is a collection of his blog posts. He still continues to produce more content today. Some of the articles in this book are a little dated but they seem to

Coding Philosophy

Coding Camps and Climbing Gyms

I have been a programmer for over 15 years and a rock climber for over 20. During that time I have seen a lot of changes in both. In some ways, the changes are very similar. Rapid Growth Both programming and rock climbing have taken off over the past couple

Coding Philosophy

Informative Versus Transformative Learning

In the technology field, particularly programming I feel like we tend to focus a lot on informative learning. Informative learning is just building upon what you already know. For instance, if you already know how a for loop works in C, and then you learn how to implement it in

Coding Philosophy

Two Questions To Improve Your Software Development

Learning is about asking the right questions. When I get a new client, I need to learn about their business and their software development process. I ask lots of questions. There are 2 questions that always seem to lead to the most insight. Asking these questions of ourselves can generate

Coding Philosophy

Soft Skills for Software Development

We tend to equate writing software with technical skills. It certainly does involve some technical skills, but really writing great software is all about human skills, often called soft skills. It’s all about how you interact with other people. Typically you are working in a group and even if

Coding Philosophy

Debug Driven Development

Recently on episode 5 of the DQMH podcast, Chris interviewed Joerg of Hampelsoft. There was a lot of good conversation, but one of the things that stuck with me was the idea of Debug Driven Development. That is writing code in such a way that it is easy to debug

Design Patterns , Coding Philosophy

Keystone Pattern

Reading the Continuous Delivery book recently has got me thinking a lot about ways to achieve continuous integration while still adding new features. The book suggested Branch By Abstraction as a way to avoid stepping on each other’s toes. It also mentioned the Keystone pattern. The real problem the

Coding Philosophy

Dive into the source

If you have been following this blog, it should be no surprise that I listen to the Maintainable podcast. It is a great resource. The other day I was listening and I heard a clip that really spoke to me. Justin Searls is talking about debugging and not being afraid

Coding Philosophy , Community

DQMH Podcast Interview

I had previously mentioned the DQMH podcast. Chris just posted an interview that I did with him a few weeks ago. If you are interested in what we are doing here at SAS Workshops and learning more about how we can help you, then be sure to check it out.

Coding Philosophy

Tech Debt Day

A friend of mine posted the video below and I was immediately struck by it. Guilty as charged. I am definitely a procrastinator in many areas of my life. If you watch the video until the end, you’ll find out that we all are on some level. Even if

Coding Philosophy

Practical Versus Theoretical

I am a big believer in personal development and growth. One of the things that often keeps us from growing is lack of awareness. There may be certain ways that we present ourselves or ways that others perceive us that we aren’t aware of. I did an exercise recently

Coding Philosophy

The Problem With Solving Problems

As engineers we pride ourselves on problem solving. That’s what we do. However I find the use of the word problem to be somewhat problematic (pun intended). When we use the word problem, typically we are referring to something that is not working. Often it was working, but for

Coding Philosophy

T Shaped Knowledge

I saw post about a similar graph on social media recently. Someone posted it on twitter, but I don’t remember who. I thought it was interesting and that it would make a good topic for a post. The graph above represents someone’s depth of knowledge. In this case

Coding Philosophy

The Zen Of LabVIEW

Simple is better than complex. Straight wires are better than bent. We read left to right, let’s wire that way. BD cleanup is often better than a messy diagram. White space is your friend as long as everything fits on one screen. Subvis are also your friends. Use them.

Coding Philosophy

Workability versus right and wrong

Very early in my programming career, I was very dogmatic. I learned one way to do things and that was THE right way and anyone who didn’t do it that way was doing it wrong. I really wasn’t afraid to tell people that either. Obviously starting with “Your

How to , SCC , Coding Philosophy

Changing Git's default branch

In the wake of the protests surrounding George Floyd’s death and the resurgence of the #BlackLivesMatter movement, there has been a lot of talk in the tech community about changing some of the terms we use. There was a lot of focus on moving away from using master and

Coding Philosophy

What does scalability actually mean?

So recently the question of scalability came up on an NI forum post. Stephen Loftus-Mercer (aka AristosQueue) made a very interesting point. He talked about how scaling can mean many different things to many different people. A solution that is scalable on one axis might not be scalable on another.

Coding Philosophy

Every Crisis Is The End Of An Illusion

So I read a book earlier this year called “The Secrets of Consulting”. It was a very good book. You can read my review here. There was one part of the book that I didn’t put in the review that really stuck with me. I have been thinking about

Coding Philosophy

Hiding in Complexity

I have this problem. I procrastinate. Not all the time, but often. The thing is you wouldn’t notice it just by watching me. I always appear to be busy. The problem is I often hide in complexity. The best example I can come up with is when it comes

Coding Philosophy , Resources

The Value of Software Quality

So I stumbled upon a few things recently: * a J.B. Rainsberger presentation about “The Economics of Software Development” * a video by Andrea Goulet that touches on some similar issues (thanks Fab for recommending!). * a video by Jessica Joy Kerr on “The Secret to Software Quality” To me they are

Coding Philosophy

To Depend Or Not To Depend

The whole idea of using open source libraries and whether it is even a good idea to include dependencies in our projects at all has been on my mind lately for a variety of reasons. I have been listening a lot to the maintainable podcast and there is a lot

Coding Philosophy , Unit Testing , Kata

Importance of practice - Katas

So I have been listening to the maintainable podcast a lot lately. There is a lot of talk on there about doing coding katas. It also comes up a lot on twitter. I had never really done any. Then I took a udemy class on TDD in Python and it