You must log in or register to comment.

Cheeks wrote

Projects small and large! Some languages are for/good for some things others arent. Learn the difference.If you have a grasp on html and css learn the basics of vanilla javascript, from there server side languages, PHP, or fucking .NET. You can use python in that respect but i think it shines more outside of web dev. Maybe thats just me? Just pick some projects and start building!!! The specialization of labor shouldnt be a deterrent to your own education. That shit creates bullshit hierarchies and stifles individual development. get your code on!


throwaway wrote

I use Python as the server language in all my webdev projects, and it's fucking great. Hosting is cheap and easy too. PHP is dying day by day, I'd suggest Python if webdev is what you want to do. It also gives a much better grasp of newer programming languages, and is somewhat easy to get a foothold in compared to something like PHP.


Cheeks wrote

I don't see php dying per se... Its been a major part of what powers the internet for a long time, LAMP has moved primarily to mariadb but python hasnt overtaken php yet. I do agree that overall python is a better language, but php is wonderful despite its pitfalls. Specifically, old folgeys like me that have been using it for 20 years can use it in ways that keep it relevant. ;)


jadedctrl wrote (edited )

Cater to how you like to learn. Different people like to learn differently.

I have this friend who likes to learn by going through books/courses, etc. And that works for him, it's perfect.

For me, though, that stuff's just excruciating. When I try learning that way, I just stop caring about whatever I tried learning in the first place, really.

What I prefer to do is:

  • Pick a simple project that you know you could do (easy enough to be feasible, hard enough that you've got to learn).
  • Skim the Wikibook or something on the programming language until I have just enough to lay the groundwork for the project.
  • Try to brute-force into the project, using StackOverflow and what I know.

… so basically what happens is that I learn more slowly than that friend of mine, but I have fun and manage to stay committed-- whereas with the other model I just end up dropping really quickly.

A lot of people recommend books and courses when it comes to “how to learn programming…” but that doesn't work for everyone, and that's OK. Just figure out which type of model works for you. :)


edmund_the_destroyer wrote

I like all of this advice. I would add that the simple project you pick doesn't have to be better than some tool you already have.

So for example, I use the command line tool rsync a lot to move files around. You don't have to know or care about rsync. If I wanted to learn a new language, I might write an rsync replacement. rsync has a huge set of features and runs very quickly, and my replacement would be slower and have fewer features. But that's fine, the goal is to learn and not to actually replace rsync.


alex wrote

if you live in the US you can see if your library card gets you access to, they have tutorials on Python


Mango wrote

Install python and mess around until something sticks. That was how I learn.