As you might know, I haven’t posted anything to TDD Fellow blog for quite a while. I wasn’t just lazy. I have been severely busy.
I was busy creating new things.
I’ve written a few guest blog posts, for example this guide might teach you how to make better decisions as a software developer. That article is about stress, willpower, mental health and results in a work of software developer.
Right now I’m writing another guest blog post and talking to more blog authors looking for guest posts.
Reading Complete Software Developer’s Guide
Also, I’ve read an amazing book, best seller in Software Engineering category, that I predict will become one of the classics of Software Engineering, alongside Refactoring and Patterns books - The Complete Software Developer’s Career Guide.
I loved it. It is a book for a software developer of any stage: beginner that is just learning, professional trying to land THAT first job, competent professional software developer itching to improve or an expert software engineer looking for ways to transcend and go beyond a simple software engineering role? Then this book is for you. Read my full review on the Amazon.
Stories on Productivity, Negotiations, and Stress
(for software developers)
I’ve started a whole series of stories and case studies (I call them “War Stories”) on productivity, negotiations, and stress for software developers. So if you want to learn how to negotiate, be productive and handle stress as a software developer, go and grab my stories.
The stories are published under the name of “Productive Developers Only.” One might think: “What a cheesy name!”. I love the name, though. Hehe :) It is not just for Productive Developers Only, it is also for anyone who wants to be more productive, more successful and healthier as a software developer.
So far, I’ve written one case study called “How to Get a Better Offer Accidentally.” It focuses on one simple negotiation technique. In fact, there were already two revisions of that story. And I’ve received some more feedback from my dear friend and colleague Alexis. So I’ll write the third version soon, and it’ll rock! By the way, check out Alexis’ blog: Free is a Verb - it is amazing!
Also, I’m in the process of interviewing a few developers for the next case study called “Why You Need to Work Four Hours Only Per Day.” In fact, you are not working more than four hours per day, even if it takes you eight or more. Isn’t it surprising? If you want to know more, hurry to grab my stories, and you’ll receive the case study as soon as I publish it in a few weeks.
If you are still reading, I’ll throw some more interesting teaser at you ;) How about I tell you what first case study was about?
Julia was searching for a first job as a developer after graduating. It was tough, as most companies wanted to hire experienced developers. Julia didn’t lack qualifications for the junior positions. She was interviewing with two startups in her hometown.