I use JS a lot these days but it's not the first one I learned (it was the second). My first foray into programming was a combination of C++ and GameMaker Language. I wanted to make games when I grew up and I remember reading everywhere that C++ was the language to learn. I was also using GameMaker a lot after school to hack together terrible prototypes which, at the time, used GameMaker Language.
After reading through hundreds of pages of a introduction to C++ book, I still never really got the hang of C++ but some of that knowledge stuck around and helped out with JS and Python. Today I haven't written any C++ or GameMaker Language in years but I'm sure they helped me get to where I am now.
What was the first programming language you learned and why did you learn it? Did you have a choice or was it by necessity?
Top comments (84)
Locomotive Basic (Amstrad CPC 6128)
I wanted to learn writing games.
Z80 Assember (beginner Level)
QuickBASIC (games)
Turbo Pascal (Applications, Games)
80386 Assembler (Games, graphics programming)
Delphi (Applications)
Perl (Web, Shell, Backend)
Java 1.1 (Applets, graphics/games programming)
Javascript, Actionscript (Web)
..
..
..
That's a lot of variation. It sounds like you chose languages for developing games. Do you still develop games today and what are using now?
I studied graphics/communication design. But today I'm writing business applications. Frontend and Backend.
I use Java,PHP,Perl,Clojure in the backend
and Javascript,Typescript,Angular,clojurescript on the frontend.
When I have time I'm playing with erlang,prolog and purescript.
Awesome stuff, is ClojureScript a new addition to the stack? What's your favourite feature of Clojure that makes you more productive?
figwheel and shadow-cljs are very great!
I think the immutable nature of clojure's datatypes is one point why this works.
the good interoperability with the javascript language
the simplicity of the language. I'd like e.g. purescript too. But often you fight with the type system and forget to solve the problem first.
Pascal, because that's what my uni was teaching at the moment X3
Have you used Pascal recently or do you mainly use C# now?
I mainly use C# nowadays but I used to jump around languages, environments and frameworks before I got a stable job and became an adult 😅
Pascal dried up around here decades ago. Never encountered a need to learn C, C++, or C#.
What's your language of choice?
BASIC on my ZX Spectrum +2 waaaaaay back in the 80s. As a child I found it fascinating being able make the computer run these simple programs. It was the only language available on that early home computer and if I recall correctly it came with a BASIC manual that I taught myself from.
"As a child I found it fascinating being able make the computer run these simple programs"
I remember my very first program ever... It was in the 80's and I have been studying BASIC only on paper, on hobby electronics magazines (in Italy there was Nuova Elettronica [New Electronics], a very good magazine with lots of very interesting projects and tutorials... I learned a lot from it).
One day I was at a computer exposition and there was this computer available with BASIC on board. I wrote a small program that printed the multiplication table of "2" with just a basic for loop...
I still remember how much I was excited (my heart was running) when I typed "RUN" and saw the multiplication table printed on the screen...
That’s so cool, I think that is the power of programming! Making something appear on screen with some simple commands is a great first experience.
There is a wealth of knowledge about programming these days, I know others learned programming this way too.
Do you think programming is as accessible to newcomers as it was in the 80s?
(I understand a reference manual probably wasn't the most intuitive way to learn)
Programming computers was basically a mystical science back then, most people had never seen a computer in person and the web didn't exist. So for most people I think the thought of learning to program computers didn't occur, it was a very niche thing, certainly where I grew up. I was lucky in that my primary school had begin given a Tandy personal computer, which they had no idea what to do with so they just let kids like me play around with it to our hearts content. That inspired me to ask for a computer of my own (the trusty Spectrum) which I was lucky enough to get and from there I was hooked.
Today I think programming is both more accessible due to the vast resources freely available on the web, but possibly also more daunting to get started due to the bewildering array of languages, platforms and frameworks now available.
That said, I recently helped out at with a class of 10 year olds learning code on hourofcode.com and it was amazing how naturally they all took to it. For them I think coding or programming will be less of a specialisation and more something most people can do a bit of, like maths.
It must have been very rewarding to help out with Hour of Code! I have to agree with you that I think there is son much information which is freely available and accessible but it could be overwhelming.
It would be great to see programming a bigger part of the school curriculum. I hated trigonometry and mathematics in general while at school. When it came to programming, I loved learning about trigonometry in the context of solving programming problems.
Isn't the web itself made computer and code more accessible - not only by making documentation accessible but by making everybody able to see code source of things they can directly see?
I think the first time I was placed in front of code was when I clicked on "View source" in IE4 or something. I remember Berners Lee saying something like that in his recent article (can't find the source unfortunately).
Definitely, the thing that attracted me to the web is that before GitHub, websites were a way to see source easily. Inspecting a webpage would give you unminified JS. It could give you ideas about how to tackle a problem in CSS by seeing how your favourite website solved it.
This is still the case today however, build tools have resulted in less easy to understand web pages from a learning perspective. The client side code is often obfuscated and minified for performance.
Basic was the first ever intro into programming I had. Pascal, was the first ever language I used. We were thought this to prep for programming competitions. Most of it was self thought though. We were just given a book. Haven't used Pascal for anything else since.
You got harangued with the whole "learn PASCAL: it will properly teach you structured programming" spiel?
I was 13, didn't know much. Most of the academics and my teachers thought Pascal would be really good for programming competitions.
Yes. I gave that speil.
Structured, hard typed, learn it well and you are ready to go do anything else.
Ironically, I find that having cut my teeth on structured and strongly-typed programming, I have to let go of a lot of habits to use loosely-typed languages.
My first ever was Basic (way before Microsoft came out with visual basic).
I was a kid at elementary school, 3rd or 4th grade, and that's what my best friend was learning to write on the Apple computer his parents bought for him. That was at least 30 years ago. Later on, in high-school we learned Pascal.
My first ever programming language as a professional software developer was VBScript, writing ASP3 / WML based mobile websites.
Today I work with .Net and c#, mostly writing services and the occasional WPF desktop application.
Thanks for sharing your journey. Do you think your early exposure to Basic and eventually VBScript lead you towards using the .NET ecosystem?
No. I think that it has more to do with my job at the time.
I've started with an 800 course on web development and Java. That was back in the late nineties, and we learned Microsoft technologies for Web Dev such as ASP3 and VBScript. Before that course was over I found myself working in a startup, right before the .Com bubble burst. In a later job, a few years after, I got into VisualBasic working on desktop applications, and later (same job) into VB.Net/winforms because the company I worked for needed me to do that. Moving to c# was only when I left to work for another company.
I never needed VBScript or .Net for work. The one class I took that used VBScript showed me it was a horrible language.
Too much like English too little like an actual programming language.
Applesoft BASIC as my Uncle let me use his Apple IIC then some Assembly and Pascal as much as I could with limited info. I was saving up to buy a C compiler which if I remember correctly was around $100.
Let's see...
Started with a dialect of Scheme called Racket (known back then as DrScheme) when I was a pre-teen (I expressed interest in learning to code, and that's what my father (who's a software engineer himself) suggested), never went past tutorials with that, and gave up pretty quickly. Toyed a tiny bit with C shortly afterwards but never went very far at the time. Technically learned basic Ruby, and JS (that is, I read the language definitions, but never wrote any code) at about the same time.
Fast-forward to my senior year in high-school when I took a course on BASIC (using FreeBASIC) which I mostly regret (I developed a lot of bad coding habits as a result of it). Started learning Lua at about the same time (mostly because of being a bit beyond obsessed with the original Star Wars Battlefront II, which uses Lua for a lot of stuff internally) and got a LEGO Mindstorms NXT set (with their weird native graphical coding environment) but never went very far with either. Started learning shell script about a year later because of learning to use Linux, and pretty quickly started learning Python after that as well as actually using some C (it's kind of hard to work on a POSIX-like system without picking up at least a little C).
Now, almost a decade later, the only things I actively use today are shell script and Python. I occasionally drop to Lua for rapid prototyping of algorithms (faster at run time than Python without the feedback delas from a compiled language), but that's getting less and less frequent (not because I don't like Lua, but because I have less and less need to prototype algorithms). I spent the past 9 months learning JS properly, and am reasonably competent with it, though I likely won't use it much and absolutely despise a number of things about the language. I also just started (past few weeks) learning Elixir, which I've been mostly enjoying so far but also don't expect to end up using all that much.
That's a really interesting journey, it sounds like you've jumped around a lot.
Firstly, what were the biggest challenges you faced learning programming in some of your earlier endeavours i.e. Racket and C?
Secondly, it sounds like Python is the one you use the most today, along with shell scripting, why do you think these clicked?
The biggest issue for me with Racket was the syntax. For some reason, I just can't consistently wrap my head around LISP-style syntaxes like Scheme (and by extension, Racket) has. Even today, with multiple years of experience programming, I have to put a lot more mental energy into understanding LISP or Scheme, or SmallTalk, or even OCaml than most other languages when I'm reading code.
C, OTOH, was mostly a case of just not getting any real experience. At the time, I hadn't really 'discovered' FOSS yet, so my only percieved option was to shell out money for Visual Studio, which I had absolutely zero interest in doing (aside from not having any practical way to earn that much money either). I'm actually reasonably competent with C these days, but I don't really use it much because very little that I do actually needs it.
Somewhat ironically, I had issues with BASIC too when I was taking that course in high-school because the prior (limited) experience with Racket and C meant I was already thinking at a much lower level than the dialect of BASIC we used operated.
For shell script, it's necessity. I work IT and mostly deal with UNIX-like systems, as well as using Linux on most of my personal systems, so it's kind of hard for me to get anything done on a computer without knowing at least some shell script.
For Python, I think it's that so many things about it are just kind of intuitive for me. The off-sides syntax just makes sense to me, exception handling in Python has always seemed more robust and well designed than other languages, the concepts around context managers fit perfectly with the way I think, etc. The robust standard library has also been a major factor for me, as it means I quite often don't need any external dependencies.
Great points, thanks for sharing your insight. Python seems to be a favourite among Dev Ops and IT because as you said, you can be productive with an extensive standard library.
I started with PHP back in 2008, at the time PHP, Ruby, ASP.NET, and Java where popular languages for server-side programming.
I choose PHP because it had the most resource and everyone I know recommended it.
Nice, do you still use PHP today? How has it changed since when you started?
no, I moved from PHP to Node.js in 2012 and nowadays I use mostly Go alongside Node.js.
I also want to give Elixir a try too.
I was 14 years old. The 56k internet was down for some reasons (probably because we had a cheap plans and used it all) and I started browsing the C:/ drive. I ended up in the browser cache reading some JavaScript.
Then, I learned the whole HTML, CSS, Js, PHP stack, C and C++, python, R,...
That's a unique introduction, I remember the days of 56K and negotiating with the phone line. I'm glad those days are over.
How did you bridge the gap from cached JS you stumbled on, to learning about web development?
Well I just started playing with the code to see what it was doing, but I had to properly learn programming from tutorials. I read openclassrooms.com/en/ at the time :D
That looks like a great resource, I haven’t come across this one before.
I started with Visual Basic 6.0, then I decided that I want to be a web developer, so I learned HTML, then JS, then CSS, and PHP.
Today, I mostly code in JS and PHP, and if you squeeze my arm I write Python and Golang.
What did I learn from all of that? Well, the language itself doesn't really matter.
That an interesting journey!
I think this is becoming more and more true, in the past it was much more difficult because languages were more closely tied to the platforms you wanted to support. With languages like JS transcending the web, it's more true than ever.
And JS is a horrible language.
That may be but it's had an undeniable impact on the web.