Four years ago I wrote about a great essay that Paul Graham had published way back in 2009 about two different kinds of schedules: the manager's schedule and the maker's schedule. Put differently, the manager's schedule is one of command. It is for bosses to drop in for 15, 30, or 60 minutes at a time, say a bunch of things, and then jump to the next meeting.
The maker's schedule, on the other hand, is one of doing, whether that be programming or working on an excel model. And the reality is that you can't make or do much with only 15, 30, or 60 minutes. To make anything of real substance you need longer uninterrupted blocks of time. You need time to get into the zone.
I'm reminded of this dichotomy now, more than ever, because of video conferencing. It has never been easier to overload a calendar with meetings. Consequently, it has never been easier to screw up a maker's schedule.
I have started to meet with developers for my new book – becoming a real estate developer – and I can’t begin to tell you how impressive and inspiring it is to learn about their stories.
It’s easy to look at someone who is successful and feel overwhelmed by everything they’ve accomplished. But nobody starts at the top of their game (unless maybe they were born with a silver spoon in their mouth). Usually there’s a backstory of sweat and struggle that rarely gets told. As the saying goes: success has many fathers, but failure is an orphan.
But those are exactly the kinds of things I hope to uncover with this little project. I am less interested in the successes and more interested in the early decisions, struggles, and thoughts that went into making those successes even possible.
And one thing I’ve noticed is a tendency to just go for it. In fact, when I asked one developer if he had any advice for young aspiring developers, he said: just fucking do it.
As soon as he said this I couldn’t help but think of my elementary school English teacher who used always tell us the same thing – minus the expletive – whenever we’d ask him something such as, how long should this paper be, should we focus on this or that, and so on. He would always say: What does Nike say? Just do it. No buts. Just do it.
At the time, I obviously didn’t give this much thought. But the fact of the matter is there’s so much value in doing. And it’s easy to overthink at the expense of doing. What he was teaching us was to have confidence in ourselves that we would figure it out along the way.
The reason there appears to be a lot of interest in “how to be a real estate developer” is because there isn’t really a set path. You don’t go to school, apprentice for a year under the wing of a developer and then, boom, you’re a developer.
Most developers have carved their own paths. They just did it.
Growing up, I had one of the best English teachers around. He was the kind of English teacher who would dim the lights, light incense and play Bob Marley in the midst of class. He had also previously taught in Jamaica, which might help to explain this behaviour.
I had him as a teacher in both elementary school and in high school. All in all, he probably taught me 3 or 4 years of English–excluding the fact that he was also the coach of my high school basketball team (which I was on).
But more than just being a cool guy, he drilled a number of important takeaways and life lessons into his students. Still to do this day I remember and try and follow them. And I know that many of my classmates do the same. So today, I’d like to share 3 of them with you.
1. Don’t say umm
We all say “umm” from time to time to fill in our sentences when we can’t think fast enough or we don’t know what to say, but it sounds awful. It also makes you sound indecisive and less clear about the message you’re trying to get across.
If we ever said “umm” in class he would make us repeat our sentence again and again until we said it without saying “umm.” He would literally stand there saying: “Start again. Start again. Start again.”
Similarly, he wouldn’t allow us to say “like”, unless we were using it to truly express that something had the same qualities as something else. But if you just said like for no reason, he would say: “Is it like that or is it that?” Again, it’s about being clear and precise in your language.