Software development trainings are usually about... well, software development. However, this next one isn’t. We’ve done a lot of trainings on how to write good code and using various technology stacks, we’ve talked about DevOps, Git flow and best design practices. All this time though we haven’t talked about what makes an individual a good software developer.
The question every developer has to ask himself/herself is:
If technical ability is the primary characteristic that gets someone the job, what keeps them on the job?
Technical skills are important. Very important. However, being a good software developer involves managing your career, reaching your goals and enjoying your life(John Z. Sonmez). If you haven’t yet, I’d encourage you to look for a copy of the software developer’s life manual. Sonmez says something we are absolutely on board with:
I embrace a holistic approach to software development. This means that I think that if you want to be a better software developer—a better anything, really—you need to focus on the entire person, not just one or two areas of your life.
This is what this next training is about: getting you to think of your software development as a career that needs to be thought through.
Of course we could make tall claims. Like, attend this training and your life will never be the same again, but we won’t. We might not achieve that, but we will set you on a path that will lead you towards a more successful software development career.
We’ll start off by talking about your software development career and how to actively manage it, how to work in teams, how to think like a business, specialisation, deal making and meeting skills, adding value, lifelong learning among other things. Quite a lot to cover in just 4 hours!
When is this training?
We will have the training on Thursday, November 19th 2015 at the iHub Space on 4th Floor of Bishop Magua Centre. The training will run from 9:00 AM to 12:30 PM and will only cost you KES 1000
Who should attend this training?
All software developers who:
- Struggle to work in teams
- Do not think of themselves or their software development(even if employed) as a business
- Cannot convey their ideas clearly to users without being accused of being “too technical”