April 2009 Archives

Keep it flexible

April 27, 2009 2:54 PM

While there was a time when job seekers could afford to be choosy about the roles they took on, which company they worked for and the hours they worked, unfortunately, there's no doubt recession and large-scale redundancies have had an impact on the IT industry, turning the job-scene very much into a buyer's market. As candidates find themselves competing with many others for fewer roles, flexibility will be a key factor on deciding who gets the job.

Although there are definitely jobs available in the market, especially for those with specialist skills and relevant experience, candidates who are willing to show flexibility in their requirements do give themselves an added advantage. Whether it involves taking on a different role than you're used to, working different hours than usual or considering short term rather than longer term contract work, a willingness to adapt to the changing needs of the market could be the one key skill that propels you to the top of a potential employer's list.

Nor does flexibility necessarily involve making sacrifices; one very positive effect of the new jobs market is that it has removed some of the barriers that have stopped candidates putting themselves forward for certain roles in the past. Perceptions about the kind of roles and responsibilities they could get or take on have often caused candidates to take a cautious approach to job-seeking in the past. Now, however, as employers demonstrably place more value on specific skills (rather than generic 'IT skills') and a willingness to understand the wider business context, candidates are in a position to explore avenues that they may not once have considered, whether that involves applying for a different type of role, considering a change in sector or approaching a different kind of organisation.

As long as they remain realistic and willing to negotiate, there are still many opportunities for IT workers in today's market; while knowledge and skills are always important, a change in mindset can be the key factor that makes the difference between finding or keeping a job and not.


When Rasmus Lerdorf announced Personal Home Page Tools 1.0 in June 1995, I doubt that he had enterprise software development in mind. Fourteen years later, the CTO of Zend software, Zeev Suraski, shows me a slide. It has a large area shaded light blue, representing all the part-time or hobbyist users of PHP, and a thin strip of darker blue representing corporate PHP developers or ISVs (independent software vendors) offering PHP applications.

"Those two categories are growing significantly," says Suraski. "In 2006 we're talking about maybe 10% or less of the entire user base, whereas by the end of 2009 Gartner expects it to be about 35%. This changing demographics is a sign of maturity for PHP."

He would say that, of course, because that thin strip is Zend's potential customer base. The company sells a professional IDE for PHP, support services, and the just-released Zend Server which packages PHP along with commonly used companions such as MySQL. There is also an optimizer (technically an op-code cache), a Java connector, and the paid-for version has additional monitoring, debugging and caching components.

It is not just talk though: Zend is flourishing despite the recession - "the Q1 of 2009 has been our strongest quarter ever," says Suraski - and although PHP's enterprise market share is small compared to Java or .NET, it is growing.

What interests me is why this has happened. It is partly thanks to the merits of PHP, its speed and simplicity, and the fact that Java's libraries and to a lesser extent those in .NET are over-engineered for many tasks. More directly important though is that the community using PHP - the large area of non-paying users in Suraski's slide - has created a remarkable pool of resources on the Internet that is available to everyone, business users included. Non-commercial users are those most likely to share their knowledge, unfettered by concerns over business confidentiality or copyright.

I experienced this for myself recently, when I sat down to write a small PHP application. Every problem I encountered was quickly resolved with a Google search, or by looking at the discussion attached to entries in PHP's online documentation.

II don't mean to belittle the extent of online resources available to Java or .NET developers, but would argue that PHP has the edge here.

I also realise that it is no good just doing a search and adopting the first solution that seems to work. Developers need to understand what is being suggested and assess its quality, rather than optimistically pasting in the first block of code that seems to work. If PHP has a weakness, it is that the language does little to help developers write secure, maintainable applications, which may explain why there are so many vulnerable PHP applications out there.

So what about Zend Server? Note that this is not an application server in the WebSphere sense; it is primarily a PHP platform installer and support package, and as such not that different technically from what you can do with a Linux package manager or something like XAMPP.

I tried installing Zend Server on Windows Vista and bravely chose the IIS 7.0 integration rather than Apache. It actually worked smoothly and will be fine for developing PHP applications, though I would normally deploy to Linux, which I gather is a common scenario. That said, the work done by Zend and Microsoft makes PHP on Windows Server a reasonable option as well, and one that makes sense if you need to integrate with .NET, SQL Server or other Windows services.

The real winner here is PHP. Zend is making it business-friendly without damaging its open source ethos, and in doing so providing a great example of how free software can sidle its way into the enterprise.

Danger Signs of a Team

April 20, 2009 11:26 PM
I was speaking with a colleague who is thinking of transferring to a team in the same company. Something didn't feel quite right, so he tried to tell me what felt wrong.

"Everyone is all over the building. If I want to talk to someone else, I have to go over and around to find them. That team shares its servers with another team in another time zone. They're all working on more than one project at a time. I like the manager, but he's also doing technical work, and sometimes the management work doesn't get done. But the work looks really fun. What do you think?"

I think he's describing a group, not a team. And, maybe, not a very organized group at that.

If you're thinking of a new job or a new role, look at the makeup of the team you'll be joining. Here are things to look for:
  1. A team is small and has interdependent commitments. That means you need to work with the rest of team, not spend all your time trying to find them.
  2. A team should have equipment that's committed to them, so they can manage the equipment. (Same with space.) If they have to share equipment with another group or team, they are not masters of their own fate, and can't let tests run as long as they might need to.
  3. Team members who multitask cannot meet their commitments. That means they can't make progress when they said they will.
  4. Managers who do technical work are not managing.
Now, if the work is sufficiently fun and engaging, and if this team really is a group, maybe all those other reasons don't matter. Maybe my colleague can carve out some good work and can develop some great relationships. But, he's either talking about a group, or a team that's not working well together. Danger!!

Common CV Mistakes

April 15, 2009 6:42 PM
cv-times-new-roman.pngJust about everybody uses Times New Roman. It's the default for Microsoft Word, and although it's perfectly serviceable as a typeface, there are better choices. Perhaps as someone with graphic design and typography training, I'm biased - but steering clear of the default is always a good way to make your CV more distinctive.

I'd stick to serifed typefaces for most purposes - there is a wealth of professional looking, readable faces suitable for using in a CV. Classics such as Garamond or Caslon are good, but delve into your font collection and suit what suits your needs and image best.


cv-12-pages.pngLong CVs, along with the closely related CVs-set-in-a-6pt-font, are not the best way to present yourself, even if you do have a massive repertoire of skills. If a CV is too long, you can pretty much guarantee it won't be read - 2 pages is the standard allowance, and works just fine for most people. If you find yourself slipping into smaller font sizes to make it fit, or you are considering going to three pages (or beyond) - you might want to cut out some of the content.

cv-decorated.pngThere's nothing wrong with a well presented CV - sometimes tasteful improvements to an otherwise standard CV can be effective. But don't be tempted to embellish needlessly - black and white is fine for CVs, so there's no need to incorporate coloured headings or - worse still - word art!

cv-18pt-font.pngBig fonts are a fairly clear indicator of a lack of CV content. For a recruiter who's sifting through CVs set in 11pt Times New Roman all day, anything set in 15pt or higher will appear huge - and light on content if there's only one or two pages. Usually the problem is including too much irrelevant information, but if you're struggling to fill two pages it may be better to go to a single page - or incorporate some additional relevant skills, experience or education you may have forgotten about.

cv-spelling-errors.pngFew things put off potential employers more than someone who claims to have 'excellent language skills' and 'an eye for detail', while the CV is riddled with errors. It's not hard to double check two sheets of paper for any errors - a 5 minute proof read may pick up a couple of glaring errors and ensure your first impression is a good one.

I realize that many people are hunkered down, working hard at their jobs. And, a bunch of people are unemployed, looking for work. But what about all those people who are still employed but are unhappy and want to look for a job? How open can they be?

I'm from the school of "be honest with your boss" while you are looking. Somehow, I always managed to send my resume to people who were friendly with my bosses! And, once you've found a job, give two weeks notice. But if you're too scared to be honest with your boss, try these ideas:

  • As you update your social networking sites, say that you're open for any and all contacts: reconnecting, networking to help other people, and interesting options.
  • As you tell people that you are looking for a job, also explain you do not want to put your current job in jeopardy.
  • Make sure you use reputable recruiters. The disreputable ones will send your resume to everyone they know. The reputable ones focus your search.
  • Only send your resume to a company that's honest about who they are. Never send a resume to a cloaked ad.
If your boss discovers you are looking, come clean--at least, about your job search, if not the reason behind it.

It's not easy to find a job, but they are out there.

Skill Acquisition Processes

April 6, 2009 4:00 PM
Learning new skills is a great way to improve your career prospects - but it isn't quite as simple as completing a course or reading a book from cover-to-cover. These techniques are great at laying the cornerstones of competency, to become fully skilled in an area of expertise will require three phases.

The first is to establish the key structures of the skill - to understand a topic, you must first establish the breadth of the subject, any allied skills, and build a basic understanding of the key principles involved. From here, the second stage is to establish a self-contained understanding of the core skills, and develop the ability to research and resolve any problems you may have in implementing the skill. Finally, the latter process of skills building is refinement - slowly honing and expanding the scope of your knowledge as you use it in a professional capacity.

skills-aquisition-process.png
Key Structure Development

Books are a good way of getting a solid overview of a particular subject area. With high information density, they can be hard to digest at first but persevere and you'll be rewarded with a solid base in your chosen topic. Even skim reading can be beneficial if you seek to build a lighter understanding upon which to build later.

Manuals are similar to books, but are generally a little more prescriptive and serve more as a reference for all skill levels. Although more useful as a reference for intermediary learning, having a complete technical reference can be very useful in becoming acquainted with any technical subject.

Tutorials are perhaps the best tool available for the self-directed learner. Whether from a book, magazine or the internet, an introductory step-by-step method of teaching is (in my experience) the best way to break down the mystery of an unfamiliar subject.

Education and training - or any other directed learning (workshops, presentations etc.) - are great ways of sowing the seeds of knowledge for a given subject. Although they usually come at a price, directed courses as part of a college course or university degree can provide a great foundation of skills - and are structured in such a way that can't be paralleled by self-tuition.

Don't despair if your university days are in the past - there are still plenty of courses available as night classes or via distance learning - and no doubt your local college will have a comprehensive listing as to what is on offer. For some, self-directed learning isn't the preferred means of broaching a new skill, so taking an introductory course can really help you get started.

Skills Independence

Once the foundations of a skill have been laid, the key to maturing the skill into something upon which you can leverage in your career is to develop usage of the skill independent to any tutorial, or prescribed manner.

Self-directed experimentation
refers simply to unguided usage of the skill in question - for instance, if you are taking up web design, you could develop your skills to a more advanced level using the basic skills you have already acquired by embarking on your own projects - setting up a web site of your own, for instance. This usage outside of the structure of a tutorial or book will help cement it in your mind.

Perhaps more importantly, going it alone on your own projects you will eventually run into something with which you haven't dealt with before - problem solving is one of the key things to get right if you plan to work in IT - if you don't like the idea of running into problems in a daily basis, a career in IT may not be the best choice!

Essentially problem solving comes down to knowledge of the resources available to you within a certain skill domain, and the method through which to find your solution. As with so many things in life, Google is your friend - if you become stumped by an error message a web search may very well resolve your problem.

Refinement

On-the-job exposure
refers to simple everyday usage of a given skill - anything you work with will slowly become second nature as you are exposed to it over time. It is this applicative usage of you skills which is the key part of turning the core skills you have learned into finely tuned ability.

Once your skills are more mature, using blogs and the internet can be a great way to keep up with the latest trends, tips, techniques and foibles within your area of expertise. While regular usage as part of your job may exercise the main areas of your expertise, in order to explore new and developing parts of your skill set you will need to keep on reading and learning from external sources. There are many blogs out there dedicated to niche programming (and other IT-related) topics - keeping up to date will keep you ahead of the curve. You may even consider starting your own blog or resource site, if you have knowledge to share!

It's an experience

April 3, 2009 10:31 AM

Gaining experience during a period when the number of readily-available jobs is steadily declining may seem easier said than done, the importance of this seemingly obvious step cannot be overestimated. Although skills and knowledge are very important elements to building a strong CV, an increasing number of employers are looking at practical experience within a relevant field or role as an equally important factor in choosing the right candidate for a job.

For university students or fresh graduates, the process of gaining relevant experience may seem easier as placement schemes can be a good way to get a foot in the door to the IT departments of some great companies. While the pay is rarely significant (and in many cases is non-existent) for these roles, having relevant, real-life experience within a business environment adds considerable value to a CV which will stand candidates in good stead throughout their career.

For those already in jobs, the process may not be as straightforward but can be very rewarding, both from a CV-building perspective but also as a networking exercise. In many cases, employers may be quite willing to let existing employees take ownership of projects or additional responsibilities that would otherwise require them to bring in additional, external resources that they can ill afford. For an employee, this is not only a great way to prove their worth to their current employer but also a chance to build up their credentials for when the next job-hunt begins.

Current Vacancies from CWJobs

(* Required field)










Preferred format
   
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4