[deleted]
Show HN: Learn to Code for Free
81–90 of 139 posts
Re: Show HN: Learn to Code for Free
#82I'm guessing this course isn't aimed at people who's new to Web development? how are we suppose to know some of those rail commands? like generate scaffold blog posts?
This course is comprehensive and goes from beginner to some fairly advanced content. No previous coding experience is required. You will be guided from the beginning.
Re: Show HN: Learn to Code for Free
#83Earlier quoted context omitted.
>> They need to be able to read other people's code to decipher and debug the coding style they are seeing >> They need to understand other styles so they can form their own After 15 years of working professionally, I kindly have to disagree to a fair extent. It turns out that most - if not all - developers are not very good at writing clean code. Including (especially?) seniors who think they write the best code on…
>> It took me a very, very long time to realize that it's simply a matter of fact that no two developers think alike, . . I was part of ThoughtWorks interview process sometime back. In one of the rounds called Pair Programming, a senior developer worked with me on the given problem statement. I arrived at right solution, but he wasn't happy with the solution just because he didn't like the way I solved it. I came bac…
After experience with several junior developers I plan to do the following to train the next one. First, let them solve an isolated problem in our code base. At pull request step comment excessively (this is what inevitably happens with all junior developers, the PR is so huge that GitHub chokes on it). Finally, pair them with a senior developer to solve the issues raised in the PR, rather than letting them fix them alone and engage in an endless loop of commits and comments.
Re: Show HN: Learn to Code for Free
#84I'm guessing this course isn't aimed at people who's new to Web development? how are we suppose to know some of those rail commands? like generate scaffold blog posts?
This course is comprehensive and goes from beginner to some fairly advanced content. No previous coding experience is required. You will be guided from the beginning.
That sounds nice, How Does it cover HTML, JS and Ruby on Rails in Depth? I assume that would take a long time lol
Re: Show HN: Learn to Code for Free
#85This is incredible. Thank you for your generosity and kindness in opening this up for everyone.
You're welcome! Hope you enjoy the content!
Re: Show HN: Learn to Code for Free
#86how does this compare to www.codermanual.com?
Re: Show HN: Learn to Code for Free
#87I've decided to make my course on complete full-stack web development free, forever! It's a massive amount of content. Please let me know what you think of the course!
I'm going through it as a tech professional who is a non-developer. I know how to code, I just don't do it professionally (and I don't know Ruby, let alone Rails). I'm loving it. Obviously the "here are some commands" and "go find Google Chrome" made me laugh a little but I understand the audience they're for. I love how quickly we get into actually creating something, it keeps my interest when I see progress. It's b…
for you it sounds great but for someone like me I like to understand how things work under the hood. Yeah I made a blog in 15 minutes using Ruby and Rails but how did that happened under the hood? I like to fully understand things not just be told how to do it.
I guess that's why PHP being embedded in HTML allows me to see the bigger picture.
Re: Show HN: Learn to Code for Free
#88Earlier quoted context omitted.
awesome. Thanks. Have bookmarked this for the Christmas break. If you don't mind me asking - how old is the content? And what did you teach at GA?
The content is brand new. Just finished recording it. I teach HTML, CSS, Javascript, and Ruby on Rails at General Assembly.
you guys located in Seattle? I live in Seattle.
Re: Show HN: Learn to Code for Free
#89Earlier quoted context omitted.
>> They need to be able to read other people's code to decipher and debug the coding style they are seeing >> They need to understand other styles so they can form their own After 15 years of working professionally, I kindly have to disagree to a fair extent. It turns out that most - if not all - developers are not very good at writing clean code. Including (especially?) seniors who think they write the best code on…
>> It took me a very, very long time to realize that it's simply a matter of fact that no two developers think alike, . . I was part of ThoughtWorks interview process sometime back. In one of the rounds called Pair Programming, a senior developer worked with me on the given problem statement. I arrived at right solution, but he wasn't happy with the solution just because he didn't like the way I solved it. I came bac…
>> How they can assume or think that two programmers going to solve the problem in "same" ... way!
It takes a lot of restraint and stepping back from being in "first-person developer mode" to understand that someone else's unique approach is quite likely valid. I purport to be able to do so but I still find it incredibly difficult to ignore my brain's initial instinct to start pointing out the supposed flaws in someone else's structure, when the simple fact is my own code for the same problem would probably be filled with the same holes - just in a different form.
Honestly, there are only a few metrics that really matter when it comes to quality code:
1. Does the code accomplish the task it's supposed to? I mean really, this is practically the only thing that really matters in most cases. Simply: if deployed, will it work?
2. Are there no glaring security problems with the implementation?
3. Does the code not excessively overuse resources (cpu, memory, network/system calls, etc.)? Real excess beyond what is reasonable, not micro-optimizing.
4. Is the code not a complete mess? No serial use of copy/paste, crazy spaghetti mess, or inability or blatant refusal to follow basic coding standards?
That's it. Deploy that shit, and move on to the next problem. ;)
Re: Show HN: Learn to Code for Free
#90Earlier quoted context omitted.
>> It took me a very, very long time to realize that it's simply a matter of fact that no two developers think alike, . . I was part of ThoughtWorks interview process sometime back. In one of the rounds called Pair Programming, a senior developer worked with me on the given problem statement. I arrived at right solution, but he wasn't happy with the solution just because he didn't like the way I solved it. I came bac…
After experience with several junior developers I plan to do the following to train the next one. First, let them solve an isolated problem in our code base. At pull request step comment excessively (this is what inevitably happens with all junior developers, the PR is so huge that GitHub chokes on it). Finally, pair them with a senior developer to solve the issues raised in the PR, rather than letting them fix them…
I agree - you very much need to learn the rules first, before you go and break them