jagthedrummer

Joined 13 years ago

Karma
85
Submissions
34
Member since
Mar 24
I’m a hard-working, entrepreneurial, full-stack web engineer. I believe in test-driven development, minimum viable products, short iterations, fat models, skinny controllers, version control, feature branches, automated deployment, performance as a feature, 24x7 monitoring, proactive detection of problems, and using the right tool for each job. I engineer scalable solutions to allow infrastructure costs to rise and fall with demand.

http://www.octolabs.com/

View on Hacker News

Recent submissions

Comment · 10 years ago
dalke, I said "some parts of my business" because I run several different business of various types.

Since the book focuses on value pricing for consulting projects it's obviously not applicable to the SaaS that I run.

However it's been fantastic for my software development/architecture consulting.

I recently completed at project for a client where I used the value based approach from the beginning of the sales cycle and very early on identified the real goals that the client had in mind and was able to work with them to identify a dollar amount that they wanted to invest to fix the problem. We agreed on that amount and I went to work. After completing the project my effective hourly rate was around $600/hour, and the client was extremely happy with the results.

(I know you're not a fan of the term "effective hourly rate", but it's the best term I have to talk about that concept since I didn't agree to an actual hourly rate with the client.)

Had I gone with my old process of saying "this is my hourly rate and I'll track hours" it's doubtful that the client would have agreed to $600/hour and I would have made much less on that project.

I don't think Jonathan meant to use "laborer" as a slur of any kind. I think he's trying to get at the distinction between being "a pair of hands" on a project, who is told what to do and how to do it VS being "a brain" on the project who is operating at a higher level of abstraction to identify problems, propose possible solutions, determine which solution is best, etc...

Those are two very different things, and the advice in the book would be MUCH harder to apply if you are filling a "pair of hands" role.

Hope that makes sense and answers your questions.

Comment · 10 years ago
I highly recommend this book. The author, Jonathan Stark, really knows his stuff when it comes to pricing. His advice on value based pricing has changed the way I approach some parts of my business.
Comment · 11 years ago
Thanks!
Comment · 11 years ago
Does anyone know if Foundation addresses the issue of how to handle the migration of existing users from the pre-foundation version of the interface to the post?
Comment · 11 years ago
I'd be interested to hear what you move to, what the set up looks like there, and what you pay for it.
Comment · 11 years ago
Sure, no money has to change hands, BUT if you decided to take the hours that you would spend moving projects away from Heroku, and instead do something productive that creates value for a client you could be spending the same amount of effort, and be making more money than you'll save by switching.
Comment · 11 years ago
Here's an analysis of how these rumored changes will affect apps of various sizes.

http://www.octolabs.com/blogs/octoblog/2015/03/31/analysis-o...

tl;dr : Current paying customers will see a discount of up to 30%. Current freeloaders will have to pay $84/year for functionality equivalent to what they get now.

Anyone who is technical enough to use Heroku effectively can charge AT LEAST $84/hour for their time, meaning that they'd need to move to a new solution in less than an hour to save money. All the hand wringing is very silly.

Comment · 11 years ago
Lemme guess, you're a developer/sysadmin/techie type? :)

This is a tool for people who don't want to be anywhere near a command line.

Comment · 11 years ago
Hmm... I hadn't considered that view before, but I can see where you're coming from. The intention (for me) definitely isn't to extract extra money. Rather I'm hoping to provide something that provides enough value that it's a core part of my customers workflow, and worth using every month. I honestly hadn't given much (any?) thought to trying to do one-off documents until you suggested it. I'll definitely be mulling it over.
Comment · 11 years ago
Thanks for the recommendation!

Nope, edits do not count towards the total. You can make as many revisions as you want to a given document. At this point there's nothing to stop someone from doing exactly what you describe. I'm mainly counting on attracting customers that value their time enough that they'd find it silly to expend time and effort gaming that particular system.

Comment · 11 years ago
I think it depends on what sort of rate you're able to charge as a consultant/freelancer. If you're anywhere near $100/hour (or more) you could very easily waste more time/money by trying to do it yourself.
Comment · 11 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton