by Danny Brian | October 4, 2012 | Comments Off on The Renaissance Developer (part 1)
Nearly every day, I overhear someone remark on how dramatically the world of technology has changed. Mobile. Social. Cloud. Information. If most professionals think their lives have changed as the result of this nexus, just imagine how developers feel! Our world is barely recognizable. Some developers welcome this change, and rise to the challenge. My team calls these folks “renaissance developers”, and we’re not just trying to be clever here. These are folks who thrive on the new. They welcome the revival of interest and passion in great technologies. They know they have a lot to gain by adopting new tools, languages, practices and patterns. And they are some of the most valuable individuals in your organization.
My document “The Renaissance Developer: Skills Guidance for Modern Applications Programmers” is now available to Gartner for Technical Professionals subscribers, and helps developers and managers meet these new challenges. How do developer skills need to evolve? For what types of competencies should you be hiring? What practices will encourage this evolution? Deep, very deep.
Over the coming weeks, I’ll be posting a series about this individual — elusive to some, familiar to others — known as the renaissance developer. Some of the content is drawn from one of my presentations by the same name. It features Craig.
As you can see, Craig brings to the job a veritable toolbox of skills. He is the prototypical renaissance developer, and there’s a lot more to him than meets the eye.
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.