InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Developer Survey: Challenges and New Technologies

Posted by Dave West on Aug 24, 2010

Sections
Process & Practices,
Architecture & Design
Topics
Survey ,
Architecture ,
Careers ,
learning
Tags
Trends

Embarcadero Technologies has released its 2010 Developer Survey Report, a survey of 600 professional developers conducted in May-June of 2010. The survey focused on identifying the "top developer trends, challenges, key initiatives, and current tools being used." Survey respondents "were primarily application developers (90%), software architects (48%), database developer (44%), and application developer (24%). Numbers sum to more than 100% due to respondents with multiple roles. Sixty-six percent of the respondents were self-employed or worked for companies with less than 25 employees. 8.5 percent worked for companies with more than 1,000 employees.

The survey covered three primary areas: Windows 7 development, developer trends, and two questions on economic issues.

Survey results on Windows 7 questions:

  • nearly 40% report that they have been using Windows 7 for less than a year, with 16% using the platform for more than a year. less than 10% of respondents said they had "no plans" to develop for the platform.
  • Most respondents (54.4%) are working on enterprise applications. Amost 40% are working on small-business applications and close to 25% are working on inter/intra-net applications.
  • The largest challenge faced by Windows 7 users was the need to support previous versions of the Windows OS (33.5%). Only 3% expressed concerns about the stability or performance of the platform, and only 8% suggested that a lack of development tools presented any kind of challenge.
  • Excitement about using new features of Windows 7 was generated primarily by the touch, multi-touch, and gesture capabilities (38%), but, interestingly, an almost equal number, 34%, found the excitement question non-applicable. It would be interesting to know the attitudes or concerns behind this answer.

 

Three of the developer trends questions focused on developer tasks/activities and only one addressed technology trends.

  • The three biggest challenges facing developers were: Not enough time for work tasks, poor testing, and lack of requirements. Poor planning and slow or inefficient tools were a close fourth and fifth response. "Inadequate skills" was the least reported challenge.
  • Coding occupied the most time for 37% of the respondents. Testing only made it to 5% of reported time - correlating nicely with the third biggest challenge facing developers. The least amount of time was spent on quality assurance - just over 2%.
  • Asked what they would like more time for, sixty percent of the respondents wanted time to learn new languages and technologies. A nearly equal number (58%) wanted time to keep their skills up to date. About 36% wanted more time to devote to testing.
  • Questioned about trends, 56% said that mobile applications will have the largest impact on development community as a whole. 64-bit computing (50%) and parallel programming (47%) were next. Cloud computing was cited by about 31% of the respondents. Functional programming, an area that has received a lot of attention the past two years, was cited by 10% of the respondents. NoSQL databases (7.8%) was the least cited technology.

 

The two economy oriented questions concerned self-employed developers making more (43.3%) or less (26.4%) less money compared to five years ago; and, is it harder (43.8%) or easier (22%) to sell applications in today's market.

Embarcadero is an international developer tools company and it was not clear if the survey was sent to their customer base or had wider circulation. Like all surveys, the primary value arises from an opportunity to compare your own experience with that reported. Is your experience and are your expectations consistent with this report?

why two "Application Developers"? by 侯 伯薇 Posted
Re: why two by Juan Jose Zapico Posted
  1. Back to top

    why two "Application Developers"?

    by 侯 伯薇

    Survey respondents "were primarily application developers (90%), software architects (48%), database developer (44%), and application developer (24%).

    there are two "application developers" in the text above, and the rate were 90% and 24%,Why?

  2. Back to top

    Re: why two

    by Juan Jose Zapico

    It's a mistake, 90% are software application developers and 24% are web application developers.

    According to the original source this are the numbers: "software application developers 89.6% of the responses, followed by software architect (47.2%), database developer (44.2%) and web application developer (24.2%)"

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.