A Tale of Two Job Specifications 👍👎 Recently I came across two job specifications for roles that were broadly related to data and information systems . On the surface they looked similar enough, both requiring analytical thinking, technical skills and the ability to support organisational objectives. However, once I started reading them closely, the difference in quality between the two documents became immediately obvious. One specification was so vague that I found myself writing comments all over it in red, while the other provided genuine insight into the role and the technologies involved. It was a perfect example of how a well-written job specification can help both employers and candidates. The first job specification described the responsibilities of a Senior Analyst role. It contained plenty of corporate language about supporting stakeholders, analysing data, promoting service improvement and contributing to organisational objectives. While none of these requirements we...
Is It Time to Move On From VS Code? VS code VS Pycharm/ For the past few years, Visual Studio Code has been my primary development environment. Like many developers, I appreciated its flexibility, extensive plugin ecosystem, and the fact that it could be adapted to almost any programming language or workflow. However, after one of the recent updates, I found myself spending more time fighting with the IDE than actually writing code. What was once a lightweight and straightforward editor now felt increasingly cluttered and distracting. The biggest issue for me wasn't that new features had been added. Software evolves, and that's a good thing. The problem was that VS Code seemed to be constantly trying to anticipate what I wanted to do before I'd even clicked on anything. Panels would appear, suggestions would pop up, AI features would offer advice, and various automated tools would spring into action. While some developers may find this helpful, I found it disr...