Tag: reading

Categories
Email List Faith Personal Reading & Inspiration

“The future is bi-vocational”

This post is my reflection and notes on the book “The Future is Bi-vocational” by Andrew Hamilton (Hamo), a Perth pastor and small business owner / reticulation guy arguing that churches should start shifting away from assuming “full time pastors” is the right way to lead a church community, and arguing that people who can lead churches might have a lot to benefit from having a different non-church job as well. It’s an easy read, well written, full of stories from his decades of experience. The target audience seems to be existing full-time pastors, or students studying to work in church, but if like me you already have a different career but sense a pull to contribute to your church community in a way that’s slightly more than just volunteering… it’s still a great read – convincing and inspiring. Available on Amazon, or probably local Christian bookstores if you’re in Australia.

Before I share my notes and takeaways, here’s a reflection on where I’m at, and what I had in mind as I started reading.

I was only five or six years old the first time I had a sense that when I was a grown up I’d likely do pastoral work, serving and leading a church community.

That sense stayed with me all through school, and into university. Though I chose to study Multimedia Design rather than go to a bible college or seminary, I still kind of assumed that ultimately it was just filling in time until some kind of a church role. By the time I was in uni I was volunteering a lot, leading groups the size of a small church, sometimes even preaching. And when I was doing those things there was a grace to it: things flowed, there was wind in the sails, there was energy in the room.

Of course part of it was some natural talent, some hard work, some early-adulthood energy. But there was also something more than that, beyond what you would expect from natural talent or effort… something undeserved. A grace.

I was so sure I’d end up working in church that I almost turned down my first software engineering job. I’m glad I didn’t.

I was newly married and Anna was sick, I’d become the sole income earner, and I didn’t want to take the job because I thought I was likely to get one at church within a few months. But I felt a sense that God was saying to me: “this is me taking care of you”. So I took the job. Software jobs pay a lot better than church jobs, which helped. A few months later the church had layoffs… it turns out I wouldn’t have gotten that role anyway.

Over in the software industry I found there was a grace that followed me around there too. Yes I had skills, yes I worked hard, but there were also opportunities I wouldn’t and couldn’t have orchestrated. Whether it’s cultural privilege or being blessed or something else, I’m not sure, but it was beyond what I felt I deserved. Again – grace.

And then, 15-ish years into this career, some thoughts start bubbling up, something is stirring, and I start thinking about the church stuff again. About using my skills, and finding that grace, in a church context. Don’t get me wrong, I love my work and career, and don’t plan on leaving… but there’s an internal pull to explore the grace of serving a church community, again.

Both to traditional church – using my skills in leading groups and public speaking to help people connect with each other and with God. But also in less traditional forms of community – facilitating community meetups, speaking at tech conferences. Being friends with people in the community so you’re available to help them find their way in key life moments – births, deaths, sickness and hospital stays, marriages and breakups. Helping kids and teenagers feel a sense of community they can belong to beyond their family and school friends.

It’s all stirring together into something. In amongst still enjoying my career and intending to continue it.

So when my mum mentioned her friend was writing a book called “The Future is Bi-vocational”, my interest was piqued.

Now that I’ve shared part of the story of my vocations – I’ll share what I learned from Andrew Hamilton’s book.

The future is bi-vocational

In the opening chapter Hamo remembers a conversation when he was about to start a new church, and he was given advice that “a viable church had 100 members and that I needed to grow my congregation to that point as soon as possible”. And so begins the unwinding of a bunch of assumptions about how to run a church: do you need to pay the salary of someone full time for the community to be viable?

For most of Christianity’s 2000 year history, we’ve had full time pastors who hold a privileged position in the community. But as society becomes both more secular, and also more religiously diverse at the same time, the assumption that a pastor can work in a church building, and the community will come to them, is not holding up anymore. That’s the mission problem we’re facing – it’s hard to care for a community if you’re in a building and the community doesn’t come to your building anymore. Also our suburban western culture often is suspicious of interactions with strangers, and so just leaving the building and starting up a conversation without a shared reason is also not an effective way to build relationships.

Then there’s the financial problem – as market pressures squeeze small churches in the same way big supermarkets squeeze small corner-stores, we’ll see increasing trends of there not being enough people in the small local churches to sustain a full time role through members giving part of their pay-cheque to the church. Bigger churches get better “economies of scale” for the surface level things people consider when church shopping: the quality of the Sunday preaching, music, and kids programs. A megachurch might be more financially efficient and effective in putting on a good Sunday service, but putting on a good Sunday service was never what church was supposed to be about. So the big churches start to attract people because of their more efficient and higher quality Sunday services, but then they need to spend their staff time on those services. The small churches can’t afford a full time pastor anymore, especially as they keep seeing their people switch to the bigger churches with the better weekend programs.

This feels like an existential problem for Christian churches… but in it Hamo sees a once-in-a-lifetime opportunity. Once in a lifetime is probably actually too common: it feels like this might be one of the ~500 year moments in church history that Phyllis Tickle talks about. The shift is coming, the cultural forces behind are probably unstoppable, and what church looks like on the other side won’t be what it looks like now. And therein lies the opportunity which he makes the case for.

He’d started his career assuming if a pastor needed two jobs, it was a sad interim state to pay the bills. But his experience has been that the setup is rewarding for a variety of reasons, and in this he sees the opportunity for the church to transform itself and be more true to its values, more effective in serving the community, and closer to the vision of a “priesthood of all believers” that Jesus intended for us.

Here’s my notes on some of the things that stood out to me in the book.

No spectators

Remember the board game Pictionary, where people played in pairs, with one person sketching and another trying to guess what they were drawing, while everyone else watched? Often church is a bit like this. However, it ought to be more like the “all play” moments in Pictionary, where everyone is involved in drawing and guessing and no one is spectating.

One of the significant benefits that can come from a shift into the bi-vocational mode is that a sometimes-dormant church, with minimal congregational engagement, is challenged to step up and function as a cohesive unit. The body metaphor Paul uses in 1 Corinthians to describe the church community means simply ‘attending’ a church should never be an option. Everyone has a role to play, and a job to do, in order to keep the body healthy. Anyone can ‘turn up’. It’s another thing altogether to discover your own unique gifts, and then to serve alongside the others in your community.

I loved this line of thinking. In the same chapter he proposes a hypothetical situation: what if a church got up on Sunday and announced that all the paid staff halved their hours, and would be taking other jobs. How would the wider community respond? Would it do less? Is there work or programs that staff are keeping alive that aren’t really worth it? Or would the rest of the community pitch in and do more? Spreading the load among a wider group, and including a more diverse range of skills, gifts and experience.

Take this example: a church pays someone to coordinate crisis care for homeless and vulnerable people. Does the existence of this role mean people in the community think “that is someone’s job, I can leave it to them?” What happens if that job disappears, or is halved? Does the community step in and fill the gap?

Views of work

I love the way Hamo unpacked some of the prevailing views of work in the church:

  • Work as cursed: we only work because this is a broken world. We didn’t work in the Garden of Eden, we won’t work in Heaven… we have to do it now, but that’s a shame.From a bible perspective, humans were working even back in the paradise of the Garden of Eden – work was part of the perfect plan, not part of the fallen broken version of reality. Work often is broken and feels cursed now, but fundamentally it’s supposed to be a good, creative, and meaningful pursuit.
  • Work as income: we only work because we need the money. You also see this in technology-optimist or anti-capitalist thinking: if we just had enough technological automation or free clean energy, we could eliminate all toil. If we just had strong welfare, or universal basic income, we wouldn’t need to work. Another take is that work is about wealth accumulation, the harder you work the more money you get, and more is good.He reminds us that the Christian view is clear that a good day of work deserves good pay, but it’s also clear that toiling your life to earn wealth isn’t worth it. Yes we work to earn money, but making it just about the money strips us of the bigger meaning, and the dignity, in the value we provide.
  • Work as service: Reminding ourselves that it’s not just about doing the tasks or getting the pay check, but the work we do provides value for someone, and doing it in a way that shows that person honour and respect and love, doing our work to serve them (and of course, still get paid), is a higher view of work.
  • Work as worship: There’s a Christian work ethic spelled out by Paul in his letter to Colossians: work hard, as if you’re working for God and not just your boss. Hamo pointed out that the link between work and worship actually goes deeper, with a single Hebrew word being used in each of these places:
    • Six days you shall labor, but on the seventh day you shall rest (Exodus 34)
    • Let me people go, so they may worship me (Exodus 8)
    • But as for me and my household, we will serve the Lord. (Joshua 24)
    All 3 of these verses, the word in italics is the Hebrew ʿāḇaḏ (עָבַד). The same word covers meaning from labour to tilling the ground to service to others to worship of God. I love moments like this, where you realise the language and culture you grew up in had a whole bunch of assumptions, but another language and culture uses words completely differently, and it shifts your world-view. The everyday labour we do can be an act of sacred worship.

Advantages of bi-vocational model

Often Christian ministers call the idea of a second job “tentmaking”, a reference to the second job held by the apostle Paul, who was the most prolific writer in the Christian scriptures. His other job, which helped pay the bills, was making tents. In the chapter “Tentmaking – it’s not about the tents”, Hamo fleshes out some of the reasons why having a role outside the church is actually beneficial even for the work you do in the church context:

  • Credibility: demonstrating you’re a hard working person with decent values, and you’re not just here to ask for money or to enjoy the status that comes with a leadership role.
  • Positioning: you’re more likely to interact day-to-day with the kind of people that you’re hoping to serve. If you work in a church your connection with the wider community can be pretty limited because you don’t have natural places to interact with the community around you.
  • Visibility: people will see how you work, and how your values hold up “in the real world”. It’s a chance to demonstrate the different values we preach about, in a visible way so people know it’s real for you.
  • Freedom: as a church leader sometimes you need to challenge the community, rather than give them what they want. If you’re relying on them for donations, then you might be afraid to say the hard truths. You see a similar dynamic with politicians and their donors.
  • Funding: relying on people giving from their income is always going to be limited. If you can sustain an income in a different way, it gives you more options for how you can do the church-based work without being limited by the bank balance.
  • Flexibility: some roles allow you to move more freely. Either because the skills are in demand in different areas, or because they open the door for visas and migration, or because they allow “work from anywhere”. Some roles also allow flexibility in hours, either at a week-to-week or a seasonal level, which might match the flexibility you need for your work in the church community.
  • Example: you want the whole church community to treat their work as worship, and a chance to bless the people around them. You can set the example. No one can say “it’s easy for you to say, you’re paid to do this”, when you do it in amongst your other work too.
  • Generosity: we say “it is more blessed to give than to receive”, and having an independent financial income allows you to live more generously than if you are reliant on receiving other people’s gifts to make your way.

In later chapters he outlines more personal reasons why a bi-vocational approach might suit, or not suit, depending on your particular personality. But these reasons I’ve listed are the competitive advantages he outlines for if someone chooses to do their church work with a bi-vocational approach.

“How do people become like Jesus around here?”

This was one of the reflection questions in the book that stopped and made me think the longest. What does that look like at my church? Do I think the way we operate is effective in helping people live like Jesus?

I particularly appreciated this push towards pastors, as the ones leading the community, leading with the example of their own life:

What is certain is that for your leadership to have credibility, and to form people into Christ, it has to come from lived experience deep in the gut, rather than clever theories of the head. It must echo a genuine encounter with Jesus. If it doesn’t, your people will know, and it just won’t fly. Any competent leader can run a church, organise meetings, and develop strategies, but what is most needed from a pastor is the ongoing experience of knowing and following Jesus, as well as the ability to help others have these transformative encounters.

As a bi-vocational pastor, it will always be tempting to skip the disciplines and practices that form us, and to get on with the various tasks that demand your time. But a pastor who isn’t ministering from a centred life is worse than no pastor at all.

There are countless books that can help you engage in practices that form you and allow you to encounter Jesus, but the bottom line is that it must happen and it has to be real. You cannot rely on your organisational skills, or preaching skills, to get you by. Your energy must come from a life earthed in a relationship with Jesus.

A useful, challenging reminder for me.

Some of the reflection questions at the end of this chapter were also great:

  • “How do people become like Jesus around here?” How would you answer that question for your own church?
  • The way a ‘centred life’ looks will depend on your current life stage. How does it look for you at present?
  • If you aren’t living a life centred on Jesus, then what can you change to put this key element in place?
  • Describe the culture of the church you hope for. If this is different from the church culture you currently experience, how can you help the church change directions?

Nuts and bolts of leading a team that’s structured like this

There’s a chapter where he maps out some of the pragmatic realities of trying to lead a church without a single full time pastor. First of these is about how you build a team to cover all the bases. Building a wider team of people who are not full time means you get a wider diversity of skills, experience and gifting. This is a good thing! You will have the things you are exceptionally good at, and also things you’re terrible at. Sharing the load means you can focus on your strengths, and find people whose strengths complement yours.

He leans on the work of Alan Hirsch who uses some archetypal roles from Ephesians 4 to think about different skill sets in a diverse church leadership team:

  • Apostle: the pioneer. Seeing new opportunities and having the drive and initiative to make them happen and lead a group towards them.
  • Prophet: the truth teller. Questioning the status quo, and calling people back when they’re on a dangerous path.
  • Evangelist – the recruiter. Drawing in other people to the mission, often focused outside the church community.
  • Shepherd – the nurturer. Caring and protecting people, helping them grow to maturity.
  • Teacher – the communicator. Able to teach people things about life and faith in a way that helps them grow.

The other part of the nuts and bolts is the prioritisation – you simply can’t get everything done. This is very familiar to me from a software engineering career: there is always more work that could be done. There’s never a true “finish” point.

He suggests one of the tools we use at work too: a simple Urgency/Important matrix, with these kinds of examples:

  • Not important, not urgent: organising your desk, archiving emails, useless meetings.
  • Not important, but urgent: phone calls, texts, some meetings.
  • Not urgent, but important: forward planning, relationship development, values clarification, strategic teaching prep.
  • Important, urgent: crisis response, sermon preparation, pressing team or culture problems.

As a part timer, you probably need to accept that the amount you get done will never feel like enough compared to all the things you could do. So you need to focus, and be okay with saying no. You need the things in both “important” quadrants. And you probably need to get used to saying “no” to some things that are urgent, but not that important. Whether you hand it off to someone else, or just accept that it’s okay for it to not get done – that is okay.

Other audiences for the same message

So I found this book really helpful. As someone with a full time career that’s not related to church at all, and as someone who grew up with both parents in full time careers that are about serving the church, having a clear and compelling case made for “why not both” was super helpful.

As I neared the end of the book the degree to which the practical advice in the book was geared towards those who default to full time church work, but are considering bi-vocational, struck me. I’m coming from the other direction, and similarly practical advice would be useful there. If the future really is bi-vocational, we need to not only convince some pastors to take on other jobs, we need to convince a whole lot of people with full time careers to dial back their ambitions there to make some space for a church-serving vocation as well.

The day I bought this book was actually when Hamo came to speak at my church, and I didn’t put together that he was the author of the book mum had mentioned until the end, but I loved his message. It was targeted more at those with existing careers, but from an angle of seeing your work as an opportunity for service and worship, rather than carving out space for explicit work in and for the church.

The sermon is online and well worth a listen. The opening story was so cringe-worthy and I was definitely expecting it to have some corny redeeming plot-twist, and the fact that it didn’t, the story ending without any resolution to the awkwardness, immediately helped me respect where this guy was coming from: no bullshit.

If you’re interested in a 40 minute talk rather than a 200 page book, this is a great place to start:

So, is my future bi-vocational too?

Yep, I think so.

Categories
Faith Personal

Confusion over the cross

Lately I’ve been confused by the cross, and confused about why I’m confused.  As I went through Easter this year I still was moved by the idea that God somehow loved us enough to die – but I couldn’t explain what it all means, and I couldn’t verbalise what it was about the traditional explanation that made me so uneasy.

So I watched a few lectures online, including this one by Tom Wright, and have picked up a copy of his book “The Day The Revolution Began” and started reading it, hoping to learn more.

I haven’t made it past the first chapter yet, but by setting apart time to think about this, I think I finally (subconsciously?) was able to piece together what I want to believe, in a way that draws contrast to my understanding growing up.

My understanding growing up:

God is love, and he loves you, but he’s also “just”, “righteous” or “perfect”, and can’t stomach your disobedience (sin), it’s because he’s perfect, and that perfection just doesn’t mix with sinfulness, and a blood sacrifice was needed to make things right for some reason.  Animals weren’t enough.  Jesus died so it didn’t have to be you.  That was enough for God the Father.  Now when he looks at you he doesn’t see sin, he’s just full of love again.

What I don’t like:

If Jesus is the image of the invisible God, then we should get a good idea of what God is like by looking at what Jesus is like.  A person with uncontrollable anger problems that needs satiating when people don’t do what they want… is not at all the type of person we see in Jesus.

Most (admittedly not all) of the anger I see the bible describe God as having, is the same kind of thing you see Jesus get angry over: injustice, caused by some humans, that crushes other humans.  This pattern seems to be well in place by the time you get to the prophets in the Hebrew Bible.  The “lash out” kind of anger is admittedly seems to be more present in earlier books like Joshua, and occasionally in later places like Ananias and Sapphira… but it seems the overall thrust is that God’s anger / anguish is about humans hurting each other, rather than about us offending his righteousness.

What I finally realised I want to believe:

Jesus was killed by humans.  It wasn’t God’s anger that put him there, it was ours.  We have the human condition, a tendency to lash out, to scapegoat, to viciously attack anything that exposes our frailty, futility or hollowness.  Jesus exposed how hollow the power structures of the day were, and showed very clearly how the actions of the religious powers and the actions of the political powers were not the actions of God – these people did not represent God.  He exposed the leaders, and like most humans, they lashed out.

But rather than fighting back and perpetuating the sinful violence of humanity, he took it and did not return it, in fact, while they were still killing him, expressed forgiveness and love.  To apply MLK’s famous truth: Darkness cannot drive out darkness; only light can do that. Hate cannot drive out hate; only love can do that.

On a physical level, the power-structures of Rome and of 1st century religious leaders killed him, because he threatened them.  On a sociological level, his non-violent response changed the game in a way where his followers continued to subvert the brutal power of Rome despite intense persecution.

What about theologically or spiritually?  Is there any meaning to it?

If Jesus really is God-incarnate, God-as-a-regular-human-being, (which I should clarify I want to believe), then him suffering the same wrath of humans as the rest of us shows that that wrath is from humans, not from God.  The angry and violent human condition that causes us to crush each other (which I feel sums up most of the concept of sin) is actually from us, not from an angry God.

In other words, what I want to believe: God was never angry that we’re not perfect.  That anger was always ours, that violence was always ours.  It took God himself suffering under that violence, as Jesus on the cross, for us to understand that the violence wasn’t coming from God.  The anger was never his.

So in a bizarre way, the cross is a sign that God is not angry: it shows me that he always loved and was not the one who was angrily lashing out.  And it is a sign that God is not leaving us to suffer alone: that God himself would suffer under our angry violence, it shows he knows our suffering and is not keeping his distance.  And it is a sign that God is working at a rescue plan: that he overcame hatred with love, darkness with light.  This is the butterfly effect – where one small act of love overcoming hatred is cascading and rippling outwards until hatred, violence and even death is overcome by love, and that the God of the universe is putting his full weight and power behind this plan.

And so, when I look at the cross, I do realise that God loves me and is not angry.  And I do realise that he loves me enough to enter into that suffering.  And I do realise that he has a plan for salvation, the rescue of the world – to transform this suffering through redemptive love.

Just because I want it doesn’t mean it’s true.

So that’s what I want to believe, I can finally articulate it.

But I’m looking forward to reading the rest of Tom Wright’s book, because admittedly: this is just the worldview that sits well with me, given what I’ve experienced and what I’ve learned and the cultural leanings that go with that.

Tom’s book looks like it will go through it in a more rigorous, systematic way: examining early evidence and early texts, examining the changing understanding of the crucifixion event by two millennia of theologians, and generally being a little more grounded than my “this is what I want to believe” write-up.

But, it’s good to be able to write down, as a product of my life and culture and upbringing and current understanding, what it is that I most want to believe about a loving God who had to die.

I’m looking forward to seeing where I land.  If you’re wondering any of the same things, asking the same questions, or exploring the same topics – I would love to hear about it in the comments!

 

Categories
Personal Reading & Inspiration Work Habits

What I learned from “Making Ideas Happen” by Scott Belsky (Book Review)

Making Ideas Happen Book Cover

On Sunday I finished reading “Making Ideas Happen” by Scott Belsky (founder of Behance).

7696135I’m the sort of person that has ideas.  So many ideas.  Some are ideas for apps or products, side projects or start-ups, cool programming libraries or fun creative projects.  When I look back at my work history, I am proud of the things that I have “shipped” and finished, or if not finished, at least gotten it “finished enough” that other people could start using it.

But there is definitely a graveyard of good ideas that I was very excited about at one point in time, that I even thought were game-changing, and maybe even started work on, but never managed to finish or get out there.

Gravestone reading "RIP: A Great Idea"As I was wrapping up 2016 and planning for 2017, I realised that I have several ideas that I actually want to see become reality.  Two ideas in particular (tentatively named Enthraler and Model School) I’ve wanted to do for at least 5 years, and have kept not doing.

When we finally launched Today We Learned I found out the pain of launching a good idea too late, and seeing someone else carry a very similar idea to success.  If I wanted 2017 to be different, and if I wanted to be part of these 2 ideas becoming reality, I had to get better at executing on ideas, pushing them forward and getting them out there.  And all of this while having a full-time job that I really love and am already feeling stretched in.

So when my my sister Clare and her husband Zac gave me a book for Christmas that promised to help me “Overcome The Obstacles Between Vision And Reality”, I was eager to get stuck into it.

Disclaimer and caveat: It’s worth pointing out that I’m viewing this book as advice on creative projects, which I’m viewing as distinct to start-ups. Both of them involve ideas, innovation and execution, but there’s a crucial difference.  If you want a start-up to succeed, you should probably not start with an idea.  You should start with a problem that real people hate so much they’ll pay someone to solve it for them.  Find a gnarly problem first, then let your ideas develop around that.  Creative projects on the other hand, start with your idea.  It’s a work of art, as if inspiration has visited and requested that you make an idea real, and it’s your job to make it.  It’s as much about self-expression and creative fulfilment as it is about business development.

Overview

The first half of the book (“Organisation and Execution”) is all about getting it done.  It’s full of practical tips to stay organised, stay focused, and keep pushing ideas forward until they’re ready.  These have made a massive difference for me so far.  The second half (“The Forces of Community” and “Leadership Capability”) focus on the relational aspects of ideas.  Ideas feel their most exciting, and most pure, when they’re in your head.  The moment you start sharing them, and inviting other people in to participate, things change.  This might feel like your idea is losing potency as it gets diluted by others, but it’s only with their help (and with the new aspects they bring to the project), that your idea is going to be successful.  How well you utilise these forces has a massive impact on your ability to consistently bring ideas into reality.

Organisation and Execution

  • The competitive advantage of organisation
  • The action method: work and life with a bias towards action
  • Prioritisation: managing your energy across life’s projects
  • Execution: always moving the ball forward
  • Mental loyalty: maintaining attention and resolve

I was really surprised by how prescriptive Scott is in this first section.  His basic argument is that they key to creative success is actually finishing your projects and getting them out the door, and doing that as often as possible.  The trouble is that ideas are exciting at the start, boring in the middle, a hard slog near the end, and then only get exciting again right before you launch.

A graph depicting energy levels for an idea decreasing during the middle, and new ideas starting and seeming more appealing during the low-energy plateau.
Ideas are exciting at the start, then get boring and hard in the middle, for a long time until you’re ready to ship – and only then does it get exciting again. Beware the temptation to start a new (and exciting!) idea during the project plateau.

So the key to all of Scott’s advice is to just keep you moving forward, one small step at a time, to get you through the trough and out the other side where your idea is finally a reality.  To do this, it takes dozens of small actions.  Focusing on these actions is the key principal in “The Action Method” – Scott’s big idea on how to do this.

Most other productivity books I’ve read have talked about the motivation and less about the mechanics of getting it done, but Scott is quite prescriptive. For example:

  • Organise your whole life into “Projects”.  Not just work projects. Not just side projects. Even mundane things like “grocery shopping” and “remember to call mum” go into a project. He isn’t prescriptive about where to store your projects, but I’ve used Trello.  I have one Trello board for my whole life.  The lists I use are “Home Admin”, “Personal and Social”, “myEd”, “Enthraler”, and “Model School”.
  • Each project has 3 types of things you can store:
    • Action Steps – literally, a specific action you can take to move the project forward.  The first word should be a verb: “Create nice styling for multi-choice component and upload to Github”.  Or “Read through things Cassie sent me and send through feedback”. My friend Stephen had an interesting take on this, going one step further and having a super specific first step in the action.  “Open gmail, read through the docs Frank sent me…”.  The trick here is to make it so obvious what the next step looks like, so whenever you have half an hour to work on something, you can easily pick an action step, start it, and push a project forward.
    • Back-burner Items – these is where you keep possible future action steps that you’re not ready to commit to yet.  Maybe they are ideas for much later in a project, or maybe they need some more thought before you commit to starting them.  Keeping them in a separate place, where you can come back to them, but where they’re not confusing you as to what the next steps should be, helps hugely.In my “Enthraler” project I have 8 ready-to-go Action Steps, and 29 items in the Back-burner.  That goes to show that when I start a new project, I’m excited about the possibilities and I keep thinking them up.  But I know if I want to keep moving the project forward, I just pick one of the Action Steps I’ve already committed to, and all of the exciting future ideas are in the “Backburner” list where they won’t distract me.
    • References – this is for things which you want to remember but they’re not actionable.  An example is finding a colour scheme I really liked for a project.  In the past, I may have taken a screenshot of the colour scheme and added it to a task.  But it’s not really an action I can take!  It’s just something I want to store so I can look back if I need to.  Now I keep things like this in references.  Also helpful: meeting notes, contact details, etc.  Keeping all these things in one separate spot helps keep the clutter down so you can focus on your next action steps.
  • Have a regular “review” session, say once a fortnight or once a month, where you go over your projects, see if the actions are still relevant and clearly defined, check what’s in your back-burner and references, and update things as necessary.  He recommends doing this some place nice, like your favourite coffee shop.  This is a part I haven’t had much practice with yet!

Screenshot of Trello
A screenshot of my projects in Trello. Each list is a project, each card is an action. (There is also a References and a Back-burner card in each list).

The Forces of Community

  • Harnessing the forces around you
  • Pushing ideas out to your community

One of the headings in this section is “Seldom is anything accomplished alone”,  and I find it a perfect reminder.  Some ideas are small enough that they can be accomplished alone, but even something like writing a song will benefit from collaboration.  Not to mention the help you would need in producing, mixing, mastering, distribution and release strategy.  And every project is like this – if you want it to become more than a hobby, you are going to have to bring other people into it.

A key part of this is overcoming the fear of people judging and criticising your work.  Overcome the fear, then get feedback early, and get it often. You don’t have to listen to what people say, if you want you can hold on to the exact vision you have.  But if you overcome the fear, and get the feedback, you will probably hear things that will make your project better, so it’s worth putting yourself out there.

There was a beautiful story in here about a story-telling course Scott went to, where people practised sharing a story, but the audience were not allowed to give “constructive criticism”.  Instead, they were only allowed to share what they really appreciated, what made the story come alive for them.  He found that as people iterated on their stories, this approach helped the “alive” pieces of the story shine even more, and somehow, the weak parts of the story began self-correcting with each iteration, but without losing the strength of the parts that really shone.  I loved that!

One of the things that challenged me the most in the section was to actively self-promote what you’re working on, and to build an audience of people who care about what you’re working on.  If you’ve ever read case studies on a site like “Indie Hackers”, you realise that a common story in side-project success or start-up success is that the person starting had an audience who really cared about what they were working on, so when they launched a new project, they had someone to launch it to.  So don’t be afraid to self-promote and build an audience, and show them what you’re working on regularly.  The fear you have shouldn’t be that you’re inflating yourself in front of others, it should be that you’re not giving your idea any air, and it might die in your mind without ever becoming a reality.

The way Scott consistently reinforced this was a wake-up call for me.

Leadership Capability

  1. The rewards overhaul
  2. The chemistry of the creative team
  3. Managing the creative team
  4. Self leadership

I’d been reading the book thinking primarily about my side projects, which are solo-shows for now.  Scott offered distilled wisdom and advice from his experience and from the research conversations he conducted, and while it’s not immediately applicable to the projects I’d been thinking about, I can definitely see how it ties into my work at myEd, and how it will be important to attract more contributors for any project I do going forward.  It identified a weakness in my approach to executing so far – the tendency to do it all myself.

Much of the advice given in this section was focused on character.  So not so much “how to run a meeting”, but “when in a meeting, let other people talk first and make sure you actually listen”.  Things like that.  I really do believe that humble leaders attract talented collaborators, but more importantly, their humility and strength of character breeds loyalty – which you just don’t see as clearly when it is obvious the leader isn’t paying attention to your input and your ideas.

The difference it has made for me

Reading this book came at the perfect time for me.  After closing down Today We Learned last year I began working full-time at myEd, but found I was still swimming with ideas for outside projects. By the time the new year rolled around, I had multiple projects I really wanted to run with, but was just not convinced I could push them all forward while still being effective at work 5 days a week.

This book, especially the focus on the action method, has helped me dramatically – and people have noticed.  Most significantly my wife Anna – who keeps commenting that she can’t believe the change in how I work and in my energy levels, and in my ability to keep things moving – not to mention staying on top of things at home more effectively.

On a practical level, it has meant that I’m staying focused and effective at work, not getting stressed out by home administration (keeping track of finances, bills, investments etc) because I know I have everything tracked, and if I sit down at work, or sit down to do some home admin, or to give time to a side project, the next actions are right there for me to continue with.

Because of the stage of life we’re in – we moved across the country to focus on our work and our creative pursuits, and we don’t have young kids to care for and hang out with – we have a fair amount of spare time.  I try to give 1 hour each weeknight to push a side project forward, and then a few hours of blocked out time on either Saturday or Sunday.  With this rhythm I’ve been able to push forward my two main side projects to the point where both are almost at MVP (minimum viable product) level.  And this has been during one of the most incredibly busy and stressful periods at work – coming home and having a different project that I can get into has in many ways helped me maintain my energy and positivity during some of the more stressful moments at work.

The challenge to think about how the community around me has also been incredibly helpful.  As well as the two side-projects I’ve been pushing forward, there were another two ideas that I couldn’t shake, and that I wanted to help become reality – but you can only stretch yourself so thin before you stop being effective.  By reaching out and sharing these ideas with friends, I’ve actually found other people working on similar things, and have been able to support them rather than carry it forward myself, and I’ve found this incredibly rewarding, while at the same time satisfying the creative urge that demands I be part of making that particular idea happen.

It’s been an incredibly timely book to read (thanks Clare and Zac!) and has helped me hugely so far.  To anyone who has ideas but can’t seem to get them off the ground, I recommend it highly.  I’m excited to see how the rest of my year pans out as I continue pushing things forward one action step at a time.

More Info

To follow Scott Belsky: website, twitter
To buy Making Ideas Happen: amazon, goodreads

 

 

Categories
Faith Personal Reading & Inspiration

I’m not lapsed. I am a Catholic in waiting — waiting for my church to remember the Gospels, to be a justice and peace-seeking community, to be fully inclusive of women and to be welcoming to people who are not hetero-normative.

Read more: What should church look like

Categories
Haxe

Language and API Design

Paul Graham has written some great essays over time, and most of them hold up surprisingly well as they age.  Take this article, “Five Questions About Language Design“.  Written in May 2001.  That’s over 12 years ago from today as I read it, and many of his predictions have come to pass (the dominance of web applications, the rise in popularity of niche programming languages), and most of his logic is still sound, and still insightful.

Two particular points I found interesting, and would be interesting to the Haxe community I spend most of my time in:

4. A Language Has to Be Good for Writing Throwaway Programs.

You know what a throwaway program is: something you write quickly for some limited task. I think if you looked around you’d find that a lot of big, serious programs started as throwaway programs. I would not be surprised if most programs started as throwaway programs. And so if you want to make a language that’s good for writing software in general, it has to be good for writing throwaway programs, because that is the larval stage of most software.

I think Haxe is beginning to show it’s strength here in gaming.  People are using it for Ludlam Dare (write a game in a single weekend), and then later the game scales up to be a full-featured, multi-platform, often commercial game.  Haxe is good for a quick win (especially when targetting flash), but then you have the options to target so many other platforms as your vision for your game/app expands.

I’d love to see ufront get this good.  I have so many things I would like to use as an app, but which I don’t feel justify an ongoing subscription to an online company.  Many of them could get an MVP (minimal viable product) out in a weekend, if the framework was good enough.  And it’s getting good enough, but still a little way to go :)

And then this:

2. Speed Comes from Profilers.

Language designers, or at least language implementors, like to write compilers that generate fast code. But I don’t think this is what makes languages fast for users. Knuth pointed out long ago that speed only matters in a few critical bottlenecks. And anyone who’s tried it knows that you can’t guess where these bottlenecks are. Profilers are the answer.

Language designers are solving the wrong problem. Users don’t need benchmarks to run fast. What they need is a language that can show them what parts of their own programs need to be rewritten. That’s where speed comes from in practice. So maybe it would be a net win if language implementors took half the time they would have spent doing compiler optimizations and spent it writing a good profiler instead.

Nice insight.  I sometimes worry that the code I’m writing will be slow.  It’s hard to know if optimisations are worth it, especially if it may compromise code readability etc.  A better solution would be to focus on making profiling easy.  On the JS target you can easily use the browser tools to show profiling information.  Another option is to bake it into your Haxe code, something that the “massivecover” lets you do.  Wiring that support from massivecover into ufront or other frameworks, and generating pretty reports, would be a very cool way to encourage people to write fast apps.