I want to be a better programmer [modified]
-
So here's the jist of it all.... I have dabbled in computers and programming for over 2 decades now. I have never been formally trained (no degree, schooling, etc). I learned everything I know from books. I have taken several hiatuses from the computing world for years at a time due to working in fields that were not associative with the subject, so I lost a lot of knowledge and technology jumped ahead of me. I started programming in BASIC. I took a 4 year hiatus, then got involved again when I started working offshore (lots of time to read). I started learning C++. I learned all about OOP and had a good knack for it. While I was working on an offshore drilling rig, I wrote a program for the engineers that cut their computation time from 3 or so hours to less than 10 minutes (they hand calculated every spec), though I couldn't get their parent company to buy. After that job I took about a 7 year hiatus. I started working in retail at the bottom of the totem pole for a small business. As I progressed at the job, it was noticed I could fix problems with the computer. Got so well known for it that when our only tech support person went away on business and vacation, all calls went to me. That progressed into me becoming the tech support guy for the company. I had to learn an archaic basic programming language (without any manuals are reference materials) called TAS (anybody played with this crap yet?). So I was stuck playing in 80's tech for a while. In addition to re-writing the code in this archaic language to customize for the company, I also had the honor of being the main tech support person for anything technical...ie - if it has a power cord I should know how to fix it. Since the beginning, we have grown from 3 locations with about 25 employees to 26 locations with over 200 employees. So while trying to learn new things, I was confronted to answering every asinine question about anything technical. As time went on, I decided to start learning a new language called C#. I have read, and read, and read so many books and articles online that I should be blind. I know I have lost a lot of what I learned when I was in my 20's about OOP. It's obvious by my coding. Yet all the knowledge I grab from all I have read has not taught me what I really need to become a better programmer. Either the books are about basics of the language or does not explain in detail the inner workings of good, solid, efficient programming. IOW, there are too many bad books out there! So I ask you, fellow programmers, wh
-
So here's the jist of it all.... I have dabbled in computers and programming for over 2 decades now. I have never been formally trained (no degree, schooling, etc). I learned everything I know from books. I have taken several hiatuses from the computing world for years at a time due to working in fields that were not associative with the subject, so I lost a lot of knowledge and technology jumped ahead of me. I started programming in BASIC. I took a 4 year hiatus, then got involved again when I started working offshore (lots of time to read). I started learning C++. I learned all about OOP and had a good knack for it. While I was working on an offshore drilling rig, I wrote a program for the engineers that cut their computation time from 3 or so hours to less than 10 minutes (they hand calculated every spec), though I couldn't get their parent company to buy. After that job I took about a 7 year hiatus. I started working in retail at the bottom of the totem pole for a small business. As I progressed at the job, it was noticed I could fix problems with the computer. Got so well known for it that when our only tech support person went away on business and vacation, all calls went to me. That progressed into me becoming the tech support guy for the company. I had to learn an archaic basic programming language (without any manuals are reference materials) called TAS (anybody played with this crap yet?). So I was stuck playing in 80's tech for a while. In addition to re-writing the code in this archaic language to customize for the company, I also had the honor of being the main tech support person for anything technical...ie - if it has a power cord I should know how to fix it. Since the beginning, we have grown from 3 locations with about 25 employees to 26 locations with over 200 employees. So while trying to learn new things, I was confronted to answering every asinine question about anything technical. As time went on, I decided to start learning a new language called C#. I have read, and read, and read so many books and articles online that I should be blind. I know I have lost a lot of what I learned when I was in my 20's about OOP. It's obvious by my coding. Yet all the knowledge I grab from all I have read has not taught me what I really need to become a better programmer. Either the books are about basics of the language or does not explain in detail the inner workings of good, solid, efficient programming. IOW, there are too many bad books out there! So I ask you, fellow programmers, wh
wrote:
the teachers are not about teaching, they do it for the $$$
Not necessarily true.
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
-
So here's the jist of it all.... I have dabbled in computers and programming for over 2 decades now. I have never been formally trained (no degree, schooling, etc). I learned everything I know from books. I have taken several hiatuses from the computing world for years at a time due to working in fields that were not associative with the subject, so I lost a lot of knowledge and technology jumped ahead of me. I started programming in BASIC. I took a 4 year hiatus, then got involved again when I started working offshore (lots of time to read). I started learning C++. I learned all about OOP and had a good knack for it. While I was working on an offshore drilling rig, I wrote a program for the engineers that cut their computation time from 3 or so hours to less than 10 minutes (they hand calculated every spec), though I couldn't get their parent company to buy. After that job I took about a 7 year hiatus. I started working in retail at the bottom of the totem pole for a small business. As I progressed at the job, it was noticed I could fix problems with the computer. Got so well known for it that when our only tech support person went away on business and vacation, all calls went to me. That progressed into me becoming the tech support guy for the company. I had to learn an archaic basic programming language (without any manuals are reference materials) called TAS (anybody played with this crap yet?). So I was stuck playing in 80's tech for a while. In addition to re-writing the code in this archaic language to customize for the company, I also had the honor of being the main tech support person for anything technical...ie - if it has a power cord I should know how to fix it. Since the beginning, we have grown from 3 locations with about 25 employees to 26 locations with over 200 employees. So while trying to learn new things, I was confronted to answering every asinine question about anything technical. As time went on, I decided to start learning a new language called C#. I have read, and read, and read so many books and articles online that I should be blind. I know I have lost a lot of what I learned when I was in my 20's about OOP. It's obvious by my coding. Yet all the knowledge I grab from all I have read has not taught me what I really need to become a better programmer. Either the books are about basics of the language or does not explain in detail the inner workings of good, solid, efficient programming. IOW, there are too many bad books out there! So I ask you, fellow programmers, wh
First of all Hats off to your zeal and spirit to learn it all on your own! :) Now that you already know about many languages, I think you should start concentrating on designing and software engineering aspects. There are many good books available on design patterns and on how to write good code (e.g. Writing Solid Code - MS Press, Design Patterns - Gang of 4, Design Patterns Explained - Alan Shalloway, James R. Trott - Addison Wesley, Bruce Eckel books on C++, Java and design patterns (freely downloadable from here[^]) or this excellent site[^] etc. Along with this, I hope you will find this article[^] useful.
It's better to know some of the questions than all of the answers.
Pravin.modified on Friday, March 14, 2008 7:59 AM
-
First of all Hats off to your zeal and spirit to learn it all on your own! :) Now that you already know about many languages, I think you should start concentrating on designing and software engineering aspects. There are many good books available on design patterns and on how to write good code (e.g. Writing Solid Code - MS Press, Design Patterns - Gang of 4, Design Patterns Explained - Alan Shalloway, James R. Trott - Addison Wesley, Bruce Eckel books on C++, Java and design patterns (freely downloadable from here[^]) or this excellent site[^] etc. Along with this, I hope you will find this article[^] useful.
It's better to know some of the questions than all of the answers.
Pravin.modified on Friday, March 14, 2008 7:59 AM
Thank you!
Jude