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.

Panel: Surviving the Downturn

Posted by Abel Avram on May 14, 2009

Sections
Architecture & Design,
Development,
Enterprise Architecture
Topics
Choreography ,
.NET ,
Architecture
Tags
Languages

A panel of hard core developers, including Ted Neward and Jeffrey Palermo, assembled at TechEd 2009 has discussed the current economic difficult times and expressed their opinion on what a developer needs to do to remain employed.

The panelists were:

  • Eric Hexter (EH), software consultant, Austin, Texas.
  • Ted Neward (TN), ThoughtWorks.
  • Rachel Appel (RA), software consultant, Microsoft ASP MVP.
  • Aaron Erickson (AE), Principal Consultant, Magenic Technologies.
  • Jeffrey Palermo (JP), CTO of Headspring Systems.
  • Moderator Bryan Von Axelson, a solutions advisor for Microsoft US Partner Group.

The following contains the key points expressed by the panelists covering 5 major topics.

How do we survive the downturn?

TN: A corporate IT developer employed by a company who is in a business other than software should show that he understands what the company’s business is about. Programming is a commodity skills these days, so in order for someone to be remarked he needs either to be the best programmer around or to have additional skills. 

JP thinks that a good programmer is always going to be hired if he loses his job, while TN and RA think that it might not be the case if he lives in an area where there are not many software companies around to benefit from a large job offering.

JP considers that programmers should not be happy with just learning and mastering a single language, and they should broaden their perspective considering multiple languages and watching the industry trends.

Quality should play an important role

RA considers the developer should show that he is not just writing code but he is concerned about the quality of the code he writes.

TN sees a benefit in the current economic circumstance. He considers there are a number of programmers who should not have become programmers in the first place. They don’t have any passion for this, they are not really interested in doing it right and they mostly produce low quality code. As a result, the present economy will force them to do something else.

Projects that still matter today

EH mentions there are still government projects going on, but their requirements are higher being more concerned with quality.

TN considers that many businesses are still asking for software but they are more cautious with their funding trying to make sure their money is spent wisely.

AE has seen projects which took 4 months to go through the legal procedures because the beneficiary wants to check each line of the contract. Also, nobody does porting projects these days.

JP: Many business have a budget for software projects but are holding the decision to start them to see how things are evolving.

Technologies that will matter in the near future

TN suggests developers to learn something that is trendy today, that is required by companies or that is futuristic. The important thing is to keep the eyes open and learn things in advance. He nominates F# as a good candidate.

AE suggests doing something that one can be passionate about even if it is not so well rewarded.

EH: one should learn something that is important but it is missing from his list of skills plus improve the quality of what he is already doing.

JP emphasizes architectural skills which open the doors on various projects. Technologies may change but the ability to take a business problem with its context and constraints and coming up with a solution will remain regarded as highly valuable.

Learning other correlated skills

RA says that she does database administration work.

AE: consulting opens the eyes to what other businesses are doing allowing the consultant to learn more and, in the process, raising his value.

JP: learning server administration and network administration is helpful.

Conclusion

The conclusion of the panel is that developers need to keep learning new skills, they need to keep their eyes open to see the changing trends and follow them and they need to get prepared ahead of time.

No comments

Watch Thread Reply

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.