Implementing VisiCalc
David Leppik writes "The author of VisiCalc, the first spreadsheet program, has
an article about how it was designed. VisiCalc is why businesses started to take the Apple ][ (and personal computers in general) seriously. It also changed accounting forecasts forever, which triggered the investment boom that brought us the "greed is good" era. Oh, and you can still
download VisiCalc in case you run DOS or Windows and have 27,520 bytes to spare."
It also changed accounting forecasts forever, which triggered the investment boom that brought us the "greed is good" era.
I highly doubt that this one application started an era of "greed is good." People have always been greedy, this just let them be greedying is a slighly more sucessful manner.
Many schools are dirt poor and happy to have what ever they can get. Some can barely afford PAPER, and the teachers end up buying some out of their own pocket so they can teach.
Our children are the future and our most valued possession.. yet we treat their education like a 'irritant ' and wont get involved or support it..
Plus don't forget, fundamentals don't change... and fundamentals are important, regardless of what some people/educators believe these days.
---- Booth was a patriot ----
Not that the CD Key system completely eliminates piracy, but it's just generally accepted that you have to buy the game now.
Not that I read .nfo files mind you...
Schnapple
How many of you have run into dumb decisions by management that looked good in the spreadsheet?
I was in NYC at the time, temping my way through college in a variety of office jobs. The first wave of spreadsheet-aware MBAs came out and thought everything could be charted on a spreadsheet.
What I noticed was that all kinds of wacky log forms started proliferating in the workplace. Workers were supposed to use these forms to log just about everything they did, even if it didn't make sense.
Me: "But I don't know what Percent Complete this project is!"
Them: "Just make your best estimate, we need the data"
The MBAs were also into TQM and various assorted management theories (remember the Japanese management fad?) They thought everything should be made quantitative. They had a new hammer (spreadsheet) so every problem was now turned into a nail.
It's hard to get by these days without knowing at least a little bit about how to use a PC.
Well, you're right about that, but it misses the point. The educational value of a computer does not, for the most part, lie in learning how to use the computer for its own sake. A computer is a general purpose information tool and one goal in owning a computer is education. Education can include reading, writing, math, science, social studies, etc. A computer can, to an extent, help with all of those subjects.
Note that an Apple ][ will help you just as much with your math as a PC, as long as the software on each is roughly equivalent.
I do get tired of hearing about school districts that just dropped $250,000 for a brand new computer lab, and then they turn around and lay off teachers then complain about the student:teacher ratio. It doesn't make sense to do that when you consider that they really don't even need the lab.
The above probably set you to thinking about how inadequate an Apple would be to learn computer science subjects. You would be right to an extent, but a lab really sees far more uses than just for computer science education. If the goal is to best serve the majority of the student body, then buying your computer equipment (and by extension the education software) around the needs of your computer science oriented students is a poor choice.
Please mod this post only if you think others should/n't read this. I have enough ego^H^H^Hkarma. Thanks!
Or if you're not, you're totally off base. Those were the days when programming was really fun, man! I remember being really excited when the PalmPilot came out, cuz it sounded like a good opportunity to get back to programming the way folks were meant to do it.
Who's with me??
Breakfast served all day!
And all young programmers should be made to sit an exam based on this.
:
:-) )
With concepts like
"VisiCalc was a product, not a program"
"The goal was to give the user a conceptual model which was unsurprising -- it was called the principle of least surprise. We were illusionists synthesizing an experience."
"One guiding principle was to always have functioning code. It was the scaffolding and all I needed to do was flesh it out. Or not. Since the program held together omitting a feature was a choice and it gave us flexibility"
and from the section on 'kidding'
"I doubt if any but the most geeky users were even aware that there was an issue let alone a solution. This is the kind of design detail that makes a program feel good even if you don't know why."
I've tried to tell several younger coders things like this on many occassions, and getting the message through can be hard work !
This article shows not only why these principles are important, but how to approach projects overall. Someone should carve it in stone (then hit newbie programmers over the head with it until it sinks in
-- You can't give it, you can't even buy it, and you just don't get it!
Promise a late delivery date, and verily, the manager shall not bug you whilst you are trying to work. Thus you deliver far sooner than if you give an accurate delivery date.
By following this strategy you will become known as a self-motivated, self-starter who consistently delivers ahead of schedule.
Additionally, your manager will never find himself with his nuts in the fire because of you, and will thus give you more 'manager support' when you need it. (read: performance review).
Good luck! I'm pulling for you. We're all in this together.
I want a new world. I think this one is broken.