saturdayplace

I think it's a useful bit of feedback.

Why would one prefer a Deleware LLC over one in their home state?

I just went through a process like this as a candidate. I was emailed a problem description and told, "Please send us the code that solves this problem. Do so at your leisure, and please don't spend more than x hours on it." This meant I got to use my own setup, and didn't feel as though I was required to come up with the "perfect" solution.

When you think about it, it's odd that most programmers aren't interviewed this way. As a firm, the most important question I want answered is "Can the candidate do the job?" There are obviously other important considerations, but that's numero uno. And the best way to tell whether the candidate can do the job is to ask them for a small sample to prove it.

I'm 100% certain I've been passed over for positions at other places because the hiring process isn't generally designed to answer that question accurately. It's something I want to keep in mind for when I'm on the other side of the table.

A minimum viable feature, nice. Interesting way to test out whether a new feature is needed or not. Then you pave the cow paths. I love this idea.

You can read about tptacek's company's process here: http://matasano.com/careers/. It really does seem like a good way to learn whether a candidate will be able to perform the job.

The gym misspelled your name and your bank told them off? I'd love for some amount of the infamous Japanese formality to become more commonplace here...

Those last two sentences might be worth appending to the guideline </2¢>

I have no experience, but here's my reasoning:

At the moment you don't have a lot of traffic, so you likely don't have a lot of users, and you don't really know if you have something they'll pay for. You don't really know what problems they experience using your app. You don't really know where else in the process they might fall out of the funnel. Putting the CC requirement at the beginning will even further restrict the flow of users through your funnel and make it harder for you to learn where your stuff is broken.

When you do have traffic, A/B test to find out which one works better for you BTW: there is likely more than one axis with which you'd measure what is "better". You'll have to decide for yourself what those are. Is it better than you have less tire-kickers and more seriously committed users? Is it better to have more people in the funnel in total so you can optimize the trial experience? Is it better to have pre-authorized the credit card and remind them that you're going to start charging them tomorrow if they don't cancel their account?

The difference, if anyone's still playing along, is what action the device takes. An IDS (detection system) is a monitoring and alerting device; traffic still gets through. An IPS (prevention system) drops the flagged traffic.

My point is that the timing doesn't matter as much as you probably think it does.

The single announcement you make isn't statistically likely to make a difference in your product's success. You're better off just getting something out the door and iterating based on actual user feedback.

"The best time to plant a tree is 20 years ago. The second-best time is now." - An old proverb

Instead of posting a comment like this, it's generally better just to upvote the comment you're agreeing with. The mods are trying to optimize the signal:noise, and there's not much signal in a two-character comment.

The downvotes are unwarranted, but my guess is: it seems like you're claiming that no one in your cohort watches sports based on your anectdata. A claim which is likely out of touch with reality. I upvoted to hopefully even out your score.

Would you mind talking about your reasons for switching from ExtJS to Backbone?

The offensive tagline (and the site's author acknowledges its offensive nature) seems like a mistake. Why alienate 50% of your audience with the first thing they're going to read?

Edit: The author has changed the tagline, but for posterity it said something along the lines of: "Want to know what boobs look like?" With a subheading along the lines of "You might have been offended, but you're still reading..."

"The best time to plant a tree was twenty years ago. The second best time is now." - Chinese proverb.

"Don't end the week with nothing" - Patio11 https://training.kalzumeus.com/newsletters/archive/do-not-en...

Start building something you can sell. It could be a book, an app, a SaaS. You might not (probability won't) get it to +$15k this year. That shouldn't stop you from beginning. If you make something thst people are willing to pay for, you should be able to EVENTUALLY get to +$15k (and more!)

This mindset baffles me. You're entitled to Game of Thrones, and are justified in pirating it because you don't agree with the terms under which it's made available?

I agree with the thrust of your comment, but it would have been more civil without the first sentence.

I wish the title of this article was more inline with its thesis, which is found further down:

> modern web design has much more in common with product and industrial design than it has with print or graphic design.

His examples of industrial design flaws that look snazzy are bang on, and replicate problems often found in web designs. You gotta USE a thing to know if it's designed well. The Design of Every Day Things[1] should really be required reading for designers charged with designing for the web.

One of the best ways of knowing whether your design is effective is to watch people use it. The assumptions you made about how your audience will use your design will likely be blown away, and watching them try to accomplish the site's goal will lead you towards designs that help them do that more effectively.

[1] http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...

You mention remote work, but the listing on your site explicitly says the candidate must be willing to relocate.

You mention that you're hiring remote, but the positions on your website list a specific location, and the front-end Dev gig isn't listed at all. is this an HN-specific posting?

An introductory tutorial about web development. The plan is to assume the reader has no prior knowledge, start at the basics, and hopefully walk all the way up through building a dynamic web application. It's only just started, http://trevorhunsaker.com

Thanks for the recommendations, I'll be sure to check them out.

Thanks for the feedback! I'll make sure to review for improper simplifications.

I recently decided to write from some tutorials[1] (maybe eventually a book) that assumes zero knowledge and works its way up. I'd like to eventually go all the way up through SQL, basic httpd administation, etc. It's a long row to hoe but I think it may be valuable.

[1] http://trevorhunsaker.com/

It's redditgifts.com. Doesn't look like they're hiring for DevOps at the moment, but they are looking for devs (among other things): http://redditgifts.com/jobs/

Did we really just make an "In Soviet Russia" joke? That was appropriate? Man, I love this place.

If this comment shows up hereafter on every "developers need passion" and hiring thread, I'll up vote it. every. single. time. Alternately, a blog post expanding on the thesis, if we could draft you to write it...

At one point I had an idea for a product that makes it easy for users to do what you're talking about here. Started doubting I could make money off it when LinkedIn gets most of the way there for free (for most people anyway).

Every once in a while I think about spinning that project back up...

Seems like an argument in favor of a bootstrapped companies which intentionally keep costs low and intend to go for slow growth instead of a spectacular flameout. Because infrastructure costs have come down so much, it now feels like companies are more likely to remain viable as bootstrapped concerns than shoot-for-the-moon operations.