[scarecrowbob]

So here's a question that I continually ask myself as I work at my remote, salaried 6-hour-a-day developer job that I've been doing for the last year:

how do I know how much work is enough?

If I gauge by productivity, that's cool... I'll just be really fast and get my stuff done and then go play banjo or whatever.

But then when folks hand me a crufty WordPress site that is misbehaving and it could be anything between "visit the route that resets the route cache" and "debug three or four broken and unfamiliar JavaScript libraries and their interaction with terrible PHP code" there is a problem, because to my boss those could be the same amount of work.

When I am doing green field work, or working with very nice, clean technology that I understand well, it's easy enough for me to have expectations about how much to do, even (or perhaps especially) when I am dealing with a large, multi-month effort where there is a lot of fluidity in hitting specific goals.

But how do I say "oh, I worked enough today" if I don't have an hourly commitment? I agreed to a certain period of my time specifically because sometimes I look up and have worked 8-10 hours.

I'm the only programmer on my team, by the way, so there aren't a lot of metrics we can pull from about performance.

This is a real question I think about a lot, and I'd be happy for an answer: how do you set a workload expectation with no reference to how much effort or time I am expending when time estimation is difficult?

[kcorbitt]

Absolutely. I don't fully understand workplace cultures (including my own) that claim to care more about "getting your work done" than "hours in a chair." The problem is that output is in many cases a very crude measure of effort. And not just because some people are vastly more productive than others, but also because it's often the case that when reading a bug report, you don't know if the fix will take 3 or 3000 lines of code until it's actually done.

Of course, over time your output averages out, and if you work about as hard as someone at about your skill level you'll have similar outcomes. This works ok for yardsticking at engineer-heavy organizations. Doesn't solve the problem for a solo developer like you though.

[pkaye]

Good points... It all depends on who sets the milestones for "getting the work done".

If a sales guy commit more features to the customers than reasonable, do you need to put in more hours to "getting the work done"? Does he need to stick around late till your are done to penalize him also? If a sales guy doesn't make a sale as aniticipated does he need to stick around until he makes a sale and "gets his work done"?

[JamesBarney]

And even worse you don't know if the 3 or 3000 line fix will take more time.

[arvinsim]

> The problem is that output is in many cases a very crude measure of effort.

Unfortunately, businesses and companies are mostly concerned about output. Does the line below sound familiar?

> I don't care how you do it. Just get it done.

[rogerdpack]

Did you negotiate the 6-hour-day up front or just...uh...you know...work 6 hours, as it were?

[scarecrowbob]

I started out as an hourly contractor doing projects for a really good salesperson, and then she bought all my time that I cared to sell (about 30 hours a week), and then we formalized it as a w2 position about 10 months ago.

It's a very small company with doing web dev projects; there's only the boss (who pretty much just does sales), the "Design Dept. Head" out in SF, the "Chief Project Manager" in Az, and me (I'm an hour outside of Austin), plus a couple of off and on freelancers.

TBH, the expectation is mostly that "we get stuff done"; for example I had to meet with a client for a sub-contracted NSF gig on our NYE holiday. Or I have had to fix broken stuff in the middle of the night/ work late to make some magic happen occasionally. That has been rare enough so that, like the once or twice a year I have to travel, it's novel and kind of fun.

But between the limited sales pipeline, higher-margin clientele, and being fairly efficient the formal office hours that I agreed to are easy to maintain.

I play a lot of music, and I suspect that it's very much like being in a successful band would be like (I wouldn't know specifically what that is like, though, I only gig on the weekends at bars).

[dkonofalski]

> and then go play banjo or whatever.

I'm taking this example. This is mine now. Thanks. :)