02 Wednesday Aug 2017
Posted in Stories
Sometimes ya gotta laugh. I just spent nearly an hour chasing one of those bugs that “can’t be happening” because “the code looks absolutely correct (as far as I can tell).” Of course, the bug, once you find it, was always hiding in plain view.
This time the fix involved adding just two characters, incidentally improving the program semantics, and very much reminded me of the old joke about the huge cargo ship that breaks down at sea…
19 Monday Dec 2016
Posted in CS101
Tags
computer language, computer languages, computer programming, computer science, GOTO statement, iteration, language design, loop statements, programming language, recursion
When it comes to what makes a computer (or any other) language a programming language, there are three characteristics usually required:
This post is just a brief note (for a friend) about the third item and why it allows three distinct options.
06 Saturday Aug 2016
Posted in CS101
Tags
computer language, computer languages, computer programming, computer science, language design, programming language, Turing complete
Back in the post HTML is not a programming language! I brought up the three properties required by a programming language. A discussion recently got me thinking about it again. This post is just some notes on those thoughts…
25 Wednesday Nov 2015
Posted in CS101
Tags
computer, computer code, computer programming, computer science, Python code, state engine, state table
In the first two parts of this series I’ve introduced state engines and taken apart a specific instance of an engine. Now it’s time to tie together the design idea with approaches to building a variety of such engines.
Because the programming logic is in the state table, the engine can be fairly generic. That means it’s possible to create a state engine framework you can reuse for a variety of applications.
11 Wednesday Nov 2015
Posted in CS101
Tags
computer, computer code, computer programming, computer science, Python code, state engine, state table
Last time I introduced state engines and state tables. I showed parts of a simple implementation of one in Python. It parsed the language introduced in Little Programming Languages. This post continues that, so be sure you’ve read that first article.
I got as far as the state table implementing the process, and that’s where this post picks up. I’ll also get into the SourceReader class that does the heavy lifting.
08 Sunday Nov 2015
Posted in CS101
At one point in my career, the state engine (SE) was one of my favorite AWK hammers. At the time much of the work involved text processing or, in some cases, serial byte processing (which is not quite the same thing). That sort of thing is right in the wheelhouse for a state engine.
They are a very useful tool and an important part of any programmer’s toolkit.
05 Monday Oct 2015
Posted in CS101
Tags
computer code, computer programmers, computer programming, programming language, real programmers, software development
There is a common tendency, as we crank out code, to think that we’ll come back later and write some really good comments — comments that future reviewers will view with admiration for their clarity, completeness, and humor. But if we’re honest we have to admit: Later never comes. We never go back and write those great comments. Often we don’t write any comments at all other than some placeholder we might dash off at the time.
Which is why Rule #4: Comment As You Go!
23 Monday Jun 2014
Tags
computer programmers, computer programming, project estimation, project management, software design, software development
Last week I took my car in for scheduled service, and when I asked how long it might take, the guy said it was specified as one-and-a-half hours of labor. He could do that because there are thousands upon thousands of data points where a competent mechanic has performed that exact service, so there is a very clear idea how long it takes.
But ask a researcher how long it will take to find what they’re looking for, and the answer is usually, “I have no idea. I’ll know after I find it.” The path a researcher follows is usually new and unexplored, so it’s impossible to predict how long the path actually is.
Creating new software is much more like research than auto service, because it involves traveling unknown ground. Despite this, software development managers often act as if new development is predictable.
It often isn’t!
20 Friday Jun 2014
Posted in Fun
Tags
50 Ways to Hose Your Code, 50 Ways to Leave Your Lover, backups, computer programming, Friday, funny, funny songs, humor, parody, Paul McCartney, Paul Simon, song parody, Yesterday
It’s Friday again, so it’s time to get casual and have some fun. Today I have a pair of songs for computer programmers. These files have been occupying bits on my hard drive for many, many years. I’m releasing them to the Wild World Web so they can live free!
You know the tunes, so sing along to the new words…
16 Monday Jun 2014
Tags
computer programmer, computer programming, computer science, software, software design, software development
Computer Programming is hard! It’s at least as hard as what commercial architects do, and I will argue that it’s as intellectually difficult as what doctors and lawyers do.
Many people think it’s easy, because they know some nine-year-old who “programs,” but there’s a difference between fooling around with the computer and building good software applications.
