|
Hee hee. At college we used punched cards, because the lecturer was a b'tard, for machine code projects. By the time I started working the world had moved on to mag tapes and 'washing machine' removable disk platters.
Thems was the days. :nostalgicSigh:
|
|
|
|
|
I had a class that taught us DEC PDP-11 assembly language as preparation for the follow-on course in real-time programming.
We did the projects for the PDP-11 assembly language course on punched cards, running a PDP-11 simulator on the university's IBM mainframe.
This was not a fun experience, since the simulator was a graduate student's thesis project, and not especially, er, complete.
Software Zen: delete this;
|
|
|
|
|
I seem to recall that there was a backspace key - it punched all holes in the column which was read as ASCII 127 or whatever the EBCDIC equivalent was.
What you didn't have was the cursor control keys.
Generally it was as easy to copy the card up to the error and continue from there.
I'd agree about using the IDE being much beter though although the ext editor approach does have a few benifits primarily it encourages you to get the syntax correct in the first place. The even greater benifit of punched cards or more accurately the day's wait for the printout in the bucket run was to ensure that you understood the code you were writing.
|
|
|
|
|
Much as I would like the newbies to feel pain, IDE it helps in leaning syntax...
|
|
|
|
|
My first computer[^] didn't differentiate between entering a basic program one (numbered) line at a time and the command prompt used for everything else.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
OriginalGriff wrote: It helps you at every turn: it prompts you with method names and properties, it helps remind you of function parameters, and it tells you when you misspell something as you go along. It handles indentation, and it works exactly the same when debugging as it does when you are editing.
When they're in a cooperative mood otherwise it's; crash, design editor problems, gets hung in a, what I like to call PMS mode, etc. otherwise it's great. 
|
|
|
|
|
Same here press ! To execute shell script , vi ? Vi ? Vi ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
If was always fun to realize you had typed your C code into vi and it was executing it as a command string...No! Stop! Noooooooo......
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Yes reminds me of "you have backed up everything haven't you ?" STOP STOP OH NOOOOOOO....
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
IDEm 
|
|
|
|
|
I started with something "less" than a text editor. Basic on Commodore 64, and believe me, it was a pain in the .... neck  After that I went to AmigaBasic a real text editor, I traveled through many different programming languages and editors until I landed on Visual Basic V. 1.0. It was like arrive to haven (Programmer's haven, of course). Water ran under bridges and now I am using Visual Studio (C#), and there is no way to return to my text editor's time. It is like get down from a limo to travel on a wheelbarrow. Of course this is my personal opinion, no offense 
|
|
|
|
|
An IDE is like a free teacher (or paid depending on the one you use) that tells you where you are wrong.
|
|
|
|
|
IDE hands down - especially when you are just starting. I mean you should, just for the experience, code apps up in using a notepad type text editor and command line compiler, be sure to use mutiliple files and include and if your chosen environment allows it build scripts.
Doing this as the main way of working just strikes me as bizarre and contrarian. I worked in one place where vi was the only editor hard-core enough, funnily enough I used emacs (the only viable alternative for our environnment) as was far more productive.
|
|
|
|
|
I actually got pretty fast using vi for coding but it was vanilla c in those days ( shudder ) I also used WordStar for coding COBOL ( double shudder ) when intellisense first came out I didn't like it as it got in the way but would find it very difficult to live without now given the sheer size of frameworks these days. IDE 1 : Text Editor 0
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Sure I use an IDE everyday. But when I learned, the ability to look things up, read the instructions, search the web, and think out my problem without typing were invaluable. I suppose the difference is will you be a technician or a master?
Ignoring the pro's and con's of an IDE it is fundamentally a tool for facilitating writing code not for learning to write the code. If you learn to program you will never know why the below code is wrong:
Int32.Parse(Session["someInteger"].ToString());
|
|
|
|
|
...when clearly it should be Int64.Parse...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
Hmmm, let's see:
Session could be null if session state is disabled for the application or the request;Session["someInteger"] could be null if the session's timed out (or you've misspelled the key);- If you stored an
Int32 in Session["someInteger"], drop the .ToString / .Parse and just unbox the value; - If you didn't store an
Int32 in Session["someInteger"] (why the elephant not?!) then Int32.Parse could throw a FormatException or an OverflowException; - Even if you did store an
Int32 in Session["someInteger"], the current culture settings might* prevent Int32.Parse from correctly parsing the result of the .ToString() call; - If you're not already doing it, this should be hidden behind a façade class;
Did I miss any?
* I don't know for certain whether there are any culture settings that could do this, but since I don't know for certain that there aren't, it's safest to assume there are.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Not only is it wrong (i.e. unsafe), it's not required since the value of the successfully parsed integer isn't used anywhere. 
/ravi
|
|
|
|
|
IMHO - to learn programming you need no computer at all. When I learned we got books to read, teachers to hear and questions/answers were delivered on paper...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
I'd vote for IDE as well... but while learning, also learn what it is the IDE is doing for you so that you're not stuck on things simply because the IDE has a bug or you don't know what it is the IDE does in the background.
|
|
|
|
|
IDE without a doubt. But keep that text editor handy to go and have a snoop around in any generated files (e.g. config files) ... compare what you're seeing in the IDE with what you're seeing in the text file - best of both worlds
|
|
|
|
|
|
"Depends"
#include <shamelessgeneralizations.h>
Depends how you learn.
An IDE can help you along by getting you up and running faster. So if you're going to get discouraged by not having results quick, then I'd say use an IDE that will help you along and get you to a project that will run quickly. Then tinker with it from there.
The problem a lot of IDEs have is that they frequently put boilerplate code in for you. Sometimes that's good, sometimes it's bad as it may give you a false sense of what's really required and what is really going on.
A text editor on the other hand demands you really "start from scratch." You have to navigate configuration of the tool chain (compilers, linkers, library paths, build options, etc.) BUT you get the satisfaction of knowing that if you didn't write it, it ain't in there.
Personally I'd much rather WORK with a text editor (I've no doubt my .emacs file is older than most people here.) But for learning a new language or platform, I like starting in an IDE with samples, then tinkering my way to enough knowledge to dispense with them entirely.
|
|
|
|
|
IDE. Except that then you have to learn two things. 
I learned with a text editor and I still prefer that for writing actual code -- but not when a drag-and-drop designer is required. And IDEs tend to have a debugger as well.
Back in college everyone (even me) preferred to use Turbo Pascal's IDE (on a 386 PC clone) rather than use VAX Pascal with a VT100.
However you shouldn't get to point where you don't think you could possibly write a simple console app in a text editor and compile it on the command line.
Learn it with an IDE by all means, but come play on the fun side once in a while. 
This space intentionally left blank.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
