Creating a powerful online presence with a platform

Having a website, blog, portfolio or stackoverflow profile is common amongst software developers. Yet, by thinking about our online presence as a Platform we could be achieving greater results. But what is a platform? And why would we want one?

My journey with Platform all started a few years ago when I read Key Person of Influence. It ultimately prompted my intrigue with writing. Blown away by the ideas in this book I had to dig deeper. This is when I discovered books talking about similar concepts:
I recommend them all.
 
The concept of Platform can apply to every type of software developer career. It doesn’t matter if you: want to work full time, start a business or go into management … The concepts of Platform apply no matter your career vision.

Perennial Seller

Summary

What a read. I loved this book. I know I’ll be returning to this time and time again in the future.
 
Perennial seller started out a life as a book about book marketing itself. Ryan runs a successful book marketing company. After getting urged to write the book he started it. In the process, Ryan pivoted from “book marketing” to creating a classic work. A perennial seller.
 
In his early life, Ryan worked with the author Robert Greene. I’ve heard Ryan quote many times a single line from Robert that seems to have made a lasting effect on him. That question was: How do you write a classic? To which Robert replied:
 
It starts by wanting to create a classic.
 
This line summarises the book. The book is about how to create lasting work. Not only in writing but in anything. A product, a company or an idea that stands the test of time. That people return to time and time again and love.

5 ways to get more out of your non-fiction reading

Flicking through pages can only take you so far. If you want to digest and get the most out of your non-fiction reading time, you'll need a plan; a strategy.

I’ve been recently pushing myself to improve certain knowledge gaps. Whilst thinking about how to tackle the problem I ended up posing myself a question:
 
When have I made the biggest learning improvements in the past? How did I do it? And can I repeat that process?
 
The answer took me back to when I was a student …it was when I read non-fiction. a lot.

Plot twist! Your portfolio is not about you …

A subtle change in the way you set out your developer portfolio can make a huge difference for it's impact and reach.

For developers, portfolios have become more commonplace. Which in itself is a wonderful thing. It’s a great tool to showcase your work and your passion. I even believe it’s one of the best investments you can make as a developer. Especially if you’re starting out. But, I made a mistake when I created mine years ago. I wish I could go back and do things again. Because there is something that I’d change.

Why “Should you build your portfolio with code or a template?” is the wrong question

Asking which way to build your portfolio is only half the question: the real question is how do you deliver what the market demands.

If you want to step up your developer career you might be considering creating a portfolio. If you are, bravo! Having a portfolio immediately puts you ahead of the curve. So, you sit down with a coffee in hand and debate the best ways to create your website and a thought crosses your mind:
 
Do I create my portfolio in code, or do I use a template?
 
This question came up recently on a front end developer forum. The answers that emerged were short and shallow. Did they answer the question? Yes. Will they help the developer get hired? I’m not so sure.

So Good They Can’t Ignore You

Summary

Cal’s book centres around the main hypothesis that we should “do what we love”. Cal calls this the “passion hypothesis”. That following our nose is the best way to find work that we love, and are passionate about. In the book, Cal offers a different perspective, in how we can find passionate work. This view is that: to gain passion and happiness with our work one must first become valuable. Those who are valuable receive rewards usually associated with “finding your passion”. Finding our passion is therefore a dangerous or impossible task without committing to mastery in a given field.
 
Despite some editing related criticisms, the book felt like it had some good insights. The insights made the book overall worthwhile. I’d recommend it for anyone starting out or frustrated about work they’re currently in.

The best software developers write, you should too

10 reasons you should write. Gain clarity over your thoughts, get better job satisfaction and accelerate your career.

The rules are changing. Especially for knowledge workers like software developers. It’s impacting how we should craft our careers. The opportunities and the tools we have are different to the years before. Writing platforms are one of these big shifts. We have the ability to share our ideas with large audiences. It’s simpler than ever. Mainstream media influence is yielding to the power of individual influencers. Only a handful of developers will identify this opportunity. Even less act on it.
If you insist on playing todays games by yesterdays rules, you’re stuck – Seth Godin, Tribes.

Why learning a new framework could damage your career.

Asking questions such as "Which framework should I learn?" is asking the wrong question. Instead, you should be asking, where should I spend my energy to improve my mastery.

 A water-tight career strategy for your personal brand is your most important asset. Having one will:
  • Guide your decision making
  • Lead you closer to fulfilment
  • Create more purpose in your work
It also puts the power back in your hands. You can write blogs, speak at talks, read books – these are all activities well within your power. With so much choice, how you spend your time has never been more important.