Guidance for Learning Programming/Software Engineering

Post Reply New Topic

Textbook ASD guy here.

Need to figure out what my next move is going to be, and as I see all the fields of learning that once were well-suited for an ASD-type (e.g., book-keeping, transactional law, stenography) go the way of the dodo because of software, I want to be the one writing the software.

How would the experienced computer science, software engineer, EEs, and IT professional suggest learning programming? This is assuming a basically blank slate... Knowing what you know now, how would you do it over?

Thank you so much!

There are many beginning programming books available on Amazon. Your choice of first programming language should be influenced by your existing computer/info tech experience (do you use Linux, Windows, Mac; have you worked in IT in any other capacity, etc). That said, a good starting language might be C# .Net on Windows or Java on Linux. Or, HTML5 if you want to be a web designer.

Getting started can be tricky. You might consider taking a low level course at a community college.

I'm interested in learning programming and web development. Having realised I'm an aspie I've decided to work with my natural abilities. I'm starting with HTML. Good luck!

I wouldn't call myself an "experienced software engineer", but I have a more than a decade experience in the field of programming (I started when I was a child).
What you should do is to start with a language that is simple and doesn't require too much theoretic understanding of how computer architecture works. The best choice would be Python. After that, you would understand how programming works better and better, and could switch to another language, such as C++.
You should choose a way of learning which suits you - you should try out many ways of learning and try to combine them - YouTube tutorials, short articles, book chapters...

Personally, I learned a lot from example code and from the tutorials on YouTube and short articles.
Also, try to modify basic code to see how it works, play with it - this is a good way to make huge gains in programming understanding in a very short time.

For me, programming never 'stuck' until I had something to apply it to.
I started working as a drafter, using AutoCAD. And realized I could relieve a lot of tedium by automating repetitive tasks. It sorta grew from there (AutoLISP, scripting, VBA).
XML and HTML followed.
I'm getting more into JavaScript and SQL now, but, much as I tried to learn them in the past, couldn't do it until now because I have a practical application to use them at work.

Hope your brain works better than mine at that.

Look what the Cat Dragged in.....Daria!

What up, home-skillet?

Got a new job working from home and finally feel like I have my sanity back, so wasn't immediately compelled to return here to rant and rave like I used to do.

Did you miss me?

Ah...but of course I missed you!

How's the family?

Wait, you were insane?

Not clinically, no... but, I definitely felt less in control and solid than i had since I was a kid. The constant onslaught of noise and stress and smells and just always an undercurrent of excessive emotions from everyone around me.
I wasn't insane, but, I was definitely in a bad place, on edge and really really close to some sort of outburst.
I haven't really had outbursts since I was young... I might shut down and go non-verbal and that's the end of it... that working situation pushed me past the end of it.

I was so upset with myself, for managing to land a job like that with a company like that in the first place and I hate to quit anything, but... I have to know my limits. Working someplace like that is definitely well past them. I'm just fortunate I was able to find another position, working from home, that will allow me to continue to learn, instead of just freak me out every day.

I'm glad you found this position, too.

Sorry to hear this happened but I'm glad to hear you're feeling better.

Based on your I was under the impression that you didn't have any limits. It seemed like you could do infinite amounts of work without food, rest or sleep.

Anyway there is no shame in being human like the rest of us.

It depends on what you want to program. Some scripting languages I've just taught myself, however I had something specific in mind that I wanted to program with them. C++ I took classes in because they were required for my major. I think C++ would have been more difficult for me to learn on my own, simply because I wouldn't have been able to easily think up things to do with it. It does not have a built in graphical interface and is more of a behind the scenes work language, but it's also very powerful.

I think I would start by taking a class that can teach you how to produce something of substance, like a game, but then also take C++ and Java classes through CS departments, to shore up your understanding of coding theory.

I have heard a lot of good things about Codecademy.

The best way to understand programming is to program things, reading books only gets you so far. Set a goal for yourself to develop something, and get to it. Use the books for seeing what's possible and for looking things up.

What programming language you choose doesn't matter very much, many programming skills can be applied in any programming language. For the sake of learning, I think a language that gives you clear errors and elaborate stack traces when you make a mistake is the best. Java or Python are fine choices here. I recommend against C++, it's pretty vague when errors happen, at least by default. It's pretty easy to pick up C++ later, after you've mastered either Python or Java.

I personally found "How to think like a computer programmer" very helpful, it's available in both a Python and Java edition, and free:

http://greenteapress.com/wp/think-python-2e/

http://greenteapress.com/wp/think-java/

It's not the language that generates the errors, it's the compiler. The vast majority of errors I've made were due to a missing bracket or semi colon. The programmer just needs to be aware of the fact that one error can cause the compiler to tell you there are many errors, because that one error has taken the code out of context and the compiler doesn't know what it's looking at.