|
I started programming when i found a book on a park!!
|
|
|
|
|
Apart from reading some books I regularly visit msdn blogs, www.codeproject.com[^], https://www.simple-talk.com/[^], www.c-sharpcorner.com[^].
It helps me to do a quick reference...
Previous -> Read "CLR via C#" by Jeffrey Ritcher.
Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder.
Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
|
|
|
|
|
I learned to program in assembly, the programs we wrote were for troubleshooting early IBM PCs. The two processors we wrote for were the Z80, the Intel 8080 and the 8086. I still have my Understanding Microprocessors text book from 1993 that covers the Intel processors.
I still use assembly today for Freescale (Motorola) HC08 microcontrollers.
It was broke, so I fixed it.
|
|
|
|
|
Basically this is it.
I like to try things, put them into practice, break the whole thing apart and start over again keeping in mind what failed before.
This have been helping me a lot on real-life decisions as I usually already know, or at least have a pretty good idea, of what is good where.
If something unknown comes to me, there I go again to my safe test bench 
|
|
|
|
|
Actually, still waiting for it to go to print... but I know it's gonna be good! 
|
|
|
|
|
... Andrew Hunt & David Thomas (Had to go get my copy to remember who by though!)
Code Complete is a close second
|
|
|
|
|
A lot of strictly technical books here. While I agree that they help making you a good coder, they not necessarily teach you the intricates of the trade. How to deal with difficult projects, how to manage unreasonable expectations and how to fight for your personal time are as important (if not even more important) to being a good PROGRAMMER. That's why I recommend "The Career Programmer: Guerilla Tactics for an Imperfect World".
|
|
|
|
|
- Sorting by frequency of occurrence isn't very useful. It appears a search for an exact title match is being done. As a result, the count for Niklaus Wirth's "Algorithms + Data Structures = Programs" is incorrect.
- The word "occurrence" is mispelled.
/ravi
|
|
|
|
|
Besides it is a 'Manual' for learning C, it IS (and not only WAS) a great book to learn how to program in a right way. It is easy to understand. (OK, the writing is easy, the concept not too much for beginners)  but if you start form the beginning and read each line, you will learn how to make good programs.
|
|
|
|
|
I'm entirely with you on that. This was my bible in my first job when I was working on a C cross compiler for Motorola 68000/68888 chips.
|
|
|
|
|
We have three things in common. One, the book we used to learn to code. Second, I also started on 68000 chips (Amiga 1000) and third, my second lastname (I live in a country where we use 2 lastnames, father and mother) is Clement.  Germán Valencia Clement. And yes, German in Spanish is the same than Hermann in English lol.
|
|
|
|
|
Great to know you German! It's cool that we share so much. My first computer, by the way, was an Amiga 1000 (unless you count a Sinclair ZX80). I wrote a freeware program that appeared on one of the first Amiga freeware disks (it was called "enpig" I think.) I searched for it, but it seems to have been erased from the memory of the internet. It took in a typed English sentence, parsed it (badly), converted it into Pig Latin (e.g. "That was fun" -> "atthey usway unfay") and spoke the result using the Amiga text to speech feature. 
Anyway, Mr. Clement.... nice to meet you
|
|
|
|
|
This is excellent! Nice to meet you too Mr. Clement  .
I worked for an engineering company at that time, and I wrote my first program using C for calculations and AmigaBasic for the interface (it was easy to work with it for windows and buttons). That ancient program was for calculating steel structures by matrix inversion methods.
We use that program in Amiga and not in PC compatible, because it was easy to access all the memory (4 MB RAM) and in the PC environment was a very difficult task. (At least in C or basic). That program never was sold and it is not possible to find it in Internet. And sadly, the source no longer exists.
Nice machine the Amiga, isn't it?
|
|
|
|
|
Very true. Some (actually nearly 30) years ago, I was given a new project at work and told that C should be the language of choice. I read this book over the weekend and started coding on the Monday, and was surprised at how much this book helped me.
Use the best guess
|
|
|
|
|
ISBN 978-0130224187, still available: http://www.amazon.co.uk/dp/0130224189
Formed the basis for structured programming, which begat OOPs.
If computers then had had as much processing power as my watch does now (and it is pretty dim) then I suspect he would have invented OOps back then (and saved us all a lot of misery).
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
|
|
|
|
|
I find such "what single book would you take to the lonely island"-questions kind of artificial. It assumes one guru writing the one-and-only book that changed your life
I could list many books that influenced my way of working.
My attitude is to also buy a book if it has the two pages worth it. With that attitude, you hardly can name the one single book.
Software construction is to a good part a craft - so I like "Code Craft" from Pete Goodlife, to name just an arbitrary one.
Cheers
Andi
|
|
|
|
|
|
Amen Brother! (hulk hogan voice). Also "The Pragmatic Programmer" by Hunt and Thomas is a must.
|
|
|
|
|
|
Agreed!!
"Benjamin is nobody's friend. If Benjamin were an ice cream flavor, he'd be pralines and dick." ~ Garth Algar
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." ~ Paul Neal "Red" Adair
|
|
|
|
|
The best book on software construction that I have ever read. A must read book for every software engineer.
|
|
|
|
|
I started programming in the mid 80s, on hobby machines like the Commodore 64 (BASIC, Lisp and 6510 assembly) and the TSR-80 (BASIC, Fortran, Pascal and 8086 assembly.) Books and magazines borrowed from the library, conversations with other hobbyists, and dial-up bulletin boards were my source of information. I took some courses in college (RPG, C, and God help me, even COBOL) but the biggest help in learning programming was to wade hip-deep into code and splash about.
|
|
|
|
|
I have not bought books so far. I have used the "learn VC++ in 21 days" some time ago in the first company I worked for.
Since then... I have mainly used internet sites like CodeProject, homeandlearn, w3school and similars.
I know many people will say nothing can replace a book and I (80%) agree with that, but since I am just learning in my spare time (which is not so stable) I prefer the "learn by doing" and search for concrete things when I get stuck.
I have somehow missed a good book, when facing some theory / concept problems. But as there are so fvcking good professionals here... at the end was not so tragic.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
while having some knowledge in BASIC, (Turbo) Pascal and Assembler, I started programming in C using Turbo C.
Using the Turbo C documentation (User's Guide and Reference Manual), and K&R The C Programming Language, I have learned more about programming than from any other source read later on.
|
|
|
|
|
Scott Meyers, Grady Booch, Jeffrey Richter, Martin Fowler, Joel Spolsky, Edward Yourdon, Niklaus Wirth
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
