The SAS Workshops Blog

Goals

2022 In Review

Here's just a look back at 2022, all the things that worked and those that didn't.

Coding Philosophy

The Programmer's Brain

Ultimately all problems are human problems and all humans have brains. Understanding how our brains work can be very useful.

Python

Python For Scientists and Engineers

If you are looking to expand your skills beyond LabVIEW, Python is a good choice. I recently took Enthought's class. Here are my thoughts.

Announcements

Advent Of Code 2022

It's almost time for Advent of Code again this year. If you haven't joined the leaderboard, and the Discord, what are you waiting for?

Python , How to

Using Python Classes In LabVIEW

Now in LabVIEW 2022 Q3 you can use Python objects with the Python Node. Find out how.

Python , SCC , How to

Using Git Hooks

Git Hooks can be quite useful for a variety of things. Here is a simple example to make sure you don't forget to include an issue # in your commit message.

Coding Philosophy

Generosity

By making your tool Open Source you are not losing out. You are actually gaining because you are allowing the community to contribute.

Coding Philosophy

Metrics

Metrics are always an interesting topic. What do you measure and why? And how do you keep people from gaming it?

Coding Philosophy

The Need For Speed

When making decisions you need a true north. You need a litmus test. Here is a case for why speed should be that litmus test.

Legacy Code , Coding Philosophy

Thoughts On Technical Debt

What does the phrase "technical debt" mean to you? How do you deal with it?

Coding Philosophy

Normalize Paying For Open Source Tools

If we want our favorite Open Source tools to continue to be maintained we need to start supporting the maintainers.

Book Reviews , Business

Go For No

The number one challenge faced by most LabVIEW Developers turned consultants is sales and marketing. This book can help with the sales part.

Coding Philosophy

The LabVIEW Experiment

You may have heard rumors that I started a podcast. "The LabVIEW Experiment" is a place to discuss how to improve our craft and make coding fun again.

Coding Philosophy

Be The Developer Everyone Wants On Their Team

How can you become the developer that everyone wants on their team? Here are a couple ideas.

Coding Philosophy , Legacy Code

Thoughts On Rewrite Vs Refactor

Rewrite or Refactor? Every developer has faced that choice. What should you consider in making your decision?

Coding Philosophy

Maxims to Code By

Maxims are little phrases that we use to remind ourselves of what is important. Here are some that I use when writing code.

Coding Philosophy

Effective Time Management

As coders, we often like to work in large blocks of time, but that's not the only way. Here are some other techniques that can help.

Coding Philosophy

What does being a software architect mean?

I was recently asked: "What does being a software architect mean?" Here is my answer.

Coding Philosophy , Conferences

Improving the Human Experience

We don't write code for the compiler or the CPU. We write it for other human beings. Both user and developer experience are crucial.

How to , SCC

Latest Version of Git Broke LVCompare Usage

The latest Git update broke my LVCompare setup. Here's how I fixed it and how you can too.

Book Reviews

Measuring History

"Measuring History" tells the history of National Instruments and the impact it has had on the world.

Coding Philosophy

Tackling Problems From Both Ends

The best way of tackling a problem is often from both ends, ie top-down and bottom-up.

Book Reviews , Coding Philosophy , DevOps

Thinking in Systems

This book is a recipe for social and organizational change. It is about predicting and influencing the complex systems we've built.

Coding Philosophy

The importance of common language

In order to see things, it is important to have words to describe them. Words are how our brains categorize and store knowledge.

Book Reviews , Coding Philosophy , DevOps

The Phoenix Project

The Phoenix Project is a must-read book for anyone who works in technology. If you have ever worked in a larger company you will immediately identify with the situation described at the beginning of the book. You have an overworked IT department that seems disorganized and is always behind on