SEP Blog

We’re curious people by nature. And we love to teach others what we’ve learned. So explore our blog to gain fresh insights from our expertise in areas ranging from culture to AI.

SEP Named A 2021 Best Places to Work in Indiana Company

void Function() { try { RunOtherFunction(); } catch { Log.Error( "Problem" ); } } void RunOtherFunction() { if ( a_okay() ) { OtherFunction(); } else { throw new Exception( "Error" ); } } Exceptions are a thing that we…
Read More

Code Analysis: Exceptions

void Function() { try { RunOtherFunction(); } catch { Log.Error( "Problem" ); } } void RunOtherFunction() { if ( a_okay() ) { OtherFunction(); } else { throw new Exception( "Error" ); } } Exceptions are a thing that we tend to use for signaling error conditions such that the error will be dealt with in […]
Read More

Code Analysis: Global State

Global mutable state by itself can make a program harder to work with because instead of  having a call tree that’s simply a tree structure, you end up with more of a graph structure.  Any given point in the program that interacts with the global state can be effected by any other point in the […]
Read More

Code Analysis: Abstract Data Type

Abstract data types are a pretty well known concept in computer science and software engineering.  The concept is pretty simple.  If you have something that is complicated, then you can make it easier to deal with by only exposing an API that allows you to safely interact with the complicated component.  Of course also known […]
Read More

Code Analysis: Fluid Call Tree

Let’s elaborate on the nature of these call tree diagrams.  Consider the following code: void doStuff() { doOtherStuff(); } void doOtherStuff() { init(); final(); } void blah( int x ) { if ( x == 2 ) { function(); otherFunction(); } else { doStuff(); } } Depending on the input for the blah function, we […]
Read More

Code Analysis: Shared Mutable State

My previous post asserts that mutable state can cause a software engineer issues in understanding the program because it becomes arbitrarily hard to understand when two different parts of a program are actually connected.  This is also why some sort of run time debugging facility is needed in order to understand some types of code. […]
Read More

Code Analysis: Mutable State

Mutable state gets a bad rap when you talk to pure functional programmers.  I don’t think mutable state is inherently a problem, but it does have an effect on your ability to understand a program.  So let’s look at what happens when you introduce a mutable reference into a programming language. The problem as I […]
Read More

Code Analysis: Halting Problem

Let’s do a quick digression.  I wanted to talk about mutable state, but first I think we should consider the halting problem. The halting problem goes something like this: Halt( program_source, program_input ) { if ( <The program Halts with that input> ) return true; else return false; } // Now assume a hypothetical program […]
Read More

Code Analysis: Introduction

There already exists a significant amount of code analysis techniques out there.  I think the existing technologies are pretty useful for tracking some aspects of why a given piece of code can be difficult to deal with.  However, I want to add a diagram technique that can be used to describe certain features in programming […]
Read More

Problem Analysis: Overlapping Blobs

Last time we started to explore the idea that you can have a system or problem that is difficult to deal with and understand because the interactions between blobs are in some way difficult.  However, we only covered the idea that the arrows that connect blobs are complicated.  There is a similar problem when we […]
Read More