HNHacker News
TopNewBestAskShowJobs

kevinastone

338 karma · joined December 19, 2012

submissionscomments
kevinastone··on Rb: A Redis parallelization toolkit for Python
Could you expand on why you didn't implement this using Futures?
kevinastone··on Show HN: My SSH server knows who you are
It's a public key for a reason. You need to the private key to authenticate, so you're safe having everyone know your public key.
kevinastone··on Crate: Distributed SQL Database for the Age of Docker
Thought that name was familiar: https://github.com/crateio/crate.io
kevinastone··on Gigaom Closes Down
“How did you go bankrupt? Two ways. Gradually, then suddenly.”

― Ernest Hemingway

kevinastone··on The Tangled Web: A Guide to Securing Modern Web Applications
we're actually reading it collectively in our inaugural engineering book club. I'm about a third the way through, it's full of insights on weaknesses and exploits for web based applications.
kevinastone··on Ask HN: What was the job market like during the dot-com crash?
I graduated in the summer of 2001 (BS ECE). Many of my classmates had their already accepted job offers rescinded before graduation. I ended up working a non-degree job for a year before finding an internship that I worked into a full-time position. Finally found a more permanent career in 2004 when I was hired into an aerospace company (where most of the jobs were).

Keep in mind, besides the dot-com crash and then the sept 11th attacks, the real macro environment of the early 2000s was outsourcing. Everybody believed you could just hire a team in India or Russia for pennies on the dollar. It would take another 5+ years for that trend to reverse as companies recognized the challenges in moving their development resources off-shore.

As I stated, I responded to the off-shore movement by switching to a less-affected industry (aerospace/defense). Most "market corrections" really affect the most vulnerable segments of the job market: entry-level and near-retirement.

kevinastone··on How we’ve made Raptor fast
uWsgi is an implementation of the python WSGi spec that also supports Rack: http://uwsgi-docs.readthedocs.org/en/latest/Ruby.html
kevinastone··on Boeing-SpaceX Team Split Space Taxi Award
It's part of the US Intelligence community, so it depends on your definition of the military. In practical terms, the answer is yes. It's mostly staffed from the Air Force and CIA.
kevinastone··on Data-focused Docker clustering – ClusterHQ
Your webpage doesn't render properly in Safari: https://www.dropbox.com/s/753xgwjhvbb1ml7/Screenshot%202014-...
kevinastone··on Show HN: FiveStar.io – The best Amazon products, by budget
Each key press adds to the push state history. Spams the back button
kevinastone··on Show HN: PyEQS – query Elasticsearch like a Django Queryset
Take a look at ElasticUtils from Mozilla. It also provides a queryset-inspired interface for elasticsearch.

http://elasticutils.readthedocs.org/

kevinastone··on Lessons from a Silicon Valley job search
Yeah, but I assure you that most of your entry level job seekers have no idea and either ask too low or some wildly inflated number (my friend over at blah blah was offered $120k...). It's more about being able to justify your expectations than having an accurate number which is why softer targets like ranges or previous salaries are usually easier.
kevinastone··on Lessons from a Silicon Valley job search
Yeah, fair point. If by Silicon Valley, you mean the large tech companies (like Google, Apple, etc), you're correct that they won't ask your salary expectations since they have their own internal process for determining compensation for a given candidate. (They also generally think they can outbid anyone else).

I have been working with smaller startups (down here in LA, but I've seen the same behavior up north), who tend to filter candidates based on expected salary due to limited resources and hiring for an exact role. (We tend to mask our cheapness by using phrases like "hungry" or "passionate").

kevinastone··on Lessons from a Silicon Valley job search
This is generally good advise (don't suggest willingness to negotiate, because that suggests you will take less).

But, unless you've done research and have confidence that the $80k is viable for your experience and the position, you can also scare off many potential employers.

That's why I'd suggest delaying giving a hard number to much later in the process, after all the screening and interviews when its time to develop an offer. You'll have more information then to justify a given price point and more leverage for a "take it or leave it" moment.

I recommend giving either a range ($70-$90k) or your last salary (I made $70k at my last job, so that's a reasonable minimum I would expect). As an employer, I'd likely start on that low end ($70k) with an initial offer. That gives you the opportunity to decline (I made that at my last job, and my skills and experienced are much improved since), and then give me your terms (say $80k or even higher) with justifications.

kevinastone··on Lessons from a Silicon Valley job search
If your answer to "what salary are you expecting?" is: "I'm fine with a market-rate salary", I'll just ask you what you think market-rate is for your position.

Now, usually, you can just say something like: "market-rate will vary with the type of position, role and responsibilities".

The goal of the recruiter is just to get a confirmation that your expectations are in within the range permitted for the position.

If you suggest that others at Apple or Google are making $X and $Y for the same role, that helps the recruiter identify how you're evaluating a market-rate. It's up to you to not price yourself below what the market may pay for your services.

That's the fallacy of never making the first offer. This expectation that you could be undercutting yourself and your negotiation partner would have offered more. In reality, this almost never happens, especially if the expecatation that the terms are negotiable. The company will just offer the least favorable terms first expectating a counter if they're unsuitable.

kevinastone··on Lessons from a Silicon Valley job search
This routinely great advise (never make the first move!) just doesn't work in practice. Those making the hiring decisions are going to want to identify a range of possible salaries before continuing the recruiting process. Otherwise, if the candidate later demands an extremely high price, we both wasted a lot of time and resources.

Here's what I recommend and have used successfully:

A) Offer a range

B) Offer your last salary (with some expectation of a bump)

The key is that this gets you in the door for consideration without being committal. Once the employer begins to really sell themselves on you, then you have the leverage. Other offers can justify increasing your ask and now they're more hooked on you as the right candidate.

kevinastone··on How the Mig-31 repelled the SR-71 Blackbird from Soviet skies
TLDR: By the 1980s, they had missiles fast enough to shoot one down.
kevinastone··on Equidate Launches A Secondary Market For Early Startup Employees To Sell Shares
It's not actually trading stock or adding shareholders. It's collateralizing the shares, much like you mortgage your home. They simply front you money with a lien against your shares.
kevinastone··on Stephen Hawking: 'There are no black holes'
The TOV Limit for those following at home. It's when the star's gravitational pressure exceeds neutron degeneracy pressure and collapses into a black hole.

http://en.wikipedia.org/wiki/Tolman–Oppenheimer–Volkoff_limi...

kevinastone··on CountUp.js
Why would you set `user-scalable=no` but not re-flow for tablets? I really wish Safari would provide an override for these incorrect viewport declarations.
kevinastone··on The Cap Trap
I'd suggest the title: Cap Trap drives to the root problem. The fact that the convertible note cap has become the pseudo-pricing of the round, creates considerable contention between angel investors and founder, which compromises the major benefit of convertible notes to raise money quickly. Obviously ego and/or misunderstanding can acerbate this issue, but ultimately, it's the focus on the cap number that introduces many of the complications of a priced round.
kevinastone··on We Should Ditch Nginx
+1 on that eventual blog post.
kevinastone··on FlyKly Smart Wheel
Their "Find my iPhone" style tracking and alerting presumably.
kevinastone··on Setup.py vs requirements.txt
Are you suggesting using `pip freeze > requirements.txt` as some kind of Gemfile.lock compared to setup.py#install_requires as the standard Gemfile?
kevinastone··on Github is Down
They say that for every outage.
kevinastone··on GitHub down 2+ hours (and counting)
Maybe its more localized. I haven't been able to push/pull since around 2pm PST.
kevinastone··on GitHub down 2+ hours (and counting)
GitHub won't accept any code push or pulls while they're fixing their file servers.

I know one of the benefits of DVCSs is that these outages don't immediately affect your work, but GitHub seems to have a several hour outage more than once a month. Why can't they keep their systems available?

kevinastone··on Django-inplaceedit: Edit on the fly
I would think `is_staff` makes more logical sense.
kevinastone··on Everything you need to understand to start with AngularJS
That security concern is nonsense. Use {% verbatim %} as noted below for angular templates (there's plenty of backports for Django <1.5). I have django templates fill in runtime parameters (csrf_tokens, etc) all the time.
kevinastone··on Don't Spam Your Users: Batch Notifications for Rails
My similar implementation offers these emailing options (every, digest or none). The nice thing about this approach is you can just add logic in the post_commit handler to route the notifications appropriately (instant email, digest queue or /dev/null appropriately based on user preferences)
← PreviousPage 3 of 4Next →