Something bad about CI

[eluser]Daniel Moore[/eluser]
Ok, this is going to open up a rant, so if you don't want to hear it, skip this post.

You guys make me feel old. I remember learning C so I wouldn't have to code everything in assembler. I also remember when I started forgetting how to do assembler and suddenly realized it might be a mistake to not keep up with it. Then I came to my senses and realized, "Why should I keep doing assembler if I can get away with doing it all in C?"

I eventually moved on to use C++ Builder for rapid application development, and I never did miss the old way of doing things.

The key to successful programming isn't knowing how to do every minute command of the language, it's knowing how to put together blocks of code that you've developed over the years and seamlessly stitch them together to make an application as if they were designed to be that way (and if you design them right to start with, they are). When it comes to details of the language, make sure you always have a good reference book handy in case you forget how to format an "if" statement for yourself, or something crazy like that. Even the best of us have days where we momentarily forget the most basic things, and if you haven't yet, wait until you get to be my age.

If you can lay out a program in a flowchart or pseudocode, then a good programmer should be able to take that and write it in any programming language as long as they have access to that language's reference manual. Basically all languages are the same at some level, you just have to learn the syntax and grammar. A good coder will be a good coder in any language, using any platform.