Live data from Hacker News

Code Reads

ashkenas.com

51–60 of 89 posts

Re: Code Reads

#51
post #38
post #17

Earlier quoted context omitted.

What's cheddar?

I thought the same. "Fame" didn't seem the right word to apply to it, but when I clicked to the homepage I remembered seeing it on HN before now.

I thought he was making a joke... like trying to bring out the stark contrast between the word fame and the relatively unknown Cheddar.

Re: Code Reads

#52
post #48

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…

I hear you, but I'm concerned about trampling on other folks' code without being involved in a long term relationship. Code bombs dropped by consultants often have this sort of problem -- where some of the more invasive changes either aren't welcome or are more difficult to integrate with the existing system than they're worth. I'm hoping that having inline examples of working code, with references to the source, str…

A combo of doc + a branch commit would be spot on.

You're right on the code bomb problem, but I think a good review involves making a judgement on the entire codebase. Something may be the 'right' thing to do but completely uneconomical due to dependencies.

Understanding the impact of a recommendation leads to a valuable refactor or rewrite call that developers often have to make on a mature ecosystem.

Re: Code Reads

#53
post #16

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.

> 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.

Re: Code Reads

#54
post #44

Interesting. But how is this a sustainable business model?

How is it not? It's not like people are going to stop writing code.

I think what he means is "how does this scale?" If the OP is personally reviewing the code, which the landing page makes it sound like he is, he can only do so many per day, and there will be a long queue if his service is popular.

Re: Code Reads

#55
post #17

Earlier quoted context omitted.

Sam Soffes of Cheddar fame charges $1000 per hour. http://hire.samsoff.es/

What's cheddar?

Cheddar is a task management app. If I recall, he recently sold the app and he was willing to give his services for $1000/hr. https://cheddarapp.com/

Re: Code Reads

#56
post #16
post #13

Earlier quoted context omitted.

Does a robot also need to be a ninja in order to process code quickly? Why so elitist?

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.

Re: Code Reads

#57
post #54
post #44

Earlier quoted context omitted.

How is it not? It's not like people are going to stop writing code.

I think what he means is "how does this scale?" If the OP is personally reviewing the code, which the landing page makes it sound like he is, he can only do so many per day, and there will be a long queue if his service is popular.

Then he can start charging more or delegating, both have benefits/drawbacks obviously.

Re: Code Reads

#58
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.

Re: Code Reads

#59
post #5

I'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…

This may sound cliche but I also thought of a similar concept when reading the post, with the added aspect of reviewing someone's review for 'karma' points. Self-policing, so to speak.

Re: Code Reads

#60
post #58

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.

Hint: google his name. His target audience already knows who he is.
Post reply on HN