Thursday, 30 April 2015
As promised, we would like to provide the answer to the Easter egg hunt competition and announce the winner. Exactly seven hours after publishing the blog post we received a comment with the correct answer. The author of the comment was Matt Swain, who runs his blog about cheminformatics.
You can verify the correctness of his answer by visiting the password protected link in the original post. The password is:
Congratulations to Matt!
Thursday, 9 April 2015
We are pleased to announce a new round of resource-specific webinars that will be given in May and June 2015. These four webinars will cover UniChem, ChEMBL, MyChEMBL (the ChEMBL Virtual Machine) and the ChEMBL Web Services.
- UniChem, 4pm BST, 13th May 2015 Register Here
- ChEMBL Walkthrough, 4pm BST, 20th May 2015, Register Here
- MyChEMBL Walkthrough, 4pm BST, 10th June 2015, Register Here
ChEMBL Web Services, 4pm BST, 17th June 2015,Currently Postponed
For those of you who can't make these days/times, each 1 hour long webinar will be video recorded and will be available to watch on YouTube afterwards. Additionally, we will make the slides available for download.
For more information about the webinars, or to suggest other topics to cover, please contact email@example.com.
Wednesday, 1 April 2015
Easter is coming and for all those, who don't know what to do with their spare time and fancy entering a little competition, we've prepared a small challenge.
In software development, an Easter egg is funny (but harmless) and undocumented feature hidden from users in unusual places. Excel 97 has its Flight Simulator, FireFox about:robots address and Debian's apt-get has a moo command. The ChEMBL web services has now joined this list and we invite you to find its hidden feature and share with others.
We would like to encourage you to look at the source code of our web services. Reading code is essential developer skill, as it helps in understanding how the code works. This can lead to the development of new software and/or improve an existing codebase. After skimming through the code, hopefully you will agree that it is well written and easy to extend. Let us know if you disagree, either by emailing us or creating a GitHub issue. We promise, there are no dragons there, only an Easter egg, which should be easy to find after reading the code.
The first person to comment on this post with a URL revealing the Easter egg (web service URL, hmm hint maybe?), will be honoured with a mention in a future blog post. As a 'guarantee', that the Easter egg exists now, we provide the following password protected URL - we will reveal the password, the winner and more details in the follow up blog post. Do you think you can do it? Check it out!
Is this an April fool joke?
No. The joke is in having an Easter egg, not in finding it.