|
I started with BASIC (on an ORIC-1), then some more BASIC (ZX-Spectrum, Commodore 64), then QBasic and QuickBASIC. Later on, I moved to ASM, then TURBO Pascal, and finally C++. I don't know if I have ever done any "pure" C programming.
Ask not whether it is useful. Ask what it is useful for.
|
|
|
|
|
I started with BASIC too, but i realy learned to program in HL language when i learned Pascal. So i think the entry level should be (OO) Pascal.
Afterwards you can continue in any direction.
ANSI C/C++ is a good start too.
If you are realy young and you have the time, i recomend assembler and some knowledge of computer architecture + binary operations.
The most important thing is who is your teacher or the author of the book you read. When i was forced to learn programming in Windows from a book called "QUE - Special Edition Using Visual C++ 6" i almost droped Windows forever. Luckily i've found The Forgers tutorial on win32 programming and later "Programming Windows" from Charles Petzold.
|
|
|
|
|
Herl the Pearl wrote: don't know if I have ever done any "pure" C programming.
same here never tried my hand in pure "C"
|
|
|
|
|
Yes. C is the best language to start with. The reason is its closeness to the assembly language and its openness to the high level language constructs.
Feel it yourself!
"Silence will create respect and dignity; justice and fair play will bring more friends;
benevolence and charity will enhance prestige and position; courtesy will draw benevolence;
service of mankind will secure leadership and good words will overcome powerful enemies"
Ali (Peace be upon him)
|
|
|
|
|
Well there is C and C. The first incarnation of C was good for doing things but not for theaching beginners, IMHO. Later the ANSI C standard adopted many features of Pascal, in the way the source should look like and ANSI C++ even more. So i gues ANSI C/C++ is good enough for teaching begginers.
Way better than languages that have garbage collectors and massive libraries for doing all kinds of stuff.
ps - I now see that the title is for developers, not programmers (or even coders), so maybe the best starting point realy is .net or whatever is "hot" on the market. Sorry, my fault.
|
|
|
|
|
Partially agree! I begin with C++ and after 1 year I learn VB. After that 4 years I used VB! It's very important what application you want to write. VB offers a short and convenient way to write good applications! Not always you need C++! It's an old and wrong discussion! You don't go with Ferrari to buy 1 kilo potato! For that you go with Ford or something like that! You must be practical!
I learn C++, VB, VBScript, JavaScript, ASP! I try to work almost three months with VB.Net and it's enough! It's not worth it! Better C++, JAVA, Python!
Now I want to learn a good language for future online application and with all recent changes I'm confuse!
http://www.kraftwin.blogspot.com
|
|
|
|
|
I definitelly do not agree to this. C is a very powerful langugage, but it's not easy to learn for a beginner. It allows (and sometimes even requires) the use of very bad programming patterns and styles. Beginners should be enforced to use good style, correct variable declarations and stuff like this. Therefore, even if one wants to become a C or C++ programmer (as most probably do), I'd suggest learning Pascal or C# first, because they enforce a beginner to the "good" style of programming from the beginning.
|
|
|
|
|
I dissagree with you as C FORCES you to define all your variable AT THE TOP of the current section of code.
it also teaches you to garbage collect, and if you use it properly (Don't abuse) then it works a lot better than C#, and even (sometimes) pascal. it also handles pointers, and reference based structures very well and doesn't have (what are to me) stange constructs to create a raw pointer. Just malloc() free().
However, I do say that Pascal would be an equal starting language to C.
The worst thing about the darkness is the light at the end - DX-MON
|
|
|
|
|
I cannot simply agree with your views. As you said, C is powerful. In my experience, in order to become a developer who never fall short of ideas, one has to go through the hardship of learning a language like C.
I equally agree with you on Pascal. But as for C#, of course it offers nice features. But the problem is it hides a lot of things under the hood. What do you prefer for a programmer to first start with C and then C# or to first start with C# and then C? First option is better because it will ease the things because a C programmer would have achieved a good understanding of memory management, IO, use of CPU registers etc.
"Silence will create respect and dignity; justice and fair play will bring more friends;
benevolence and charity will enhance prestige and position; courtesy will draw benevolence;
service of mankind will secure leadership and good words will overcome powerful enemies"
Ali (Peace be upon him)
|
|
|
|
|
You're right. I was maybe a bit short-handed on C# here. I agree that one has to learn the basics of memory managing, IO, etc the "hard way". What I don't like about C for beginners is that you're allowed to do a lot of odd things, like fiddling with the preprocessor more than necessary, doing manual address computations (where it's not really required), using a bunchload of global variables and stuff like that. That's why I think C# (or Java) may even be a bether choice than C in some ways. But preferably one learns Pascal first, which is as powerful as C but without some of its pitfalls.
|
|
|
|
|
|
In other words if someone has a natural curiosity and is willing to continually learn new things then they will be fine. I guess that goes for a developer's whole career, not just their first steps.
If someone is lazy and incurious then their programming will never get anywhere, regardless of the language they learn on. In my opinion it's from this pool of people that "evangelists" emerge.
Murray
|
|
|
|
|
Tend to agree here.. curiosity has kept me in the game when others were long gone.
modified on Monday, April 7, 2008 11:55 PM
|
|
|
|
|
The noobs must learn the right way to program -- without side effects.
|
|
|
|
|
  and whats with F# then he will get it half right
|
|
|
|
|
Where is any functional language?
|
|
|
|
|
In my opinion, the most important aspect of training NEW programmers is not at all making sure they understand the fundamentals. I am talking about the beginning stages, where I feel that getting the student to ACTUALLY CODE must be the first goal.
Once, the student sees results, that may motivate the person to take on more complex tasks and thus realize the need for further understanding of the underlying system. Therefore, it is my belief that any talented/motivated student will automatically seek information about the very basics.
In other words, FIRST make it very cool (motivation), THEN show them the REAL truth (understanding). I am no authority on the subject, but that is how I would train my students, regardless of what they are learning, cooking, drumming, programming, or something different.
With that in mind, I would choose the language that seems the easiest to pick up and use real quick.
Ask not whether it is useful. Ask what it is useful for.
|
|
|
|
|
A voice of sanity in what looks to be a lot of posts that are completely out of touch with the reality of a beginner learning to program.
"The pursuit of excellence is less profitable than the pursuit of bigness, but it can be more satisfying."
- David Ogilvy
|
|
|
|
|
The issue isn't 'what is the best implementation language', but 'how do we best train developers just starting out'.
I've been a software engineer for 24 years.. the biggest gap I've discovered in developers fresh out of school is in understanding the architectural underpinnings of modern languages, and how those languages 'meet with the metal'.. how they work on the hardware in question.
It points to a severe gap in basic understanding of the low level mechanism of the hardware. And note that this isn't just 'nice to know'. Understanding the systems we program at a low level also translates to better approaches in troubleshooting problems that occur, since the programmer isn't restricted to looking at the system 'just through the lens of the langauge he is using'.
To that end, learning the low level is the first step of understanding. In much the same way that an architect is made useful by his knowledge of basic construction techniques, programmers are made effective by their understanding of the hardware and how it plus the low level expression of the software translate into modern programs. No matter how much I see young folks trying to escape this, it remains as true today as when I started.
On the seemingly endless argument on 'ideal language'.. languages have use based on their application, not by nature of their existance. Its why researchers continue to experiment and look for better ways, and why there continue to be a plethora of languages. Ladder Logic on PLCs meets its industrial control needs very well, just as Java and C# meets the needs of its users. Its all about application.
|
|
|
|
|
I think this is due to the fact that most languages live in a "level".. As in "high-level" and "low-level". This because over time, we've "stacked" languages on top of each other..
Consider this layering of languages, from lowest to highest level..
- Processor Machine Code
- Assembly Language
- C
- C++
- Java Byte Code/.Net CIL/Lots of other language runtimes and compilers
- Java/C#/Misc Scripting languages/etc..
- Domain Specific Languages
Each higher level language is implemented in the lower level language, and cuts off it's scope of functionality at it's "layer" (with minor exceptions).
The problem that this creates is that each layer is semantically *very* different from the previous layers. That means that to learn the functioning of a different layer, you need to learn a whole new language, and a whole new functionality paradigm. This is intimidating and very hard to learn. A lot of people never bother to learn it.
What if a single language could be used from top to bottom? What if I could write in C#, and access my x86 opcodes directly, as if I was writing assembly, or re-write the syntax so that I could create my own domain specific language?
I recall, back in the early '90s when I was programming in C, using the Borland Turbo C compiler, who cool it was to be able to in-line assembly code in my C# code. This was a step in the right direction. I didn't need to switch contexts to access a lower level of functionality.. Just put my assembly code in a scoped block (see this article for more info[^]). This can still be done with Visual Studio in C/C++, but not in C#.
C# can also not re-write it's own syntax... F# however, can.
Anyhow, this is only a step in the right direction. What would be even better is if I didn't have to write in a completely different language (even if it is inlined in context), but if I could just do those things within the language directly. C# has some element of this with "unsafe" clocks, in which it can access memory directly in a C/C++ like manner...
But where is the language that lets me use a single language from the most primitive hardware specific low-level calls to the most abstract high-level syntax-customized DSL?
If such a language existed, and was in common use, then the barriers to learning the lower level concepts would be dramatically reduced. Instead of having to learn a whole new language (as well as a whole new set of tools, and switching between environments), a programmer could simply explore within that language the different levels of computer functionality... uncovering new ways to do things, when needed, without impedance.
I think F# is really nice for this, but only in an "upward" manner. It sort of cuts off at the "CIL" layer in the "downward" direction.
"Be liberal in what you accept, and conservative in what you send." - Jon Postel, First Law of Internet Communications
"It's 5:50 a.m., Do you know where your stack pointer is?"
"If at first you don't succeed, you must be a programmer."
http://vanguard-against-confusion.blogspot.com
|
|
|
|
|
Given the outsourcing frenzy, I submitted 'English'.
What does an agnostic, dyslexic, insomniac do?
He lies awake at night wondering if there's a dog.
|
|
|
|
|
In a way I agree with you.
People should be taught boolean logic first. That way they can understand, in very basic terms, what the building blocks of computing machines are about. This is a very interesting topic that most people should enjoy, even if they are not into programming or mathemetics.
|
|
|
|
|
Yes,
There seems to be an implicit emphasis on getting someone coding profitably ASAP. However, if your premise is that the learner is hoping for a career of many years, then these basics are going to make their (and their colleagues') life so much easier and more successful IMO.
Personally I started with Pascal (Programming 101), but in the mid-year break I worked through Peter Norton's Assembly Language Guide to the IBM PC. I have to say that "the penny dropped" in so many ways when the underpinnings of programming languages were revealed. It have no doubt whatsoever that it was the reason behind the perfect marks for all assignments in Programming 102 (exams? I don't talk about them).
I have so far resisted the urge to do what I think most developers do when asked this question and simply recommend what *I* did. However, I truly believe that assembly language should be learnt very soon after learning the first one. I lean towards Pascal for the first language rather than C because of some of the innocent looking time bombs that can slip by in C.
Murray
|
|
|
|
|
Yup, you got my point exactly. What makes us effective is our view of the system, not any one of its pieces. This only comes from an understanding of the underlying machine and how to leverage that machine to 'get it all done'. The more complex things get, the MORE important it is to understand, since so many more things can go wrong in the system.
The aim of training developers is for the long haul, not the moment.
modified on Monday, April 7, 2008 11:54 PM
|
|
|
|
|
I understand the point you are trying to make. I followed probably what you would call the wrong path. Started in BASIC, went to VB6, then learned Assembler, C, Java, and now on to .NET. I will fully admit that after I learned assembler my outlook and view on coding techniques were dramatically changed. However, I feel trying nowadays to get someone from assembler to C to C++ or C# and then finally onto a framework is akin to telling your 16 year old to rebuild his car bolt for bolt before he can take it once around the block.
I fully understand and see everyday the problems of programmers with no mental connection between their code and the machine it is running on, but I don't think forcing a PhD amount of work before they can start doing anything is the right answer either. However, I do well believe all CIS college programs should have an assembler course in their somewhere, which is sadly lacking. I just think there has to be a better way.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
