neilwillgettoit

Joined 14 years ago

Karma
695
Submissions
70
Member since
Feb 3
View on Hacker News

Recent submissions

Comment · 1 year ago
https://github.com/ereuter/PyEOT - Eric did a great job breaking down the protocol that was impacted.
Comment · 1 year ago
I originally reported this to ICS-CERT in 2012. The American Association of Railroads denied, deflected, and dismissed the claims for 13 years until CISA finally agreed with me that publication was the only option left to pressure the rail industry to fix this vulnerability. This vulnerability is still unfixed in the USA and all rail operations are vulnerable to it. This could lead to inducing brake failures that could cause a derailment and the ability for anyone to shutdown all rail operations across the USA.
Comment · 10 years ago
Before the switch, 80% of the time I would get the unsolvable ones.
Comment · 10 years ago
The move to the new reCAPTHA alone has made it a lot more usable for tor users.
Comment · 11 years ago
That share via email in their demo is just ripe for abuse.
Comment · 11 years ago
I'd rather not be forced to sign up with twitter.
Comment · 11 years ago
How is this 'analysis' ?
Comment · 11 years ago
That's a great point. It's one thing to be able to program it yourself, and another to understand enough to ask the right questions about the code to learn how it works.

If they had the ability to QA the outsourced team's work at a semi-granular level, I'd imagine there would be a lot less disconnect between the work done and expectations.

Comment · 11 years ago
I think it would be a much more positive indicator if they had chosen to learn the skills necessary to create their product.
Comment · 11 years ago
I would not take a startup that is outsourcing their development seriously. All of the institutional knowledge of how a product works goes right out the door. If you cannot fix your own product if it breaks, do you really own it?
Comment · 11 years ago
That is a fantastic response.
Comment · 11 years ago
Replace 'older candidates' with 'candidates who are less likely to sacrifice their work/life balance.'

1. Candidates that demand compensation for sacrificing their work/life balance are more expensive. Tech isn't that hard to learn. You can get pretty good at a particular tech within 2 years of learning it. Why pay a candidate tons of money for them to give up their work/life balance, when you can hire one that will give it up for little?

2. Candidates that value their non-work time don't know the latest tech. They spend their evenings with their families / kids / friends / hobby whereas those who do are constantly learning the latest stacks at home to benefit their work.

3. Candidates that would rather go do something not work related after work don't pass the 'beer test' with those who's life choices are work-centric.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton