HNHacker News
TopNewBestAskShowJobs

jwarkentin

131 karma · joined January 22, 2013

submissionscomments
jwarkentin··on Could a Pending Amazon Patent Doom Coin’s All-in-One Payment Card?
I think you're thinking of the wrong problem. The basic problem, of course, is simply that we want an easy way to pay for things without having to carry a lot of cards around. Google Wallet was an attempt to solve that, but it's got some flaws.

First off, everyone has a card reader, but not everyone accepts the NFC based payment method with Google Wallet from the phone. At the relatively few places that accept it, when I've tried it's been pretty finicky and only worked a few times. So, naturally, I was pretty excited about the idea of a Google Wallet card when I first heard about that because it was a card I could actually swipe. It would be accepted everywhere and not be finicky.

Well, as it turns out that only pulls funds from your Wallet balance, not your selected default payment method. I told several people, even long before the Wallet card, that I really wanted a Google Wallet card that could charge any one of my payment methods, but that had a screen on it so I could select which one to use.

So like I said, it seems like an obvious solution. If you want to have a payment method that works everywhere (including legacy payment systems), isn't finicky, and can replace all of your other cards then you obviously need a card with a barcode that has a screen and a way to select the payment method (or allows you to select the method on your phone before swiping - which is what I'd hoped the Wallet card would do since it's a virtual card).

As for your accusation of protesting based on who is patenting, I really don't give a crap. I'm opposed to most, if not all patents, but especially obvious ones like this because they stifle innovation. They're used for evil SO much more than they're used for good. As for Amazon specifically, I don't really have any major problems with them. I generally like them. I just hope they don't use this patent for evil because that would anger me enough to abandon them.

jwarkentin··on Could a Pending Amazon Patent Doom Coin’s All-in-One Payment Card?
This is an example of something that shouldn't be patented. I had this idea about half a year ago and thought it was unique until I saw coin. Then I got excited that someone actually made it and I bought one.

If everyone's coming up with this idea now (it's the obvious solution to an obvious problem) then it isn't even evolutionary enough to deserve a patent.

jwarkentin··on Anonymous hacks MIT website on anniversary of Aaron Swartz suicide
The ridiculous part is trying to slap him with 35 years in prison (worse than murder in many cases) when the victim, JSTOR, chose not to even press charges.
jwarkentin··on SSL/TLS analysis of the Internet's top 1,000,000 websites
It seems to me that browsers ought to pop up a security warning for any site that tries to use an insecure cipher like RC4 or 3DES so the user is at least aware. I say that simply because it's possible that even if a site supports something more secure, what's to stop a MITM from reporting differently during the protocol negotiation?
jwarkentin··on Anonymous hacks MIT website on anniversary of Aaron Swartz suicide
Seems like we should be focusing more attention on the Department of Justice. They were the ones really pressing the ridiculous charges. MIT definitely shares some blame, but the DoJ is where we really need to see some reform.
jwarkentin··on Engineer-to-Engineer Recruiting
I get a ton of recruiter spam. For me I think it's a combination of having a LinkedIn profile, an active Github and Stack Overflow profile, having a blog, and having them all linked together. Unfortunately, I'm now at a place where it's mostly just a nuisance because the positions they have to offer are generally at worse companies with worse management, environments, pay, and benefits. It's generally not worth my time to respond. If I do respond it's not going to be with my resume, but instead with a list of questions they need to answer to decide if it's worthwhile.
jwarkentin··on RESTful Realtime
In the realtime stuff I've built I publish update notifications on different channels to Redis whenever data is saved from a model. Then I have a Node.js server that listens for those update notifications, fetches the new update once, and then pushes it out to all connected clients. This reduces a LOT of load on the server because if we have 300 clients connected, it still results in only one request to the server to fetch the new data and update all clients.

Even if you don't want to use a pub/sub and publish instant notifications when data is updated you could implement polling in a Node.js server and just have all the clients connect to it with Socket.io. Then when the Node.js server sees an update in the data it can push it out to all the clients.

This strategy also has the advantage that you don't have to change anything on the client if you decide to switch to a pub/sub in the future for more real time updates.

jwarkentin··on RESTful Realtime
Or make life real simple and just use Socket.io
jwarkentin··on RESTful Realtime
That's basically what I was going to say. I've developed a realtime system for my company that uses a REST API on the backend, but we use websockets to push updates to the clients in realtime. It's so much faster (no polling and no overhead of establishing new connections). When there's an update we hit the API once to fetch the new data and then push it out to all clients subscribed to the given data set which massively reduces load on the server.
jwarkentin··on Ask HN: Is it possible to get a tech job without a degree?
I think it comes down largely to what you know, and if you can show it. I don't have a degree and I have a great job. I also get contacted usually multiple times a week about jobs. I maintain some open source projects, I have an active SO profile, Github profile, blog and I keep LinkedIn up-to-date. That seems to be enough. Regardless of whether you have a degree or not those are all valuable things that can show what you know and help your career a lot.

I just don't think you need a degree if you know what you're doing.

jwarkentin··on I will not hack on your codebase for free in an interview
I absolutely agree. I think that it's important to first establish interest and weed out candidates that are obviously unqualified. You can figure a lot of that out in a short amount of time. While some of your best candidates may already be employed and thus only casually interested initially, at least for someone like myself that interest could increase significantly after sitting down and chatting about the company and projects for a bit. If I were to then become really interested it could be worth spending a lot more time in an interview process.

Personally I don't think that a company will learn much more from 8 hours or more than they could learn in 3-4 hours tops though. I think it's overkill in most situations.

jwarkentin··on I will not hack on your codebase for free in an interview
I disagree. While I have an awesome job, I'm always casually open to new opportunities. That doesn't mean that I'm willing to sacrifice a day of my time for an opportunity which I know very little about before making the sacrifice. If I'm out of work and/or desperate, then yes, the potential benefit outweighs the cost/risk. Since I'm not by any means desperate or looking, asking me to take the risk/make the sacrifice with no compensation is more than the possibility of some yet unknown potential gain.

That isn't any logical grounds to assume I wouldn't be a good fit. That just means the ROI tells me it's not worth my time. Without seeing significant potential reward and a reasonable possibility of getting the job, and actually wanting it, there is no way I'd go in for more than a couple hours of coding without compensation.

jwarkentin··on I will not hack on your codebase for free in an interview
Sure, your company invests the time of many people in the process. But you do it because you've determined that overall it adds value to have another employee. It's worth the cost. Hopefully, most things that they would otherwise be doing if not searching for a candidate would also add or maintain value of some sort (whether monetary or not). So really, it's just another value adding task that must be done. So we've established that in the end you gain more value by having that employee than it costs to hire them.

From the employee perspective they may or may not actually be looking for a job, versus casually interested in all possibilities (like me). They also may or may not already have a job, in which case they'll have to take the day off to go through such an extensive interview, giving away work and potentially IP for free.

If I have a job and/or I'm not really desperate, then the cost of the interview may be greater to me than what I see as the potential gain. Especially when compared with the other possibilities out there. There are a lot of companies that will pay for any significant amount of time spent coding for an interview. Why would I waste my time with a company that doesn't value my time (esp. taking it off work), the work they're asking me to do, or potentially the IP I give them (e.g. if I come up with a new way of looking at a problem or a new solution they haven't thought of during the code interview).

A couple hours is a reasonable sacrifice, IMO, but may depend on each candidates situation. If I as asked to spend more than 2 hours coding, I would ask for compensation or turn down the interview.

jwarkentin··on I will not hack on your codebase for free in an interview
On the other hand, many people already have jobs are were contacted by the company looking for a candidate. I would have to take a day off work to go in for a full day interview, so some compensation is also reasonable.
jwarkentin··on I will not hack on your codebase for free in an interview
You're missing the big picture. If all it was doing was slowing down a developer for a day then the company wouldn't bother interviewing anyone that way because all it is just a cost and there is no benefit to the company. However, the company does that because they decided there is a positive value, an actual benefit to hiring a needed developer and knowing that they can do the job.

There is always a cost to hiring. When a company decides that the value of having that dev is greater than the cost of hiring them, then it makes sense to hire someone. It may not be an immediate monetary value, but the company decided they needed the dev. So they decided that slowing down a developer for a day to work with a candidate _is_ beneficial to the company.

Plus, like others have said, it really sounds like he was being asked to work on something that was adding value. If a company has decided a particular bug or feature is worth prioritizing then it obviously has value. That means that if a potential candidate comes in and does it, they are adding value (though whether the net value is positive or negative varies case by case).

jwarkentin··on I will not hack on your codebase for free in an interview
It is common practice when hiring a developer to pay them for time spent programming if it's any significant amount. I've never heard of paying for all the time spent in the interview, or for time spent if it's just something small and simple to get a quick feel for skill. But if they're asking for more than an hour or two or if they're asking for new features added to their existing code base, it's completely fair to ask for compensation.
jwarkentin··on I will not hack on your codebase for free in an interview
A first interview should never be sitting down with code. That's a waste of everyone's time. The first interview should probably happen over the phone, though it could be in person. There are too many people out there looking for programming jobs that can't pass the idiot test. In the last interview I went on the first thing they had me do was write a for loop. They explained that, while it may sound stupid, too many of the people that came in couldn't even do that. Where I work right now, we have been trying to hire for a PHP job, but most of the people they've brought in don't know basic things like what an associative array is.

Assuming you've at least weeded out the many people that are a waste of time and money, then I think it's fair to pay anyone you bring in a reasonable rate for a couple hours of work.

Also, with most companies that contact me, I don't really know if I'm interested at all until I go in and talk to them. Don't presume that all candidates are interested in working there. It's hard to know until you know more about what they do, their processes, the culture, the type of people you will be working with and what the management is like.

jwarkentin··on “MongoDB is dead. Long live Postgresql”
Some things to consider:

http://www.sarahmei.com/blog/2013/11/11/why-you-should-never...

jwarkentin··on What 4chan thinks of HN
I don't know that you can consider healthcare.gov an existing service. I don't know anyone who's actually been able to get service there. It's more in the idea/alpha phase. Health Sherpa ripped off an existing idea and made a improved functioning (bootstrap) version.
jwarkentin··on StackEdit: A free, open-source Markdown editor based on PageDown
This is awesome! I've wanted something exactly like this for ages for publishing to my blog! You are my hero - at least for the night :p
jwarkentin··on Tessel: The end of web development as we know it
I'm curious if there's any advantage to this over the Espruino which actually runs JavaScript.
jwarkentin··on Federal Government Begins First Shutdown In 17 Years
Whoops, that's what I meant to say. Good catch!
jwarkentin··on Federal Government Begins First Shutdown In 17 Years
Haha, exactly what I was thinking. Like the part where the IRS stops auditing...
jwarkentin··on Federal Government Begins First Shutdown In 17 Years
I think 3 months is a bit long to wait, but I'd be all for a new election.
jwarkentin··on Federal Government Begins First Shutdown In 17 Years
My thoughts exactly. People already make fun of our dysfunctional government. It's just adding fuel to the fire. Then again, I make fun of it too... :)
jwarkentin··on Why Phonebloks Will Never Happen
I never figured it would be done in the way it's presented. I like it because there's a lot of potential. And if a lot of smart hardware engineers start working on it, we can develop something way cooler. I want to see companies recognize that people like this idea and start moving in that direction. I would love for this to spark pressure that moves us away from monolithic solutions and towards something more modular.
jwarkentin··on Provo-Orem area ranked 11th for high-tech startups
I'm in Herriman. I almost bought a house in Lehi :) I currently commute to Downtown Salt Lake for work though. It's about a 30-35 minute drive for me in either direction.
jwarkentin··on Provo-Orem area ranked 11th for high-tech startups
As a developer here I'm constantly getting contacted by recruiters. I live half way between Salt Lake and Provo so I can go either direction, but there definitely is a lot going on in the tech industry here.
jwarkentin··on Tox: secure messaging for everyone
Many people make plans, few carry them out. You posted that March 21, 2012. Now, 1 year and 4 months later, someone apparently independently created a similar logo and is actually doing something with it, not just planning to do so. If you do something with it as well then great! I don't see what the big deal is.
jwarkentin··on Show HN: A Search Engine for Developers, Marketers, Web Designers, and Hackers
I think charging for search in general is going to be their downfall. There are so many search engines these days that without bringing something truly revolutionary to the table, you'll be hard pressed to get much notice even offering it for free. Charging for it? Not a chance. There are other ways to monetize search.
← PreviousPage 2 of 3Next →