How I hoped this to be an announcement for a public code reading. Like a author reading a chapter of his book, Jeremy reading and discussing a part of the coffeescript source.
Code Reads
31–40 of 89 posts
Re: Code Reads
#32How I hoped this to be an announcement for a public code reading. Like a author reading a chapter of his book, Jeremy reading and discussing a part of the coffeescript source.
Re: Code Reads
#33Holy 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 commitment or expense. Much of the time, when people are struggling with a thorny technical problem, an outside perspective and a bit of friendly advice is invaluable in getting it solved.
2) Get a lot of valuable exposure to different approaches in production apps, to learn as much as I teach.
3) A style of work that I can be productive with, even without a reliable internet connection, or offline entirely (a large problem these days).
So, it seemed like a fine idea to try. I'll keep y'all posted on how it goes. 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.
Re: Code Reads
#34I'm sure Jeremy can only do so much code reviews a day (unless he's a ninja robot), so why isn't there a crowd-sourced version of this? Sometimes I write code that I would like other coders to help/critique with. Github is great for collaborating and some code reviews happen (pull requests) but sometimes you're just working on a project and have no idea whether you're writing the right things or not. There have been…
Maybe fork Discourse? Naturally this would eliminate the crazyness that issues with every SE discussion. I can help.
Re: Code Reads
#35Earlier 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?
Generally speaking when it comes to SE, I've noticed the smaller the site the bigger the tolerance towards discussions, and codereview it's not quite a big community yet.
Re: Code Reads
#36I always thought there should be a good market for companies hiring outside code reviewer before they hire an employee or a consultancy. Seen many projects crippled by dirty code written by contractors.
Re: Code Reads
#37Probably a silly question, but what's the deal with this? Small Not a huge deal but I think it's good to show where a link goes on mouseover, especially a mailto: link (some mail clients take a while to start) ... it'd seem you want here.
Just started with a bit of CSS that worked better for a button is all. You're right that a real link would be better. I'll change it.
The idea is to perhaps eventually sell these directly on the page, via Stripe, in a more explicit fashion. But for starters at least, I think we'll work together on setting the scope of the "read", and keep things bespoke.
Re: Code Reads
#38Re: Code Reads
#39I'm sure Jeremy can only do so much code reviews a day (unless he's a ninja robot), so why isn't there a crowd-sourced version of this? Sometimes I write code that I would like other coders to help/critique with. Github is great for collaborating and some code reviews happen (pull requests) but sometimes you're just working on a project and have no idea whether you're writing the right things or not. There have been…
Sounds like an awesome project. I think there's room both for open-source-y versions of this, where you review shorter bits of code for the karma -- as well as a more professional version, where you spend a lot of time reviewing private code, in conjunction with testing a prototype of the application.
That said, if anyone is really excited about this sort of thing, and think they'd be good at it -- do drop me a line. I imagine there might be ways to team up.
Re: Code Reads
#40I'm sure Jeremy can only do so much code reviews a day (unless he's a ninja robot), so why isn't there a crowd-sourced version of this? Sometimes I write code that I would like other coders to help/critique with. Github is great for collaborating and some code reviews happen (pull requests) but sometimes you're just working on a project and have no idea whether you're writing the right things or not. There have been…
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.