81–89 of 89 posts
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.
I'd get a lot out of it as I'm building a Javascript static analysis tool - exposure to lots of production code would identify how useful its features would be.
I'm no Jeremy Ashkenas, but:
- I've been writing JS apps since 2009, after I stopped doing AS3 apps with Flex
- Teach Backbone.js, JS and d3 at General Assembly, have given various talks/workshops
- Lead dev on two 10k+ LOC JS apps (for Picklive and Skimlinks) using Backbone.js
- Built 3 game clients for Picklive with JS, on mobile and web
- Built a visual scraper recorder/runner plugin for Chrome for Arachnys
- Contribute to JS open source - shims, Sinon.js, lots of little pull requests
https://github.com/timruffles @timruffles
In my previous life as an enterprise code monkey I've came across good and bad Architects. Just knowing and being able to tell me how something could be done better is valuable. But I found my frustration often was 'just f*ing do it!'. If an Architect came with great refactoring suggestions that would take minutes or even seconds to implement, what's the value in dumping me with a document? The best Architects would…
Earlier quoted context omitted.
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.
> Release some educational content. Like very well documented and widely used compiler of some language to JavaScript, perhaps?
Do you know if it would hurt those sales in any way if he inserts a short bio for those who don't?
Earlier quoted context omitted.
Well, we all know that the best people at writing code happen to be ninjas (have you read any job descriptions or got any recruiter emails lately?), so I think this may perhaps be the reason. Still open to explanations of why ninjas have an enhanced coding ability though.
Isn't that obvious ? Ninjas are fast, so they type faster. That's what coding is all about, after all.
On the other hand, I've seen it in the movies that they can disappear... I assume that's what they do before someone can actually try to run their code.
Also, would anyone be interested in dramatic reading of potentially horrible/hilariously bad code?
I think either could be fun, but maybe that's just me.
I could see this being a inflection point for him (or someone who runs with this idea) in a few years. Good luck!
He's talking about very general "code reading" on the whole article and then, at the bottom, he lines out which languages he knows - and it suddenly gets disappointing for anyone outside the Ruby/JS world.
He has to be more clear about that in the headline.