61–70 of 89 posts
Earlier quoted context omitted.
http://codereview.stackexchange.com/
How will this work with SE's infamous hatred of discussion threads? I'd imagine posts about code style would generate multiple "right" answers with lots of discussion to be had?
Earlier quoted context omitted.
Maybe fork Discourse? Naturally this would eliminate the crazyness that issues with every SE discussion. I can help.
On a semi-related note, it's silly how there isn't a "canonical" StackOverflow-like site for open discussions yet.
Just curious: how much do such prolific programmers usually charge? (Hourly/daily/etc.)
Sam Soffes of Cheddar fame charges $1000 per hour. http://hire.samsoff.es/
Judging by a post on his blog* I doubt that his was very lucrative for him.
Don't take this the wrong way, but why would I want you to review my code? I would consider adding a few "achievements" like: * I've worked on JS for x years. * I've written client-side JS for x companies. Anyway, you get the idea.
The HN effect only lasts for so long. Once the flash crowd evaporates, prospects need more than such an unvarnished offer before they can act.
Cozy up to your prospects. Release some educational content. Give some examples of how you deliver value with your code reviews.
Going forward, a testimonial strategy definitely wouldn't hurt.
Earlier quoted context omitted.
Maybe fork Discourse? Naturally this would eliminate the crazyness that issues with every SE discussion. I can help.
On a semi-related note, it's silly how there isn't a "canonical" StackOverflow-like site for open discussions yet.
Earlier quoted context omitted.
Maybe because of the fact that bots usually scan the href attribute, but not the onclick attribute?
I would think any self respecting bot would notice "Hey, there's a valid email address on the page source code :D".
Don't take this the wrong way, but why would I want you to review my code? I would consider adding a few "achievements" like: * I've worked on JS for x years. * I've written client-side JS for x companies. Anyway, you get the idea.
Agreed. The HN effect only lasts for so long. Once the flash crowd evaporates, prospects need more than such an unvarnished offer before they can act. Cozy up to your prospects. Release some educational content. Give some examples of how you deliver value with your code reviews. Going forward, a testimonial strategy definitely wouldn't hurt.
Like very well documented and widely used compiler of some language to JavaScript, perhaps?
Holy moly. Didn't expect to see this at the top of HN. Went to grab some dinner, and the ol' inbox is already starting to fill up. Thanks for the warm response. To illuminate the rationale a bit more ... A lot of folks have asked for quick "gut checks", "sanity checks", and similar overviews of their codebases in the past, and this seems like a way to: 1) Help folks out in a way that doesn't entail a massive commitme…
Can you take a high-profile public project (like coffeescript or underscore/lodash or angularjs) and do a code read? (yes I'm aware that you are the man behind coffeescript and underscorejs but I'm sure you can find something in a code read)
Holy moly. Didn't expect to see this at the top of HN. Went to grab some dinner, and the ol' inbox is already starting to fill up. Thanks for the warm response. To illuminate the rationale a bit more ... A lot of folks have asked for quick "gut checks", "sanity checks", and similar overviews of their codebases in the past, and this seems like a way to: 1) Help folks out in a way that doesn't entail a massive commitme…
"And although Code Reads will be entirely confidential, if any of the companies are interested in sharing theirs (perhaps to attract recruits) -- maybe I'll be able to post one or two up publicly." Can you take a high-profile public project (like coffeescript or underscore/lodash or angularjs) and do a code read? (yes I'm aware that you are the man behind coffeescript and underscorejs but I'm sure you can find someth…
I'll admit, it would amuse me.
Earlier quoted context omitted.
> Still open to explanations of why ninjas have an enhanced coding ability though. Do they? Seeing that you can't actually see ninjas, how can you see they have an enhanced coding ability? ;)
When you get into the office, and your code has seemingly magically improved with no explanation visible in your git log, it's ninjas.