I'm glad it works for you guys, but I'm often irritated by these preachy posts which seem to say that developers should be treated as delicate flowers and suggest all manner of strategies to preserve their preferred ways of working, many of which, if you actually applied them to the real world, would result in clients saying, "Wow, these guys are hard to work with, can we please find someone else?"
I would go further than saying this isn't really very revolutionary, rather it describes a fairly normal working environment.
Of course, in those environments, developers cannot say "no", they can either keep working under whatever unreasonable constraints they have, or quit. (I've found this a lot more common in companies where the main focus isn't software development)
I agree it's not very revolutionary, but I still find it useful to read about how other people organize their teams and how it works, and very especially what tools they use (Slack and a few others are on my to-try list).
Exactly. Totally flies in the face of saying "how high" when someone says "jump".
Not only that but a similar attitude of some old timers in a business that I was in (right out of college) was what allowed me to get their clients.
We live in a world where people want instant gratification and answers to their questions. While there may be cases where timing doesn't matter when you are dealing with sales and closing deals and keeping away the competition I have always found the early bird gets the worm. And sometimes you get the deal just by showing up because the other party is to busy to service the account.
As a company we really want to spend time sharing what we learn.
This is one of the first posts we've written, so we'll try to improve in the future :)
I too am tired of people discovering this "blog" thing.
> How do I tell my clients that I only do meetings on Thursdays?
I generally do 10-15 customer meetings per week. When I get a meeting request, I ask if they're available on the following Tuesday or Thursday with a 90% hit rate. Meetings are almost always not urgent, so fitting them into Tues and Thurs, instead of spreading them randomly througout the week, has worked really well for me.
> How in the world does [doing 1 thing per day] work? [...] surely your goal should be actually doing a reasonable amount of things
In the context of software development, doing a large number of things usually doesn't push the product forward as much as doing 1 big 2-4 hour project.
Personally I still have 30+ things on my TODO list at any given time, but I try to center my days around getting one "big" thing done, and fill the rest of the day with smaller day-to-day tasks.