Claude Code is an agentic coding assistant by Anthropic that integrates directly into the terminal, helping developers understand, edit and manage their codebases via natural language commands. After installing Node.js 18+ and Claude Code, users authenticate with their Anthropic Console account to access features such as file editing, bug fixing, codebase querying, Git operations, test execution and deeper project analysis, all within a secure environment. Designed for macOS, Ubuntu, Debian, and Windows via WSL, Claude Code employs a tiered permissions system, comprehensive memory management for persisting preferences, and built-in tools for code search and modification, while providing robust safeguards against command injection and other security risks. Customisable at both global and project levels, it supports automation in CI pipelines, accommodates various shell environments, offers Vim mode, cost tracking and model selection, and is compatible with Amazon Bedrock, Google Vertex AI, proxies and devcontainers. Privacy is emphasised, with limited retention of feedback data used solely to improve functionality and not for model training. Extensive configuration, troubleshooting and notification options ensure adaptability and usability for individual developers and teams.
While ActiveState has moved on from its Komodo and OpenKomodo editors, you still find the cod on GitHub. With all the other options out there, it is difficult to see why anyone would use these tools, save for an escape from the incessant onset of AI into everything we do.
It’s astonishing what a misplaced wp-config.php file can cause. Today, one ended up travelling in here while I was setting up a test blog for seeing how WordPress 2.7 was coming along. The result was that content more appropriate to my hillwalking blog turned up on web browsers and in feeds instead of what should have made its appearance. I’ll have to be more careful in future…
P.S. I realise that I have been quiet over the last few weeks, but that’s down to my being away in Scotland hiking on some of its islands and catching up with some friends in Edinburgh. I have some ideas for new posts, so they should manifest themselves sooner rather than later.
In delivering an overview of the current state of statistical programming recruitment, it's evident that the field is experiencing rapid transformation driven by increased complexity in clinical trials, heightened regulatory expectations, and technological advancements. The demand for programmers skilled in multiple languages beyond SAS, knowledgeable about automation and AI integration, and experienced in handling real-world evidence is rising. To remain competitive, companies must adapt their recruitment strategies to attract candidates with both technical proficiency and the capacity for cross-functional collaboration. This means prioritising those who can manage complex data, ensure regulatory compliance, and collaborate effectively across teams. Moreover, employing a balanced approach between permanent hires and contract specialists will provide the flexibility needed to meet high-demand projects whilst maintaining core expertise for ongoing operations. Companies that align their hiring processes with these evolving needs will position themselves to navigate regulatory shifts and technological advancements successfully, ensuring data integrity and timely project execution in a competitive landscape. Engaging specialist recruitment services can be instrumental in identifying candidates who meet these exacting standards, thus helping organisations build robust and future-ready statistical programming teams.
When securing database credentials in R, several methods are available in order of preference. Integrated security with a DSN is optimal as it requires no plaintext credentials in code. Without a DSN, you can still use integrated security by passing connection settings as arguments. For storing credentials, the keyring package utilizes your operating system's credential storage (Keychain on macOS, Credential Store on Windows, Secret Service API on Linux) to securely encrypt and retrieve credentials. The config package allows credentials to be stored in a separate config.yml file. Environment variables can be set in the .Renviron file and retrieved with Sys.getenv(). Base R's options() function can store credentials temporarily during a session. As a last resort, the RStudio IDE can prompt users for credentials with masked input. Each method has different security implications and implementation complexity, but all aim to keep sensitive information out of plaintext code.
After checking in with R again as part of getting client work on the go once more, I went about setting up R and RStudio on a new machine. It was when I tried to add packages that things did not proceed so smoothly. It turned out that there were system dependencies that were missing. The combination of a console showing red against black and a lot of output made the problem difficult to spot. Handily, AI had a use here, and Google Gemini is turning out to be very useful when I have some debugging to do. All got sorted on this occasion; it might help to harvest a list of packages, so I have them for future reference.
The January 2025 release of Visual Studio Code, version 1.97, brings numerous updates and enhancements aimed at improving coding efficiency and security for developers. Notable features include GitHub Copilot's Next Edit Suggestions, which predicts coding edits, and enhancements in workspace management, such as a repositionable Command Palette and enhanced log filtering capabilities. The update introduces significant security features like extension publisher trust and compound log views for better log analysis. Developers can now debug Python scripts without setup and benefit from advanced git blame functionalities and support for various source control actions. Accessibility features have also been refined, enhancing sound clarity and adding keyboard shortcuts for easier navigation. The update further includes support for customisable terminal settings, enhanced debug capabilities, and diverse improvements in documentation and syntax highlighting. Remote development is also enhanced with better SSH configuration, and contributions from the community have helped streamline the codebase and improve the development workflow.