In the last post, we spent a small amount of time understanding a problem faced by our hypothetical novice programmer, Ned. As a reminder, let’s revisit Novice Ned’s breakdown of the problem. Launch FTP Connect to the host Log in with the foobar user and password Change to the appropriate remote directory Put each of… Read More »
In an earlier entry, I covered the first thing a programming novice needs to know: how to break down a problem. A short while later, I was talking with a guy at our local Perl user group and he presented me with an actual novice problem he was fighting. After some thought, I realized that… Read More »
When I originally approached this topic, I wanted to explain to those GUI users why a TUI is more powerful. As I tried to write down my opinions, I realized that once again this was more a case of it depends than I had thought. I really should know better by now. In order to… Read More »
As I said in the last entry, you can separate computer users by their user interface preferences. In that entry, I made the argument that a text-based interface (TUI) is better than a graphical interface (GUI). Since that isn’t inflammatory enough, I’m now going to argue that GUIs are better than TUIs. A Short History… Read More »
One of the ways that you can separate groups of computer users into groups is by their preferences in user interfaces. A few decades ago, most computer interfaces were simple text. The display hardware didn’t support fancy graphics, and the processors weren’t fast enough to do the calculations needed for reasonable graphics. As computers and… Read More »
The first skill a new programmer must learn is not what most people expect. It is not learning a programming language. It has nothing to do with algorithms or data structures. The first thing a new programmer must learn is how to identify a small piece of a problem. Solving the Big Problems Most problems… Read More »
Between my earlier career in electronics and my current career in software, I have found a number of questions that have been helpful in troubleshooting problems reported by others. None of these questions are original to me. My wife described troubleshooting a hardware problem over the phone and mentions some of her troubleshooting questions. I… Read More »
In the last post (Coding Style: Terse vs Verbose), I laid out some of the arguments for and against a verbose coding style and a terse coding style. Although, I didn’t delve deeply into what I meant by these styles, I hoped the details were less important than the general feel. However, by the end… Read More »
One coding style issues that causes many arguments is the distinction between the Terse/Elegant/Succinct style and the Verbose/Legible/Debuggable style. As usual, each side explains that their style is the only rational choice and that the other approach is obviously wrong. First, let’s look at the two styles to see what they say. In order to… Read More »
One problem with comparing different programming languages is finding a valid comparison. It’s pretty hard to really compare two different languages. On the other hand, it’s pretty easy to compare example code from the two languages. Unfortunately, comparing code examples is likely to run into Sturgeon’s Revelation, or Sturgeon’s Law: 90% of everything is crap.… Read More »