Hacker Newsnew | comments | show | ask | jobs | submit | ericclemmons's comments login

I know the are well, and let's just call it Walkable. For comparison, I moved from the suburbs of Houston (14 walking score) to the Montrose area (94) for the same reasons why I live visiting Manhattan - not having to drive most of the time.

Chao's comment is right on. Living in your own pocket is great, but driving to the article's house still takes 20-25 minutes since it's all interior roads.


I checked out both repos but still...not sure what this does. Is there an example of what's supposed to happen when you run these scripts on an example project?

I believe the idea is as follows.

1. Suppose you have contributed to projects A, B, C, D, and E.

2. When someone looks at your profile, they see A, B, C, D, and E listed in a vertical list, apparently sorted by how many contributions you have made to each.

3. You decide that you want the world to know you disavow your contributions to one of these, say, B.

4. You fork the project disavow/above-repository.

5. You make a branch, make some commits, and push them, and then make a pull request. Apparently disavow/above-repository will accept your pull request.

6. disavow/above-repository then appears in your contributions list.

7. Keep making commits to move disavow/above-repository up the list until it is between B (the project you wish to disavow) and C.

8. Now when people look at your contributions list, they see:

I'm not sure what you are supposed to do if you want to disavow a second repository. Maybe they need to make a disavow/below-repository project too.

The idea of disavowing contributions is an interesting one, although it is probably something best handled by convincing Github to support a mechanism for it. More generally, it could be useful to have a mechanism to explain your relationship to a repository you have contributed to. On a project page, you should be able to view the explanations from all the contributors, and on a person's profile, the list of projects they contributed to could also list their explanation.

https://github.com/disavow/below-repository looks like they have that too

It's true that your best shot for a 15% raise is switching jobs, but there's no way that's sustainable (for a comparable position).

I think each year people should evaluate how they're expertise and duties differ from the previous year.

Many people I know inadvertently become team leads, head up projects, mentor others, or change roles entirely and wait for their old position's performance review to address it.

That's a mistake.

As a manager, I've had the best success with getting better comp for my team when giving a new title + bump around 4 months before review.

That way, the discussion with execs is closer to "what eould we pay for a new hire for this position?" and the upcoming review allows for minor comp tweaking.


I have to stop and comment how I've never heard anyone make this analogy, or put it so well!


My most recent is "React Resolver":

> https://github.com/ericclemmons/react-resolver

When React came out, I was disappointed that server-side rendering was pretty much impossible unless you knew _all_ of the data requirements for the entire render tree & loaded them up front.

This project has just underwent a rewrite for React v0.13 that I'm pretty proud of, since it's ES6 and packaged as ES5 via Babel.

It's been fantastic in my personal & work projects, and has made it possible to rebuild a major application that was in PHP entirely in Node w/ progressive enhancement.


We've been rebuilding a major app in Node and searching for validation solutions that would support async.

Embarrassingly, very few Node validation libraries support async!

This makes it annoyingly complex to have multiple sets of validation on the server to ensure a new user is indeed a new user, that foreign keys match their constraints, etc. on top of the dumb type checks.

We ultimately found Schemator from the js-data project: > http://www.js-data.io/v1.5.8/docs/js-data-schema

We've been able to put all of our sync/async constraints into varying "schemas" that run on both the client and the server!


The fact is, there's always a new tool for the job a year or two down the road, but software needs building today.

I launched a major internal admin a year ago with Angular and it's largely on autopilot because Angular is so darn easy to work with when it comes to building new features, especially in the view layer.


Man, I totally agree. Just from the beginning, watching someone get hurt actually made me feel something, compared to the paper-thin characters in other games.

My wife and I planned out each evening to be our "movie night" for this game, and found the pace and story well crafted.



I've done several BBQ tours on my monthly trips from Houston to Austin, and Salt Lick consistently requires a fork.

The half-dozen times I've had Franklin's BBQ, I've witnessed the brisket slab wobble like jello, and can't help but describe the moisture as butter-esque. Seriously, that stuff is so rich you can't eat it often at all.

Still, I've found that even in Texas everyone argues over which bbq is better. Some argue against any sauce, any forks, or anything to imply the meat is less than perfect. I've even had pitmasters argue that tearing at a rib bone with your teeth because the meat is dried on is "correct", and fall-off-the-bone is over/undercooking.

At the very least, Franklin's is different from Rudy's is different from Salt Lick is different from whatever.

It's all preference, but one thing you can bet on is good BBQ will have a good line :)


The best open-source projects are the smaller ones, IMO, which are usually the efforts of a few developers who welcome outside help.

I've contributed to large-ish projects like Symfony2 with high standards, but the community was still encouraging.

Point being, I think the overall community and age of the project are the best indicators for determining how hostile contributing would be.



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact