About this blog

Software development is a commitment to lifelong learning and I guess we’ve all reached where we’ve reached via a different path. After feeling burned out more than a few times and nearly costing myself a relationship trying to keep my boss happy rather than my girlfriend (now wife) happy, I knew I had to find a better way to keep up with the demands of the industry.

How can some people always seem to have the answers, or even ask the right questions?

Why did I feel like I’d done 1 year 10 times rather than 10 years?

How can I expect to move quickly enough to get the job done?

How can I add strings to my bow other than just coding?

I came to realise that learning how to learn is as important as coding itself.

So I figured there must be plenty of people who feel the same way as me, that it’s hard to keep up, that there must be smarter ways of working. Also, the ability to *retain* useful knowledge for use in multiple contexts seems a good thing to focus on if we are to get up to speed quickly.

What you can expect from this blog is a scouring of the internet, ideas for improvement, and a brain dump of thoughts on better ways of working.

It won’t just be theory though, I’ll publish how I put these thoughts into practice with concrete examples and my study plans. I’ll be starting with studying for my AWS Developer Associate exam, hopefully people will get use out of that.

Additionally, I’ve been using GTD for years now, and have found it a life saver for project management at an individual level. Expect to find some thoughts on this and and other productivity hacks here.

I think as developers we also owe it to ourselves and partners/family to try and get the best out of our day.

I hope that you find this site useful, and positive feedback is always welcomed here.

James