I’m in the process of migrating my blog to a new domain, and will no longer be posting at this address. Please check out http://stuartgunter.org for my new blog and to keep up to date with my posts.
Thanks for reading!
I’ve recently been involved in a number of interviews for our growing team at Betfair, and have been surprised to see some commonly occurring mistakes in some of the CV’s. Given the vast number of free resources online that advise job-seekers on how to write an effective CV, it’s somewhat disappointing to see some of these issues still plaguing us. This is not intended as a criticism of those that have submitted CV’s – in fact, a number of them have been very good! This is simply another one of those free resources that I’m hoping will be helpful to someone.
#1 Think like the interviewer
It’s very easy to get consumed with the stress of updating your CV and forget that someone else needs to read it. You should constantly try to read your CV as though you were the interviewer, and then fix anything that doesn’t make sense or appear to add value.
#2 Your CV is your personal brochure, not your biography
I can’t speak for anyone but myself on this point, but I generally tend to focus on the first two pages of any CV. That should typically include your skills, education, most recent work history (2 most recent positions/projects). Everything of value should be on those two pages. It’s not that the interviewer doesn’t care (we really do!) – it’s that we seldom have the time to read an extensive CV. Bullet points are always preferred over paragraphs… this can’t be emphasized enough.
#3 Acronyms… friend and foe
I’ve been amazed at the number of CV’s that include “private” acronyms – in other words, acronyms that only people in your own organisation will know. These are typically acronyms for systems that have been worked on, or internal tools that are used. While acronyms can make a CV much easier to read, you should be careful not to assume prior knowledge by the interviewer. If you need to use private acronyms, make sure you introduce them first… and only introduce them if you intend on using that acronym later. You don’t want to give the interviewer a StackOverflowException (sorry, lame programmer humour).
#4 Avoid technology shopping lists
Try to avoid listing an excessive number of technologies on your CV. It might be true that you’ve had some exposure to loads of different technologies, but try to describe those that are most applicable to the position you’re applying for. Admittedly, you may not always know which those are – but if your CV lists more technologies than some of the job postings on JobServe, you should probably cut it down a bit. Again, this is not to say that you should downplay your experience. But it’s highly unlikely that you’re an expert on everything. If you feel it is important to list them all, try order them for the interviewer. It’s nice to know what you consider your major strengths and what you’ve only dabbled in. It’s great when you see that someone has enough interest in their career that they’ve chosen to learn 10 different languages, but try let your CV demonstrate both the depth and breadth of your knowledge.
#5 Get someone to proofread it
Every interviewer will be looking for something different, but it’s almost certain that communication skills are high on their lists. With that in mind, you absolutely must get someone to proofread your CV before submitting it. Spelling mistakes, poor grammar, incomplete sentences and poor punctuation are all too common and they detract from creating a good first impression. This is not to say that you will be judged purely on these grounds, but getting them right will certainly help. But you’re a programmer, not an author… right? Wrong! You will be called on to explain your ideas and present your (or your team’s) work at some point, and you need to be able to convey it well. A CV that is poorly constructed and full of mistakes doesn’t inspire confidence in the candidate’s attention to detail. And that same attention to detail is often what helps make a great programmer.
These aren’t really ground-breaking revelations in the art of CV-writing, but I think they’re the common sense advice that we all need from time to time. I hope this has been helpful, and happy hunting.
And while I’m on the topic – if you’re a great developer, passionate about what you do, and keen to join an excellent team… check out the positions we have available!
Having just finished reading Steve Souders’ High Performance Web Sites, I thought it would be helpful to point out how some of the server-side rules can be configured on SAP NetWeaver.
PS: Buy the book! It’s short and to the point, and very well written. I’ve already ordered his follow-up book Even Faster Web Sites to be delivered today!
The book covers 14 rules for improving performance on web sites, concentrating mostly on front-end optimisations that can dramatically improve the responsiveness and user experience of your site. However, some of the rules involve changes on the server – for example, enabling gzip compression. The full listing of the Yahoo! Performance Rules can be found here.
Below is a brief summary of how to configure some of these rules in SAP NetWeaver. I’m using NetWeaver CE 7.1, so you may need to adjust these slightly if you’re running a different version. All configuration is done within NetWeaver Administrator > Configuration > Infrastructure > Java System Properties > Services, so I’m only going to mention that once to avoid repeating it many times over. I’ve also made an effort to reference the SAP Help docs that I’ve used to compile this summary, which you should find at the end of each section.
Rule: Add an Expires or a Cache-Control Header
The first thing to point out here is that NetWeaver has two cache control settings: one for the server and one for the client. Before understanding how to configure each of these, you need to know what it is that you’re configuring and the implications of the changes you’re about to make. I’ve included a diagram from the relevant SAP Help page (full reference below) to show the architecture of the ICM Server Cache.
The full explanation that accompanies this diagram can be found here: https://cw.sdn.sap.com/cw/docs/DOC-107069
Right… now that you have a better understanding of how caching works on the server, you’re ready to configure it. I assume you’re already familiar with the standard HTTP Cache-Control header, but refer you to the full explanation here if not: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
In order to change the cache configuration, you need to find the HTTP Provider Service in NetWeaver Administrator and modify the following properties:
SapCacheControl – This should be set to the expiration period (in seconds) of the cached resource.
CacheControl – This can be set to any of the cache-response-directive values specified in the HTTP Specification (see link above for a reference to the section on Cache-Control).
You could argue that the server-side cache isn’t exactly what Steve Souders was talking about in his book – but when reading the documentation on the SAP Help site, you’ll see that the SapCacheControl value is also used as the Cache-Control max-age response directive… so it will have an impact on the cache status of web resources.
SAP Help Reference: https://cw.sdn.sap.com/cw/docs/DOC-100645
Rule: Gzip Components
Enabling gzip compression is fairly straight-forward. Just find the HTTP Provider Service in NetWeaver Administrator and modify the following properties:
AlwaysCompressed – This is a list of all the file extensions or MIME types that should always be compressed.
NeverCompressed – This is a list of all the file extensions or MIME types that should never be compressed.
CompressedOthers – Boolean value to indicate whether all other file extensions or MIME types (i.e. those not listed in either AlwaysCompressed or NeverCompressed) should be compressed.
MinimumGZipLength – Specifies the minimum size required for gzip compression to be applied. This property works in conjunction with AlwaysCompressed and CompressedOthers (i.e. the resource must be listed for compression AND larger than MinimumGZipLength in order to be compressed).
Note: File extensions must be in the format “*.ext”. Any entries without an asterisk will be treated as MIME types.
SAP Help Reference: https://cw.sdn.sap.com/cw/docs/DOC-111485
You can also dynamically enable compression for Servlet / JSP responses by passing special headers in the response. These headers are not sent to the client, but rather instruct the HTTP Provider Service to compress the response before sending it on to the client. These headers override the HTTP Provider Service configuration described above. If specified, the presence of these headers will force the HTTP Provider Service to either compress or not compress the response – regardless of what is configured elsewhere.
The header values themselves are configurable within the Web Container Service, and are described as follows:
HeaderForCompression – Specifies the header name that must force compression when present in the response
HeaderForNoCompression – Specifies the header name that must prevent compression when present in the response
To use this in your Servlet / JSP, simply set the relevant header to “true”.
SAP Help Reference: https://cw.sdn.sap.com/cw/docs/DOC-100076
Rule: Configure ETags
ETags are very elusive within the SAP Help docs. Despite much trawling, I could only come up with a few minor references to indicate that it exists – however no details could be found. I did find a SAP Note that mentioned a fix to ETag functionality in NW 7.0 – see Note 1020365.
If anyone manages to come across more information on this, please post a comment. I’d be interested in finding where it can be configured.
While making all these configuration changes, it’s not hard to see that NetWeaver Administrator is lacking the user-friendliness that it should offer to administrators. It a fairly poor means of managing a system as it has been built to be as generic as possible. Unfortunately, in this case it means that there’s a lot it just doesn’t do very well because it’s trying to cater for everything in one go. To illustrate my point, simply try to modify the list of MIME types within the HTTP Service (see Mime property). This list is likely to be very long, regardless of how you configure it. What do you do if you want to add one extra MIME type? Well, in that case you need to copy the list already there and paste it into Notepad, add the item you want, then re-insert the entire list into an input field only wide enough for about 20 characters. To put that into perspective, the default list of MIME types is just under 4000 characters long. Not only is the input field far too small, but surely an administrator should be able to modify the existing list rather than recreating it to make a small change? Even worse than this is the fact the modified property text is not wrapped in the table cell. So if you do decided to add a MIME type, you lose all visibility of what has been configured as you can only see the first few characters before they disappear. I can’t say I’m surprised though. Usability has never been something that SAP do well… or at all, for that matter. However, taking visibility of the configuration of a system away from the administrator is a very dangerous thing to do. This issue very clearly illustrates how poor usability can have very far reaching consequences, and why it is so important to get it right!
This is by no means a comprehensive review of the how’s and why’s of each of these rules, nor does it go into much detail about each system property described. I intentionally kept this fairly straight forward so it can serve as a reference guide, and have instead provided links to more detailed documentation wherever I can. After all, the links are where I got the information in the first place – so it’s only right to give the original author full credit for it. I’m just hoping to save some of you time in finding the right resources.
I hope this has been helpful, even if it was nothing more than a prompt to look into other areas where NetWeaver can be configured to operate according to what you need.