glimcat

Generously: Nothing at all, they just wanted to grab hits.

Less so: They figured that any products which primarily target women must be fundamentally similar.

You left off the difficulty multiplier, namely: "which can be operated and maintained by a typical consumer."

Headline actually understates it. It sounds like the real deal was less microtargeted than the headline implies: according to the article, they banned "requiring or requesting employees or job applicants to disclose electronic passwords, such as for social media sites."

The value of brand awareness is also inversely proportionate to how much brand awareness you already have. When you're Facebook, more brand awareness may not be the primary motivator.

Larger projects: for each, does the code available or the language features make it a substantially smaller project than it would be otherwise? Also, what gives the lowest difficulty to maintain?

Google Street Map cars, then.

You want to pick nits over Google being able to ship?

Usability is problematic from a user's perspective. It does nothing new, but it increases the complication of completing the transaction.

Also, since Google has customer service approaching nonexistent, who are you going to call if something goes wrong with the transaction or if there's fraud?

Spend some time working through this if you want to learn Rails.

http://ruby.railstutorial.org/ruby-on-rails-tutorial-book?ve...

Also, bugger recruiters, what do they know? Talking to a recruiter usually means there are at least two people between you and anyone actually on the product team. Real experience in the trenches really getting things done is valuable. You can always learn another language, framework, library, whatever you need.

Python 2.x is the one that most people use.

Python 3 is a fork with broken compatibility and poor adoption.

I'd be happy just seeing prominent and clear icons for major threat types, e.g. access to personal data, elevated device access, and so forth. Make them large and suitably threatening. It wouldn't completely solve the problem, but it could take back a lot of ground.

It's not not just Chrome.

A better behavior would be selective approval. Extension asks for permissions for X, Y, and Z. You allow X and Z but deny Y. Any features affected fall back to an alternate state or are disabled. User is given clear access to control the permission states and clear feedback as to which permissions affect which features. Information about feature dependencies is available prior to install, particularly if they are arbitrary dependencies like "send us all your personal info or the software does nothing."

Is this going to happen? Probably not. Application-level firewalls help somewhat, in some cases, for expert users. Sometimes "use different software" helps, but there are many cases where that's not viable.

In the sense that evolution drives speciation, yes.

Which is to say, a random walk based strictly on local optimization conditions, which produces absurd dead-end results at least as often as it produces something of lasting value.

Yes.

The problem is, that's below the care threshold for wide swaths of the audience they're hoping to attract. You're hiring developers? So what, everyone's hiring developers these days.

As a startup, it's also unlikely that you can win a bidding war, so avoid that dimension. Where startups can often succeed is in the "moral payoff" - are you building something I care about and want to be part of? Startups have a giant advantage there compared to a company that needs you to add a new feature to their in-house order fulfillment software.

Unfortunately, you've set that axis to zero if you start going on about "hard problems" and never ever reveal who you are or what you're building.

See also the previous post by the same user which is completely vague, while the current post at least gets as far as "probably some SaaS / iOS app."

http://news.ycombinator.com/item?id=3580917

I wonder that YC doesn't include an hour session on "how to write a job post that your target audience won't classify as spam."

Think about what's needed to bring your product to market. Does your team adequately cover the bases? If you have to hire to fill the gaps, can you find and manage competent people without excessive hand-holding?

Teams come in all shapes and sizes, what's important is that they have a reasonably viable shot of doing what they propose to do.

Isn't that exactly the problem which VC funding claims to address?

Residents tend to be reasonably well clustered in terms of socioeconomic factors, and we know that at least one resident exists for whom this is a reasonable purchase.

If we assume the 3x10^6 sales are all US (false, but good to some order) and estimate the US population at 300x10^6, then the expectation is roughly 1:100 that a random person will order a unit. Conditioning that on socioeconomic factors should yield a reasonably high probability that if you ordered one, so did several of your neighbors.

The article really doesn't say anything more than the headline already did (then gets into "high-entropy random character strings are hard to remember" --> solution: "read xkcd, use passphrases"). Also, the DARPA program is more involved than this implies.

They do link to the DARPA Active Authentication program:

http://www.darpa.mil/Our_Work/I2O/Programs/Active_Authentica...

The thrust of which is that they want a better way to establish that the expected user is in fact the one at the keyboard, including ongoing verification of whether they are still the person at the keyboard.

They'd also be extra happy if it works with existing hardware, so they'd like the answer to be things like analyzing the way the keyboard or mouse is used, or analyzing patterns in how you write (IMO probably more trouble than it's worth!). "Implant RFID chips in the hands of all DOD personnel" is off the menu for the moment.

Roughly, keymaster.js is focused on being small, while shortcut.js has been through a few iterations and is focused on being feature-rich. But they are both fairly small and they have many of the same features.

Links don't work in posts, someone has to reply with it. By etiquette, usually someone other than the submitter.

It's a bit non-intuitive. I think it's intended to cut down on linkback spam.

I've been using shortcut.js for keyboard shortcuts. Works great.

http://www.openjs.com/scripts/events/keyboard_shortcuts/

Problematically, with many lawyer and accountant hours, and generally while buffering outgoing payments until the incoming payment is fully secured. Paypal and ACH seem to be common transfer protocols.

Guns have recoil. Grenades don't.

Also the targeting issues are vastly simplified and they're very effective in swarms.

Vision affords high input bandwidth and loose constraints. The key constraint being, you have to look at the interface.

Other senses afford low input bandwidth and have many constraints. They tend to trump vision only where needing to look at the interface is problematic, or where the data exists in another form (audio) and transcoding it is problematic, or where closed-loop feedback control is needed (tactile feedback & haptics).

Maybe you don't have the data to make that determination.

Maybe fries aren't profitable yet, but you're hoping to make them become so.

Maybe you have to have fries on the menu even though you make more money off soda.

* Many startup acquisitions are speculated or known to be about acquiring the team rather than acquiring the product.

* Consultancies are nominally the experts you call to compensate for gaps in your inside staff.

* You can run a contract with a consultancy first, and consider acquisition only if it goes well and if their people fit well with your people.

If you were aiming for that particular exit strategy, it sounds like it could be much more effective than building a random web / mobile product without a sustainable revenue model beyond "get funding, hope it lasts until someone buys you."

prgmr.com

Yes, but you shouldn't. Also, adapters are a couple bucks on Monoprice.

Also, a "tempermental" PSU may need to be replaced before it does destructive testing of the components connected to it.

It would be interesting to run sentiment analysis on the archives of various online communities to figure out where the likely phase transition point is. Probably a PhD in it for someone.

You realize "go forth and build cool stuff" is, in many domains, about a million times easier than it was even just ten years ago?

A big part of the problem is that fraud prevention is HARD.

Worse, it's prone to expensive scaling laws, and more so if you want to catch edge cases, and much more so if avoiding false positives is critical.

Any PayPal successor which is successful enough to become an interesting target for fraud will have to deal with exactly the same problems, possibly causing service to break down in similar (or equally problematic) ways.