Review: Coding 101 - Episode 3

[G+_Joe C. Hecht]

Review: Coding 101 - Episode 3

 

The folks here at the Code4Sale ofices are reporting that Episode 3 of TWiT's "Coding 101" was much improved over the first two episodes (and beta).

 

Slowing down, explaining things, and not talking over each other, where the top three reasons cited for the improvement.

 

Still, it seems that the suggestions for the use of pre-made materials might be a safe bet, as the main code example demonstrated on the chalkboard had a pretty good error.

 

To be fair, it has to be a very tough job to do the show live. While the Padre does handle the pressure very well, demonstrating incorrect code examples (without noticing) only serves to confuse the viewers. Bets are already being placed on if the blooper will get edited.

 

Interestingly, the show hosts claim that the "Coding 101" is not about learning to code, but more about "encouraging people" to learn about code, noting that in three episodes, they have yet to give any real examples of why someone would want to learn to code, and the only encouragement so far has been to say "just try it and break it".

 

Once might guess that the real value of the show is in the lessons taught, and the entire show does seem to be dedicated to giving lessons about how to code. The stated purpose of the show seems to be the exact opposite of both the advertised content and what the show presents.

 

Chat room regulars agreed that the stated purpose of the show and it's actual content are in direct conflict, posting comments that the show title should be renamed to something that does not indicate the classroom learning experience that it seems to be.

 

The show is slowly progressing. Episode three added explanations for "equals", "greater than", "less than", and "not equal" to the loop exercise started in episode one.

 

But is the show a good value for time spent? It depends on how much you value your time, and what side of the table you are sitting on.

 

So far, viewers have been given links to download a couple of compilers, they where shown a "while loop", and have been told to "play with it and break it". While I do not think that is much value for a 90 minute viewing investment, there certainly seems to be a  fair amount of people that have followed the dispensed advice, and are more than content with the outcome. Still, in 30 minutes, I expect a bit more bang for the buck than to learn what "equals" and "not equals" means.

 

On the other side of the table, you have the advertisers (Lynda.com), and the show's owner, Leo Laport's TWIT, both counting the coins to see if the show will move from the red ink and into the black.

 

Finally, with the TWiT network seemly suffering talent drain, we are starting to wonder just how many shows Padre SJ can successfully juggle.

 

With all the energy of ten fair sized dynamos, my bet is on the Padre!

 

In fact, given a bit of time, and a bit of Vatican financing, I would not be at all surprised to someday hear the words:

 

"This is Leo Laport, and your listening to the Padre SJ radio network".

 

TJoe - Joe C. Hecht

Code4Sale, LLC

[G+_BrightSilence]

That is a lot of words for a mistake that becomes obvious in your first sentence. This show is clearly not for you.

 

Now there are two things you can do. Use your experience in the field to help out the people who do enjoy the show. Or stop coming back here.

 

Take your pick, but I doubt the rest of the feedback is very useful.

[G+_Joe C. Hecht]

Interesting that you would make the assumption that I have not been helping some of the people who do enjoy the show.  I paid my dues on that one, long before I picked up my pen.

[G+_BrightSilence]

I didn't assume that, nor did I mean to imply it. I'm just saying that it seems to be working to get people to take the first few steps into the world of programming. So you seem to be trying to fix some that isn't broken. At least according to the audience it is actually meant for.

 

I've seen you help out. And that's great. I just don't think the negativity is very helpful.

[G+_Joe C. Hecht]

Not sure anyone has seen me do anything but complain, (at least here), but FWIW, I clocked over 10 hours of giving assistance with Coding 101 this week alone.

 

Please dont get me wrong, I TOTALLY support this show, and I certainly hope and pray it gets as many new folks learning to code (and off on the right foot) as possible!

 

And I also have a little surprise contribution for the community coming as well - (running late due to medical issue I am involved with).

 

OK, so your right. Allow me to sign off with something helpful to the community:

 

One of the best things you can do when first starting to code is to get into good coding habits early in the game.

 

I cannot stress that enough.

 

There is a book, (once was freely available?) called "Code Complete". It may be a little too much info for those just starting out (today), but tomorrow is a new day, and if you are still coding tomorrow , then go get this book!

 

There. That may not seem like much, but trust me, someone is going to get a lot of mileage from it!

 

[and no, I had nothing to do with the book - but I do wish I had read it long before I did]

 

TJoe(h^);

[G+_BrightSilence]

I definitely agree that it's great to get into the right habits from day one. But like many others I learned to program by just playing with the code and starting with simple things.

 

Mostly self taught... Ofcourse the problem with that is exactly what you describe. Bad habits. I think it's a necessary evil though, I know very few people who learned to program the right way right away.

 

First you need to get into it. Because if you're not having fun with it you won't be interested in doing it right.

 

It's learn and relearn I guess. I'll jot that title down though. Still need to shake some bad habits for sure.

[G+_Joe C. Hecht]

I too was self taught, and often think back to my first

experiences at coding, where I went in short order from

"code-zero" on a Timex Sinclair to "code-all", and

participating in everything from the first Windows print

driver to the first Disney Interactive Game CD engine.

 

For that reason, I am not ever going sell short the

capabilities of a beginner. Right here, right now,

someone in this Coding 101 community is probably

getting their start at becoming the next great code

guru.

 

Thats why I feel so passionately that "Coding 101"

should deliver the best it possibly can, and I will

rock the boat if thats what it takes to make it happen!

 

Padre SJ said the following, and I took it to heart:

 

"Have you ever seen something in your daily life,

something that people take for granted, and you say 

"Why is it made that way - That's stupid!, That's

ridiculous!"  

 

Here is something I want to challenge the chat room to do:

 

If you look around, and find something that we have taken for

granted, it can be anything, anything you think we need to

redesign, then I want to hear from YOU!

 

TJoe(h^);

[G+_Christopher B. March]

I used to have the Timex Sinclair 1000 and then later on the 2068 color version, which was better because it had an actual keyboard and not just a membrane keyboard.  I also bought the subscription to the U.K magazine ZX computing.....I spent hours writing the code in the magazine....most of the time the program worked afterwards, sometimes it didn't ...frustrating when that happened.

[G+_Joe C. Hecht]

LOL! I had a Sinclar.