That's certainly true in many states. We used to take advantage of that law by buying expensive things at a discount from stores in Kentucky right before the end of the year; if they had those products on their books on January 1, they had to pay tax on them, so they had an added incentive to sell them. Thus, they were willing to take a little bit less money for them, because they knew they'd get that much less if they sold them a week later anyway.

In declarative languages instructions are not executed in order (indeed, modern compilers frequently reorder instructions and, as we progressively move away from Von Neumann architectures, very few computing environments will guarantee instructions are executed in order). In functional languages variables cannot change. If those are the ideas you've internalised about software, you aren't going to go very far.

BASIC is just the ultimate bad language. Like King John, it has no redeeming features.

That's what they told me when I was at school. I'll be sixty this year. I don't see programming becoming obsolete any time soon.

BASIC is a really, really bad language to teach anything about computing. If you want to equip them for the world of work, go for Java or C# (which are more or less the same, from a learner's point of view, and neither is hard). If you want to teach a deep understanding of algorithms and how computers work, Clojure or Scheme would be good choices.

What horrible department were you in? That doesn't sound like any department I encountered. Well, I'm not sure about the IT folks.

I thought Apple had already done this. Their cafeteria workers have been employees since the late 90s, give or take, and the folks who sit at the front desk are also employees. I had always assumed the security guards were as well, but apparently not.

I currently work for a small (50 employees) engineering company. One person in my present team's weekly standup is in Montreal, Canada. Three are in New York, USA. Three are in London, England. The rest are in Glasgow, Scotland. In my last job, with a major international bank, one standup member was in Chennai, India; three in Geneva, Switzerland. One in London, England. And the rest in Glasgow. In the real world 'everyone in one room' just isn't going to happen.

I imagine, using standard journalists' practice, the Guardian phoned up the NSA and said 'we've found this in your documents. Would you like to comment?' That's what professional journalists do.

About 5600 lines. However, because it was a glorified case statement, you were really only debugging a single case at a time, each of which was about the length of a sane function, so splitting it into functions would do little to improve readability. I like to trot out that example to terrify people, but the function itself was really quite sane and easy to maintain.

You did, however, have to fully understand the state machine as a whole, which in total was almost twenty kloc, had almost 200 instance variables in the state object, and leaned heavily on a tree object with about 30 instance variables. That's the point at which most people's heads exploded.

Either way, 4,500 lines is the size of a fairly straightforward iOS app. Most folks can dig into that and figure out enough to maintain it without spending a huge amount of time, even if the organization isn't ideal. When you hit tens of thousands of lines, that's where you have to start thinking about how you organize it and document it, because with such large projects, if you jump into the middle without a complete picture, you're likely to be hopelessly lost.

Seriously. I've written single functions longer than that. If your code is so confusing that you can't maintain it without refactoring it by the time the entire app hits 4500 lines, either your code is some of the worst in the universe or you have insufficient working memory. Just saying.

If you're trying to determine what the file type of a file is from an extension on the end of its name, you're engaging in industrial archaelology, not computer use. You can rename any file to have any 'extension'; consequently this idea is completely broken. The idea that you deal with this misfeature by hiding it just compounds the error.

You're confusing cause with effect. Programmer wages aren't high in the Silicon Valley because of having a lot of programmers. There are a lot of programmers because the wages are so high that CS majors come here in droves after college.

The reason the wages are so high here is because of basic supply and demand at work. Silicon Valley has only about a 3.6% unemployment rate among programmers, and a lot of the unemployed either want to be unemployed or are unemployed because their specific skills aren't in high demand. Programmers may be common in the Silicon Valley, but the demand in the Silicon Valley far exceeds the number of qualified programmers who are available and looking for jobs. Thus, the entire market is a zero-sum game, and the high wages are a result of the need to buy people away from other companies.

As a result, any sudden increase in the number of programmers drives down salaries for new hires, and fairly dramatically at that. For proof, you need only look at what happened to programmer salaries outside the Bay Area during the dot-com crash, when droves of people suddenly were looking for more affordable places to live. In some areas, salaries for programmers dropped almost in half because of that exodus.

Is it realistic to believe that there will ever be enough programmers to satisfy the Silicon Valley's voracious appetite? Hard to say. But that's a separate question.

Yes, it is pretty silly for them to expect the government to educate people. It is not like an educated population is some kind of public good.

Well, it is a benefit to the public as a whole to a large degree, but there is a dark side, too. The main reason that companies want to increase enrollment in CS is to get a larger pool of people to draw from so that they won't have to pay employees as much.

The Web is in the mess it now is because Microsoft (and, to a lesser extent, Netscape, back in the day) has gone through so many iterations of deliberately trying to create subtly incompatible variants of HTML. Creating a browser which is backwards compatible with that mess simply perpetuates the mess. The new browser should simply refuse to render non-conforming legacy pages at all - that would force web site owners to clean up their act in short order.

I'd also tell her about your illness, and tell her what you tried, just in case it is congenital. The more detail, the better. It might save her life someday.

Also, if you haven't already, you should check to see if you qualify for any of the immunotherapy trials going on. Search here if you haven't already.