Book Recommendation: Give and Take

I've just finished Give and Take by Adam Grant. My manager suggested I read it and leant me his copy a couple of months ago.

I've just put it down, and I must say, it's one of the best (and only - don't judge) books I've read in a long time. It talks about reciprocity styles, those who give more, those who match, and those who take more. It argues for being a giver - giving more, creating more opportunity for everyone to succeed. It provides many examples from people, backed up with many, many studies.

I also try my hardest to be a giver. Over the last few years, I've upped my volunteering, done more talks, written more content, and learned to take less. I'm seeing benefits pop up from all of that, in many unexpected and wonderful ways. This book told me why that was happening, and most importantly, to keep going. 

Give it a read. 

Back Into Swift!

I'm stoked to announce I'm getting back into Swift. I'll be changing jobs and company soon to be a fulltime iOS developer (again). 

But here's the issue - I haven't done Swift since about Swift 1.0. I did a bit of Swift 2.0, but then I left go to explore (and also love) server side development and AWS. 

So, now that Swift 4 is out, and Swift 5.0 is on the horizon... I have a fair bit of catching up to do. So how am I doing it?

I reached out to a bit of a guru in the area who does great content around Swift, John Sundell.

I took his advice, and Mugunth Kumar's (who you'll remember from DevChats) and started on my journey.

First up, I'm watching WWDC Videos. The plan is to watch the following videos:

  • 2015 - What's new in Swift (Swift 2.0)
  • 2015 - Protocol-Oriented Programming in Swift (Crusty... I've tried and failed to understand th end of it too many times...) 
  • 2016 - What's new in Swift (Swift 3.0)
  • 2016 - Swift API Design Guidelines
  • 2016 - What's new in Foundation for Swift
  • 2017 - What's new in Swift (Swift 3.something?)

This should provide a great overview and get up to speed on the changes in an efficient manner. 

After this, I'll take John's advice and work on converting an project and go slow and think carefully about each migration step. 

I'll keep you posted.