sethherr

First sentence of this is good, the rest is an unnecessary character attack that undermines your point.

The amusing thing is this article suggests people running red lights are a problem, but makes the exact same argument that people make against traffic light cams - "people are going to run red lights anyway, stop ticketing them"

Ticket them and make money for the municipality. Don't engineer new solutions that cost tax payers money and make rodes less safe for people not in cars.

This is my huge problem with the article - it argues we have no control over speeding. And then it suggests places that ticket aggressively are behaving irresponsibly, to the point of villafying a town in Missouri for enforcing its speeding laws. All while skirting the fact that there is a clear correlation between higher speeds and higher fatality rates.

Everyone knows a place cops like to hang out, and slows down accordingly.

Why not enforce speed limits more frequently so people obey them? Why suggest a worse solution (encouraging all drivers to go faster) instead of punishing more people for driving irresponsibly?

That's a reasonable example, but doesn't answer the question: what differentiates it?

I'd say it's something like "involving people without their consent" - e.g. farting on them.

Which includes forcing people to listen to tales of your sexual exploits.

1. People don't follow the checklist

2. People don't understand how to fix broken tests

This piece is about is that exactly. Closing those PRs. Not responding all the time. And that being ok.

That's why they define community as "students, facility, staff, postdoctoral researchers and administrators" - not just people nearby.

SEEKING WORK - Chicago, IL, SF Bay Area or remote

Experienced contractor and full stack developer interested in making useful products and tools. Great at moving quickly and not breaking things, deploying web apps more reliably for less money than you though possible and good enough at design to get by. TDD everything practical. I like Ruby, Rails, React & coffeescript.

https://github.com/sethherr | https://linkedin.com/in/sethherr | seth.william.herratgmail.com

Change.org petition to restore his blog and email: https://www.change.org/p/google-restore-dennis-cooper-s-blog...

TAKE HEED! This is the solution to everything

See, here's the thing: I don't want free private repos to exist. What GitHub has done is incentive making things open source, and that's immeasurably valuable.

I guarantee everyone maintaining a large public project on github has private repos and is paying for the service.

Open source ties in with my work. Every one of my private repos has open source dependencies hosted on github.

Privileging the priorities of my private repos over their public dependencies would be shortsighted.

I came across as aggressively flamey - but what I intended to communicate was the difference in the communities. In the Ruby community, if somebody posted a really long regex driven scraper, people would ask why it was written and recommend looking at libraries/gems instead of writing your own. In Python, it ends up on the front page of HN.

Ruby's community is very pragmatic and Python's is more scientific. Most people I'm discussing learning programming with are interested in making something, and pragmatism is far better suited to their goals.

e.g. from my perspective, as someone who uses programming as a tool, writing my own scraper is boring (other scrapers work well enough for me). From my friend's perspective, writing a scraper is a fun experiment.

This is why I recommend Ruby over Python for web development. The difference between a blog posted code snippet and the wealth of mature, multiple contributor projects like https://github.com/propublica/upton

Agreed. Sort of funny this doesn't make the top of everyone's list.

There's no shipping if you have prime. So you're using sub-standard Amazon.

Here in Chicago I get everything within 48 hours of ordering, often less, and don't pay shipping fees. Some items are free same day shipping.

You must make wildly different hourly rates to think visiting a store and paying the same amount is cheaper than a few clicks on Amazon.

Agreed. Speed, particularly on sub 1 hour drives, is mostly about competitiveness. If you're no longer competing with other divers, because you have a robot that is, what will that extra 10mph do for you?

Particularly when you can work in your car. Or watch a movie in your car. Or have sex.

Github issue discussion: https://github.com/wa/wahoo/issues/95

To see and learn how people work, possibly learning how to do stuff better yourself.

Exactly - why did page caching get removed from rails core?

Exactly. This style interview doesn't find the people I think are valuable - people who ship code. Instead, it validates people who spend time thinking about interview questions.

I made a base rails app for a pattern I've been using recently.

It might be helpful to take a look at it and get it running? I think getting a few apps running locally so that you have at least somewhere to start is useful.

https://news.ycombinator.com/item?id=9090818

I found that I was using this pattern in a number of places, so I thought it would be useful to create a base I could use again.

It isn't government regulation of the internet. It's government regulation of cable companies that provide the internet.

I don't want the government monitoring or restricting my internet. I would like the government to prevent companies from doing that to me.

Agreed, backend isn't going to disappear. I was thinking of learning go, but going for Elixir seems like it might be a better option - happy to have read this.

I don't think ruby/rails is going anywhere for a while though, it's too easy to get things up and running. And I think node is going to be around for a while too, and increased familiarity with javascript is pretty much guaranteed to be helpful, so going that direction isn't a bad idea either.

MerchantOS.

I do appreciate your passion, I would love if you would contact me through the contact form on our site https://bikeindex.org/contact_us

I'll respond immediately, I feel like we might be able to figure out our disagreements if we just chatted together.

Having worked in a shop in ruralish Indiana I can tell you that winters are long, no one comes in, and the internet is a magical wonderland.

We made pixel art, checked every webcomic to see if anything new was published and raced bicycles around inside the shop. And we read a bunch of bike blogs, all the time, every day. We sure as hell would have been on twitter if it existed, if only to mock other people.

Also, only a fool stands on concrete all day. You put down a mat or at least some cardboard.

We're already doing all the above (except magazine ads, which we're working on).

1. Ok.

2. Let's say 15 shops in the 10 cities.

3. The third party will undoubtedly need to call the police. But what are you allowed to do until they arrive? And what will they do when they arrive?

4. Y'see, we aren't aiming to go to 289 cities. We're aiming to raise publicity and interact with bike shops in the areas of the country that a lot of bikers live. Individually approaching all the shops in the country isn't feasible and would be stupid. But joe average shop owner in nebraska will be much more likely to sign his shop up for the Bike Index if he knows a shop in NYC that he follows on twitter has.

5. We aren't looking for serious revenue through people paying for registration. Bike shops benefit when you visit them - so they're happy to get you in there. And we're giving iframe forms to bike advocacy organizations (like EBBC) so you can register on their site (for free). We also go to events and register bikes for free. But we think the service is valuable, and people are much happier getting a registration for free that would've cost 6.99 (which to us still seems like a pretty good deal - the national bike registry charges $10 and throws away your registration after 10 years).

Great! Don't back the project.

I worked as mechanic for quite a few years - the whole reason that I built the service was because I wished that I could do this for customers. We've had shops in Chicago registering all the bikes they sell all summer long. I do agree though - things get hectic, and we want to make it easier - which is why we're working on integrating with point of sale systems, so bikes are automatically registered at checkout if a box is checked.

And while we started the Bike Index to fight theft, we really don't think that it's the only use of the system - and we are focusing on registering bikes before they are stolen. So a name that highlights theft isn't our goal.

Honestly, all the nice bikes I've sold had beautiful up-to-date manuals (Specialized even includes a DVD), but no one read them anyway, so I don't think that's the solution. Especially when shops already have the serial number and manufacturer in their checkout system.

We do want to partner with manufacturers, but we want to make sure it continues to be a service for the biking community rather than a trick to get more marketing information for manufacturers. And to achieve that we need to approach manufacturers after already having a base - hence our Kickstarter project.