Jump to content

  • Log In with Google      Sign In   
  • Create Account


What was your path?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
8 replies to this topic

#1 JonBMN   Members   -  Reputation: 701

Like
0Likes
Like

Posted 17 August 2012 - 01:24 PM

What was your journey to becoming proficient in the languages you know? I know myself I love hearing how people got to be who they are today and the steps they took. Feel free to share here, if not that's fine! I know beginners love to here others' success stories.

Sponsor:

#2 Telastyn   Crossbones+   -  Reputation: 3722

Like
3Likes
Like

Posted 17 August 2012 - 02:05 PM

What was your journey to becoming proficient in the languages you know?

  • My dad has been a programmer for 40 years (same system too!)
  • We got an Amiga when I was 8, and I poked around at AmigaBasic, but not seriously.
  • I picked up Pascal in a high school course, quickly out pacing the class and working on little graphical things and dumb text games when I wasn't busy playing DOOM on the network.
  • Started to learn C++, failed.
  • Tried again a year later, failed.
  • Used matlab in one of my college courses to play around with a breadboard.
  • Tried learning C++ again, failed.
  • Dropped out of college.
  • Tried a year later and got some stuff working.
  • Started in with PHP for web scripting needs and then on-machine scripting.
  • Got some socket programming working in C++.
  • Learned some perl for text manipulation because more machines were unix based.
  • Got a book for Regexes since perl's kinda useless without.
  • Made my own (horrible) heterogeneous linked list implementation in C/C++, and thought it was the best thing since sliced bread.
  • Did some numerical factoring stuff in C++, learning that I was really bad at making programs of any size.
  • Took a C++ course in college, realized I knew more than the professor.
  • Did a little perl automation for my QA job.
  • Got enough C++ skill to do basic directX work.
  • Realized that I'd spent 8 years learning C++ and I couldn't actually make a vaguely respectable app.
  • Picked up a book on C# and reproduced the entirety of my C++ code in 3 months.
  • Spent 18 months unemployed trying to get a programming job with no experience or degree.
  • Got a job that required heavy SQL use, so learned SQL.
  • Job also required writing/maintaining C/C++ apps, so did that.
  • Quickly realized that even though I was a horrible programmer, I was still better than all but the most senior guy on the team.
  • Job required Java to create a credit card processing portal, so I muddled through Java/Servlets. (and I pity anyone who entrusts their credit card data online)
  • Transfered to a webdev C# division and put my 2 years of rapidly improving hobby C# skills to work.
  • Didn't know CSS or JavaScript/jQuery so learned them.
  • Didn't know much about database design, so learned as I went.
  • Spent a few weeks writing Haskell on the side to pick up concepts.
  • Switched from doing 4x games in my spare time to programming language development (see sig).
  • Realized that I was making 60% market rate, so looked for other work; promptly doubled my salary.
  • Quickly became a team lead, so needed to learn much of the politicking/people management side of things.
  • Designed and led the team that implemented the software that drives some of the fancy TV menus you see in restaraunts these days. Involved a bit more JavaScript, and a ton of C# and concurrency experience.
  • Spent ~2 weeks learning F# and implementing a bunch of CodeChef sort of problems with it.
  • And now I'm at another position, aiding in developing an archtecture, training the staff, and concocting elegant solutions to difficult problems (largely in C#).
  • This fall I'm taking some courses to finish my degree, which will require getting back into Java development.
And there you are, some 20 years of steps; mostly involving failure.

Edited by Telastyn, 17 August 2012 - 04:23 PM.


#3 fallenphoenix   Members   -  Reputation: 212

Like
1Likes
Like

Posted 17 August 2012 - 03:37 PM

When I was quite young, my dad tried to get me interested in programming using basic on a TRS-80 4P (still sitting in a closet back home). I was too interested in playing in the dirt and taking apart the hardware for a few years, so I didn't focus and learn anything really significant until I was a teenager. In middle and high school, I did my share of HTML and PHP to get web sites and rudimentary forums up, but again distractions (this time it was cars and girls) made programming less than a priority.

When WoW came out, I got into Lua, but didn't branch out of that application. It wasn't until I had my BA in English and working on an MEd that I finally sat down and dedicated time to learning how to seriously program. My parents, who had suggested computer science as a path of study when I was a teenager, gave Stephen Prada's C++ Primer Plus to me for Christmas. After that, I was hooked on not just learning how to program, but how computers work on every level.

After my first semester of teaching high school, I realized that creating software was a passion and not just a hobby. I'm now solidly into a computer science masters program, and learning far more than I ever thought I was capable of. It's a downright cathartic experience. That English degree wasn't totally wasted, ;)

#4 SillyCow   Members   -  Reputation: 845

Like
1Likes
Like

Posted 17 August 2012 - 03:40 PM

  • 5th grade Art teacher taught us how to write a simple BASIC program.
  • Asked a basic question, teacher didn't know the answer. ( She was an art teacher... )
  • Bought a book about basic from local bookstore.
  • Oh my god! programming is cool
  • Made many cool basic programs.
  • Made many small games in basic.
  • Wanted to do more serious stuff --> got a book about C.
  • Made some games in C
  • Wanted to do cooler stuff --> Got a book about Assembler
  • Made a graphics engine using assembler
  • SOMEONE INVENTED THE INTERNET
  • OH MY GOD! DON'T NEED BOOKS ANYMORE. CAN LEARN ANY LANGUAGE WITHIN A WEEK.
  • Found porn on the internet ( No time to program :-) )
  • Went to college ( No new languages/Technologies here )
  • Got a Job
  • Whenever I need to learn a new language, They send me to a crash course. Much easier than reading tutorials. Also much more expensive (But I'm not paying) .
My main tip is:
a. Learn through doing (reading is not enough). Think of a small fun project, and make it as you learn.

Edited by SillyCow, 17 August 2012 - 03:43 PM.

My new android game : Enemies of the Crown

My previous android game : Killer Bees


#5 VReality   Members   -  Reputation: 434

Like
1Likes
Like

Posted 17 August 2012 - 04:55 PM

  • In fourth grade they had a Texas Instruments computer in the classroom. If I finished my classwork early, I could mess around with it. Taught myself Basic.
  • In Junior High they had a computer class, but after a week I realized they weren't going to cover anything that anyone who had been within 100 yards of a computer before didn't already know. I transferred to wood-shop.
  • In High school they offered essentially that exact same computer class. But they also offered Advanced Placement Pascal. And a top grade on the advanced placement test would test me out of the entire first year of Computer Science classes in college. That's money in the bank.
  • In college they didn't really teach languages. They'd say, "Your project this quarter is in Ada. There's a book on it in the book store." When I graduated, I had about ten languages on my résumé - not to claim I was proficient, but to start the conversation in which I pointed out that I had been taught to learn any language.
  • There was one rogue professor who taught C++ under the guise of an object oriented design class. So I learned C++ much more thoroughly than any other language.
  • In college, I got a job making networked medical systems, using C++. And I used it in aerospace for a year and a half during and after college.
  • At my first job in the video games industry, they were on the first generation of games developed in C++. We discovered all the classic pitfalls, such as the all consuming monolithic base class. But I also arrived at the abstract factory pattern independently, while designing a physics system.
  • Between that and my next job, I developed a functor class which was a precursor the the C++11 std::function and std::bind.
  • But there were aspects of the language which for various reasons weren't used by any of the studios I was at. There are those who would say that I was never truly proficient with the language until very recently, when I took some time to study those aspects of the language and the new C++11 features as well.


#6 Bacterius   Crossbones+   -  Reputation: 8177

Like
1Likes
Like

Posted 18 August 2012 - 12:26 AM

What was your journey to becoming proficient in the languages you know? I know myself I love hearing how people got to be who they are today and the steps they took. Feel free to share here, if not that's fine! I know beginners love to here others' success stories.

Since most of the previous posters give insight into how they got into programming back in the time when computers and the internet weren't exactly commonplace, here's my story from the point of view of someone that started out in the 21st century with most of the stuff available at a few clicks' reach.
  • Started at 10 when my dad introduced me to Object Pascal (with the Delphi IDE), whipped up a few crappy apps/games with the RAD interface
  • Two months later, I discovered pointers and indirection mechanisms and my world changed that day
  • For the next six years, honed my skills to become quite proficient in that language and with hardware, but with intermittent 6-month "coding breaks"
  • Got interested in math only when I was around 15, figured I could use my knowledge of programming to make homework less tedious
  • Picked up Python when I was 16 and played around with it. Never really got proficient but I love writing short algorithms with it
  • At 17 I went to my first "programming class" which was available at my high school
  • Subsequently had to learn Java, did not like it much but survived
  • Had to learn C# the second year, liked it a lot as a productivity tool and got proficient (with the syntax at least, lol, but checked out a few libraries)
  • At 18, built my first actual desktop computer with - omg - an actual graphics card
  • Immediately learnt XNA, but found it too convoluted and used SlimDX/C# instead
  • Six months later, got bored to tears with computer graphics, learnt OpenCL and crunched numbers big time
  • Learned some x86 and x64 assembler shortly after (just general knowledge for when I need to inline stuff)
  • Begun university, have to use Java for computer science courses, which is slowly turning me into a code monkey
  • Turned 19 and three more years to go before I get those degrees <- I am here
  • Looking forward to learn some functional languages, such as F# or Haskell and some database stuff (which I've ignored completely for some reason)

Not exactly a "success story" but I feel I'm not doing too bad in terms of picking up new languages and frameworks (it certainly could be better, but I got... hmm... sidetracked with other things).

My advice is to just "do it" and don't worry about what you learn, it's not like your brain has a limited capacity, and any experience you obtain in one area can often be reused elsewhere, as the whole programming/computer science field is very modular. I can safely say my extensive knowledge of Pascal and all the underlying algorithms/syntax/constructs made performing all of the subsequent bullet points about a thousand times easier (plus, it makes my discrete mathematics and logic course an absolute breeze). Whatever you learn cannot hurt you.

For what it's worth, I have very little knowledge of C++. OK, whip me now!

The slowsort algorithm is a perfect illustration of the multiply and surrender paradigm, which is perhaps the single most important paradigm in the development of reluctant algorithms. The basic multiply and surrender strategy consists in replacing the problem at hand by two or more subproblems, each slightly simpler than the original, and continue multiplying subproblems and subsubproblems recursively in this fashion as long as possible. At some point the subproblems will all become so simple that their solution can no longer be postponed, and we will have to surrender. Experience shows that, in most cases, by the time this point is reached the total work will be substantially higher than what could have been wasted by a more direct approach.

 

- Pessimal Algorithms and Simplexity Analysis


#7 darookie   Members   -  Reputation: 1437

Like
1Likes
Like

Posted 19 August 2012 - 05:15 AM

  • Being faced with a random problem (say: writing a simple text adventure)
  • Looking at the options I have available (I started with BASIC on a Commodore 16)
  • Learned how to use the tools to achieve my goal
  • Tried to improve my skills by learning some theory (I started looking at algorithms like bubble sort, insert sort and data structures, etc.)
  • Bought a lot of shareware- and technical disk magazines (this was way before the internet) and looked at other people's code - now it's the internet.
  • Learned new languages (namely C and later Pascal), because they were used by many people in these disk mags
  • Added the new languages to my "toolbox" and tried to figure out what they were especially good at
  • Went back to Step 1 and repeated this cycle ever since.
My current skills include a wide range of languages with varying degrees of current working knowledge (from domain specific ones such as SQL, XPath, XSLT, IDL and regular expressions to general purpose languages such as C++, ARM assembly, C#, Java, F#, Ruby, Pascal/Delphi, Javascript, ...). Lately (for the past 8 or so years, that is) I added a Step 7a to the cycle - acquiring more in-depth knowledge on some language features like implementation details, to better understand how the language works and why.

#8 TMKCodes   Members   -  Reputation: 271

Like
1Likes
Like

Posted 19 August 2012 - 05:43 AM

I got my first computer when I was five. I broke it and the next day I fixed it. I was sold on how magical the thing was. Later in the same year I got dial-up connection and laptop running win 95. I still have it. With dialup I went surfing the first websites I could find and noticed the view source button, which was my first finding of what software actually is. The funny thing is I still could not read yet, but i was trying out what happens if If i do this or if i do that. After that I have tried out many languages and found what I like and dislike.

#9 french_hustler   Members   -  Reputation: 341

Like
1Likes
Like

Posted 20 August 2012 - 10:24 AM

My biggest growth as a C++ programmer happened after 6 months or so at my first job after graduating. I work as a graphics programmer, and upon starting, I had never worked on a large project or with a team. Being around other programmers and tackling large scale projects and problems really made me better. Sharing knowledge with others and getting a lot of practice in making clean code that works has been a huge factor in my growth. I feel more at ease programming and I rarely ever struggle to understand other's code anymore. Practice is key though. As with everything, you need to get out of your comfort zone and practice to expend your knowledge. I've worked with a lot of things I knew nothing about from networking to doing Linux IT work. I feel that these things made me a better programmer as well.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS