Being able to develop software today is more applying best-practices than being knowledgeable in a specific technology. Why? Maybe because technology evolve so fast that it’s better to understand principles than technicality. Obviously a minimum of technical skills and experiences are required to perform best.
This makes university degree workers and autodidact people more interesting employees, since they are open to change and apply best practices. Many call it Software Development Maturity or Software Engineering Culture which is link to a way of thinking and a continuous desire to improve and be aware of new ideas in the industry.
Here’s a list of what I consider be essential knowledge for today’s developers.
6 Fundamental Knowledges
- SOLID (Code magazine article, Wikipedia)
- Object Oriented Programming (OO)
- Design Patterns (Do Factory)
- Domain Driven Design (DDD)
- Agile / Scrum (Agile Manifesto, Scrum org, Agile Scout)
- Test Driven Development (TDD ) (Arrange Act Assert, Eric Mignot, TDD trainer)
Is software maturity enough?
We are all humans… Yes we are! As such we have needs and abilities we should respect. Software development was often considered as a nebulous science where people are resources that can be interchanged. Well we learned, sometime the hard way, which it’s not the case, some people achieve better with specific “people skills” that support and healthy team and we should encourage more these behaviours.
Here’s a list of developer people skills:
- Business Awareness – Understand expected behaviors and value
- ROI thinking – Consider efforts VS added value
- Tolerence to changes – It will occurs, be ready for it and embrace it
- Recognize – Take time to acknowledge other’s accomplishment
- Team spirit – Ability to be efficient in a team
- Communication – Active listening and clear explications, don’t hesitate to interact!
- Open minded – Accept comments and try to improve overtime
- Organisation – Work on top priority first
How could I improve?
As anything in life, you will have to work to get results. First you can participate in communities of your area (ex: Communauté .NET Montréal, Agile Montréal), you can listen to podcasts (ex: Visual Studio Talk Show, Vox Agile) or event read about emergent architectures (ex: CQRS => Greg Young Blog post, Another Greg Young Blog post, Julien Letrouit’s Blog). Try to become a better team player, ask yourself what you can do to be more efficient in your context.
- Any other ideas to improve that article?
- What do you think is the most difficult to achieve?