Some programmers balk at the idea of teaching PHP with plain HTML/CSS instead of teaching using Rails + Angular + all the fancy crap they like, but I've taught web dev to over 500+ students in the past 7+ years (and programming/CS to about twice that), and it's worked like a charm (and the people who get the most upset by that notion are often those who have taught 0 students).
My girlfriend is an art teacher, and when they teach new students they don't start right away with watercolor or oil paints; rather, they start with materials that are easier to handle for beginners (e.g. plain pencil), so they can focus on the basics before tackling the more subtle and advanced techniques. Why are we trying to teach programming using all the fancy tools and technologies used in production systems?
You can add things like templates (they're built in, and can be really simple) or just concatenate HTML the old-fashioned way. You can program very imperatively and work up to abstractions. It's very friendly.
I haven't seen it used as an introductory "language" but I feel like it would work well.
Having worked with absolute beginners, this isn't nearly as easy as you think for someone just getting started. You're adding ssh keys, getting set up with git, installing the heroku client, running things from the command line, dealing with dependencies, dealing with heroku config file issues...
These are the things that get extremely frustrating very quickly to someone who doesn't have a technical background, and they cause people to give up.
Compared with: start a shared hosting account for $2/month, connect with a gui FTP client and the password you made during signup, drag and drop files to the server, go to http://www.yourserver.com/foo.php and see if it works.
If it's about learning the most basic fundamentals, PHP just works. It will be some time before these people start building things where security, scale, separation of concerns, version control etc start to count. Introducing too many things at once is frustrating, and the fun starts when you can use the things you're building, and share them with others. There's not much that's better than PHP in that regard.
Once everything is set up, it's two-ish commands to commit and push to somewhere like Heroku.
And no, I haven't taught beginners at all, I'll fess up to that. I've learned alongside them, though. PHP is a perfectly cromulent language/framework for this sort of thing, but something like Flask could be just as accessible.
Right click xampp icon and start services
Ubuntu: sudo apt-get install apache2 php5 mysql-server php5-mysql
sudo service apache2 start/restart
sudo service mysql start/restart
copy files to /var/www/
"getting FTP set up to get into your remote server"
sudo apt-get install ssh sudo service ssh start
Does that apply to you?
I think something like Flask might be a worthy successor. Heck it even includes a webserver, no need to fiddle with installing Apache to test stuff locally. And with services like Heroku the barrier to getting it online is almost as low as PHP.
> but I've taught web dev to over 500+ students in the past 7+ years
Setting up a web server with e.g. Python's SimpleHTTPServer is absolutely trivial, and teaches them a lot more about what a web server actually does (routing requests and building responses), and also prepares the students to use whatever hip python stuff people are doing servers in these days.
Might that give students a false impression of what a webserver does and is capable of doing? The students can implement the same thing themselves in a few lines of python, rather than offload most of the functionality to a monolithic and unapproachable black box like apache or nginx.
Edit: to clarify, I read about "routing" in "web-apps" now and then. I have problems figuring out, although it seems to be clear to anyone. And then you come and mess up terms even more, while routing is absolutely not essential to a web-server. Also, if your idea of routing is anywhere near apache's rewrite-rules, I don't wanna know it. If on the other hand routing is essential to an ftp server, I'd be curious.
I agree with everything you wrote, of course. Kids need to learn how to CODE first with simple, non-magical tools. Experience with the other bells and whistles comes later.
Wait, either a) PHP isn't a production system, :) or b) you are blaming yourself for using it, or c) ...
At least you have Google, Bing, Yahoo, ...
Kids these days. :)
That stuff is 80% of practical software engineering. The other 20% is communicating with other people.
If you want to be good at your job, you've got to put in the hours to learn the stuff that isn't in the books. The same as any other skilled career. If you want to worry about the niceties of programming languages all day, go into academia.
Also, I feel we are talking about students quite a few steps below the stage where engineer vs. academia discussions become relevant.
The comment about academia was a bit silly, true. I was trying to say that it's the only place where you can have the luxury of thinking about "pure" programming as a primary concern.
This! In my team, everyone comes to me for help with their problems. Generally, 75% of the time, I know the answer (because I've come across it before). And the other 25%, I solve their novel problem because I ask the right questions, and use basic problem-solving and problem-narrowing steps.
It really isn't rocket-science, it's just analytical, or problem-solving ability. I suppose it has many names. After burning much over other peoples' problems, I eventually resorted to guiding them towards the right direction. Asking them what they think is the problem, getting them to tell me their thought-processes. It's helped quite a bit...
Hm, though I see your point, and agree that "googling" is an actual skill you can acquire and improve by yourself, I feel it's not that different from any other skill, generic or not. I mean, before structure dawned upon playing piano or coding, to learn, the task was problem solving.
To me, there's no essential difference between "this note sounds wrong, why is that, let me try another one" to "how do I get my damn website online". If one beginner's learning process can have structure, why not the other's.
Searching for knowledge/information, discovering domain-specific terms, then finding their definitions... these are all very important parts of learning.
Any time I've had to get into a new domain, I start off with searching. Then you discover new terms specific to that domain, then you learn those terms, then you apply those terms to learn more in-depth topics about the domain you're learning about. Before you know it, you're a jack of a new domain (or more than a jack, if you put the time in).
Are there not tutorials like that?
And then there would be next steps, using free tiers of online services to add a backend etc. There's quite a lot of places to go from there though. What would be best?
I think there's a few others which also follow the approach of each lesson essentially culminating in a new portfolio piece.
You'll get a lesson a week for 10 weeks. The lessons are text-format, combining a balance of challenges with instruction.
It should be:
html -> css -> Javascript (-> php) -> Hover(DNS) -> AWS(server) -> Final assembly -> Live product! -> github -> promotion/advertising/fluff
Available for $10 until friday pm (says usual price $199 but there's usually a discount on) and includes a year or so of hosting on Rob the teachers servers. I've been doing some bits myself. He also has a how to earn money while doing it by pitching your services on elance guide. It has detailed instructions to get the stuff up on the servers, for web at any rate.
https://www.udemy.com/complete-web-developer-course/?hb=get1...
Search for: "hosting html5 javascript steroids.js"
Because AppGyver seems to be related to some sort of JS framework called steroids.js. I'm not going to do it for you, but presumably there is a logical search chain that gets you from "javascript" or "javascript framework" to "Steroids.js".
Yes, I search a lot. It's the third most useful tool I have at my human disposal, just after "touch-typing" and "problem-solving ability".
As a wannabe programmer, one thing I always lacked from these sites was the ability to somehow see my code live. I.e. it's fun to write html and css on codecademy or python from LPTHW or whatever but how on earth do I get it on the web or assembled into .app? In actuality, the complexity that surrounds DNS providers, server apps (or whatever you call filezilla etc), server providers (here i mean heroku, AWS, Cloudflare etc), those weird githubs and repos that people chat about etc etc, is way more deterring than actually learning what a "class" is.
Learning is fun; endless googling is not.