After playing a little bit with QBasic when I was a kid, I was given a K&R C book. My takeaway: programming is not for me. I didn't look at programming seriously again until I was 23. This article is terrible advice.https://www.zeroequalsfalse.press/2017/11/29/c/
-
Show this thread
-
Incidentally, a relative who was really interested in programming went to college and her first course was in C++. It was too much too fast and she quit (and never became a programmer). Unless we're actively trying to reduce the number of programmers, don't start with C or C++.
37 replies 46 retweets 200 likesShow this thread -
Replying to @wycats
I've been grappling with this at the undergraduate level (where we do start with C++) for our object oriented course. What do you think are better options? Ruby?
5 replies 0 retweets 7 likes -
Replying to @ProblematicProf
Ruby, JavaScript. But the main thing is start making things that you can share with others right away. Create a blog and start tweaking it in ways *you want*. There's nothing more motivating in programming than seeing an idea you had in your head take form.
7 replies 12 retweets 126 likes -
Replying to @wycats
I completely agree with you on C - it's a terrible language. But as a first language, Ruby and Javascript are terrible choices as well - you may have more fun, but you will likely learn how to do everything wrong.https://medium.com/@mindplay/the-problem-with-learning-languages-like-javascript-php-ruby-or-python-first-is-you-can-get-away-7accc689d365 …
3 replies 0 retweets 10 likes -
Replying to @mindplaydk
Can you give an example of something "loose" you can get away with in both Ruby and JavaScript that you can't do in Go that you have to spend years to unlearn?
2 replies 0 retweets 3 likes -
Replying to @wycats
Put any JS code through the Typescript compiler in strict mode - it will show you everything that's wrong, missing, undocumented, etc. Correct everything, and you will discover that most JS is jam-packed with subtle (or sometimes horrible) bugs.
1 reply 0 retweets 1 like
That isn't the question I asked. What's an example of something you can get away with in JS and Ruby (the "loose languages") in your post that Go protects you from?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.