spencerfry

I actually bought it back in 2006-7. I was working on a local reviews site for a few months before working on Carbonmade, which was my last startup before Uncover.

Here's one from a few months ago:

http://spencerfry.com/why-and-when-to-learn-to-program

I wanted to keep the most recent blog post solely focused on Uncover. I'll follow up with more coding posts shortly.

Interesting idea. We'll look into that. Thanks.

Thanks a lot. I'm familiar with Rypple, but I haven't used it to be honest. We're definitely working on something similar, but with a slightly different approach.

We have a feature called Rewards that allow employers to reward employees for going the extra mile. With that feature you can reward one or more employees and tailor the gift and message to them.

Thanks! I actually bought it all the way back in 2006-7 for another project I launched. It was a small local review site I was working on for a few months before beginning to work on Carbonmade.

Thanks, tannerc! We're going to put up a Pricing page. We wanted to release as quickly as possible, so a few pages didn't make the marketing site: Pricing, About, FAQ, Customer Stories, etc. They'll be there shortly, though.

Thank you! That's part of what we believe: "Discounts aren't effective. There's a difference between 'here's a discount' and offering something special."

That's good feedback. Definitely continuing to improve the message.

Thank you!

Thanks for the support. We're trying to solve a similar problem as BetterWorks was, but with a completely different approach. If you're unfamiliar with BetterWorks, you can read more about them here: http://www.crunchbase.com/company/betterworks

Here's a post on learning to code:

http://spencerfry.com/why-and-when-to-learn-to-program

I'll follow up with some more code posts in the future. I wanted to keep the "Introducing Uncover" post to be focused on the startup.

Here's my blog post on our launch: http://spencerfry.com/introducing-uncover

The premise of do what you're good at is great. However, even the non-technical examples listed still require quite a bit of technical knowledge (accounts, management, payment flows, notifications, etc.). The good thing is that these are fairly simple processes nowadays and can be picked up within a few months of studying.

We can hope!

I applaud Danielle for writing this piece, but it should be really obvious to any startup founder. If you're not growing in any important metric: change course. It's not rocket science. The problem with raising money too early is that it's an excuse to flounder for longer. You won't have this issue as a startup if you start off by bootstrapping yourselves.

Totally agree. I should probably clarify that point to say that we looked at both revenue and expenses. This is especially important if you plan to bootstrap for some time as we do.

What kind of bugs have you found?

You can turn it off here:

http://*.disqus.com/admin/settings/?p=discovery

Heroku does a good job of notifying its users.

That's true, but the overall themes apply to most -- if not all -- countries.

I'm not sure the origin exactly, but Googling found that the term supposedly comes from the mid-80s: "Around the mid-80s, the term ‘human resource management’ arrived from the USA."

I don't think either of us are saying that they're unnecessary or useless. We're just saying in 2013, technology can make these processes more efficient as well as better designed.

Those are my feelings exactly. I'm not as familiar with companies over ten employees -- I've never been in an environment any bigger -- but I'm sure that if we're having issues at ten then companies of one hundred, five hundred, and thousand+ are having any even worse time keeping track of everything.

Wasn't meant as an "ego leak" as you say. It was only meant to emphasize that I've been doing this for a long time and had many stops and starts. I was only really able to start learning when I figured out the when and why for me.

We have similar life experiences it seems. I'd suggest putting off all thoughts of managing, promotion and monetization when you're learning to code by building your first project. If that stuff happens. Great. If it doesn't happen, then you'll at least come away with an awesome understanding of programming and then the next time around you can focus on the other stuff. It's a win-win.

This is so true. I've only been programming for around a year, but I now have a much better understanding of what goes on under the hood. In the last few months, I've gone from doing 100% to 20% of the coding as I'm now working with a better developer than myself, but the understanding alone has given me a huge leg up on other CEOs/product people who have no experience programming.

I couldn't disagree more. It's very elitist to say that interested minds shouldn't pursue the field you're in because they're asking the wrong questions. The better and more productive approach would be to educate them by answering their question and at the same time pointing out the preferred way to look at it.

I know when I was first starting out there were obvious cliffs that I confronted when growing as a developer. The first cliff is going from syntax to understanding how to piece syntax together. Then further down the line is learning best practices and how more seasoned developers do things. This is something that you can only learn from practice and by asking questions on sites such as Stack Overflow and your peers. How else are you going to learn?

I agree. I've become a huge user of Intercom. Great app.

Getting an Error 999.

Here's a cached version:

http://webcache.googleusercontent.com/search?q=cache:B4tHkMj...

I wrote all the way back in November, 2009 that three co-founders was better than two. http://spencerfry.com/threes-company I've since changed my thinking that two co-founders is a lot better and that both of those two people should be technical or design.