When and Why to Use XML

According to the XML Litmus Test, XML is the appropriate tool for the job if the following criteria are satisfied by choosing XML as the data representation format for a given application:

  1. There is a need to interoperate across multiple software platforms.
  2. One or more of the off-the-shelf tools for dealing with XML can be leveraged when producing or consuming the data.
  3. Parsing performance is not critical.
  4. The content is not primarily binary content, such as a music or image file.
  5. The content does not contain control characters that aren't carriage return, line feed, or tab because they are illegal in XML.

Comments

Post a Comment

Popular posts from this blog

30+ GitHub Products & Key Ecosystem Features You Should Know in 2026

Image
GitHub has grown far beyond a place to host code — today it's an entire ecosystem covering CI/CD, AI-assisted development, security, package management, and team collaboration. Whether you're new to the platform or just want a single reference point, here's an alphabetical list of GitHub's major products and features, each linked to its official page - GitHub Actions GitHub Advanced Security GitHub Apps GitHub CLI GitHub Code Review GitHub Code Security GitHub Codespaces GitHub Container Registry GitHub Copilot GitHub Copilot Business GitHub Copilot CLI GitHub Copilot Enterprise GitHub Copilot Extensions GitHub Dependabot GitHub Desktop GitHub Discussions GitHub Education GitHub Enterprise Cloud GitHub Enterprise Server GitHub Gist GitHub Importer GitHub Innovation Graph GitHub Issues GitHub Marketplace GitHub Mobile GitHub Models  (retiring July 30, 2026) GitHub Packages GitHub Pages ...
Read more

Uncle Bob vs. Grady Booch: Rethinking Code Reviews in the Age of AI

Image
In response to a question about the feasibility of effective code reviews for large (e.g., 500-line) AI-generated PRs like those from Claude, especially when reviewers lack deep codebase familiarity in new projects or fast-paced environments, Uncle Bob Martin and Grady Booch have contrasting views Uncle Bob Martin advocates metrics-based oversight (test coverage, complexity, dependencies) and higher-level management over line-by-line AI code review, while Grady Booch stresses manual verification for vulnerabilities, dead code, and performance factors. Uncle Bob Martin : " I don’t review code written by agents . I measure things like test coverage, dependency structure, cyclomatic complexity, module sizes, mutation testing, etc.  Much can be inferred about the quality of the code from those metrics. The code itself I leave to the AI.  Humans are slow at code. To get productivity we humans need to disengage from code and manage from a higher level." Grady Booch : "Unlike B...
Read more

This Week I Learned - Week 30 2026

Image
This Week I Learned -  * The OpenRouter Pareto Router is a dynamic model selection tool that allows users to select a coding model based on a minimum coding score preference. It maintains a curated shortlist of strong coding models ranked by Artificial Analysis coding percentiles. Users can set a min_coding_score between 0 and 1 to control the strength of the coder they need. The router automatically selects the cheapest model within the chosen tier or the fastest with the Nitro variant. This approach ensures that users receive a strong coder without overspending, as the exact shortlist evolves over time with new models and benchmarks. The OpenRouter API is compatible with most SDKs, allowing for easy integration into applications. * openrouter/auto-beta is a task-aware router. It classifies each request, routes it to the model teams are actually spending on for that kind of task, and filters that choice by the cost-quality tradeoff you set. The response is priced at the routed mo...
Read more