249 karma · joined March 25, 2009
I agree that we could do better at communicating progress and more about the process - I think this is one of the major things we need to work on.
We're not thinking about charging for it right now, it's just a proof of concept to answer the question "Can software make someone more creative"?
We're not worried about people leaving and applying the skills elsewhere, since what we've seen in practice is people who've paid thousands of dollars to learn these skills revert to their old habits once real problems pop up.
Thanks a lot for giving it a shot, and for your feedback!
ALSO, I'm sure you can hire someone on craigslist to give your work a second read for gramatical mistakes, if that's really a blind spot you care about.
But I worry, are you even trying to get better? It sounds like you've accepted your current skill level as a fixed balance that can't improve, when that's probably not the case.
But I think you need to pay attention to what others are saying. If you can't get users to complete a series of tasks to get to your value proposition, either the (expected) value you're offering is too low, or the expected probability of getting that value is too low.
In other words, with a high enough value proposition, you should theoretically be able to get someone to do something EXTREMELY difficult.
1) they're risk averse and want to know what pricing they're signing up for (pay-per-use is often much more difficult to figure out what you'll wind up paying in the end)
2) most businesses operate within known budgets, and introducing new software on a pay-per-use basis may hurt their ability to accurately plan those budgets.
I see your argument that slower page loads leads to less engagement and higher bounce rates, and I'm somewhat skeptical - how do you know that your data isn't saying that more engaging websites are faster because they're more engaging?
If being engaging is correlated with delivering more value, they're likely more profitable and more able to invest in higher quality engineering & infrastructure than other sites. This would likely lead to decreased load times. In other words, how do you know the cause from the effect?
I think the only way to make the argument you're trying to make is to compare each website with itself when loaded slower.
What I'm pointing out is a fundamental problem with coding problems.
FizzBuzz is a relatively simple problem to solve, so if fizzbuzz fails as a test for coding ability, then it's fairly likely that all coding problems fail.
There's are probably better metrics (faster, more uniform, etc) that you could use to figure out how good a coder is.
For example, one thing I've noticed is that I'm fairly aware of the skill levels of everyone I've ever worked with. I think it might be interesting to see how peers rate each other (A players can tell A players, and so on)- maybe that would be the metric that's most useful. All I know is that FizzBuzz probably isn't it.
One last thing I need to add: the people who are dramatically more productive coders are not always dramatically more productive because they code faster or better. It's often because they enact/enable processes that amplify the other developers. (e.g. the developer who pushes the company to have a hackathon, or the dev who creates machine images preconfigured for deploying test and dev builds).
The big difference between the two metaphors is that mine has direct impact on your personal life and negative consequences are gonna be seen as your fault, while yours is a company threat - fixing it will get you seen as a hero, not a disgraced villain.
But if you take a second and think about it, how the hell could these same people who fail fizzbuzz write production code in previous companies? Are you really saying that you believe that fizzbuzz is more complicated/difficult than their previous work?
As someone who's run lab experiments and who's seen a bunch of surprising results, trust me when I say that shocking results usually mean that you're running a test that you don't understand.
In this case, you're probably testing for a host of things that have nothing to do with day-to-day engineer performance.
Sell pain killers to people in pain.
I would first figure out the size of the market, then pick a price point (informed by the size of the market + the pain solved by your solution), then a marketing strategy (target either building management or individuals).
While most people on HN are telling you to market to the apartment complexes, I think you might want to market towards individuals, since they are the ones who feel the pain that you alleviate. You can target apartment complexes if you alleviate some pain that they have (maybe having your system is something they can include in marketing materials, which will get them more occupants/better occupancy).
The best thing about targeting individuals is that you may be able to get them to market for you (see dropbox), and that they will cross pollinate your solution to new apartment complexes when they move.
Separately, there are several reasons why people read tons of news articles they don't really care about. In general, they fall within rewards of the self (desire for mastery, completion, etc). For more info, check out http://www.nirandfar.com/ and pay attention to his explanations of the different types of random rewards that drive behavior.