#text-based-procedures

#text-based-procedures

The query_one() method throughout the Textual documentation allows users to retrieve a single widget that matches a CSS selector or a widget type. You can pass in up to two parameters to query_one(), which are the CSS selector and the widget type, or both at the same time.

Voice interaction with Claude Code significantly enhances the user experience by allowing for faster input. Speaking is often 2-3 times quicker than typing, which can streamline the process of giving commands.

CLAUDE.md = "project brain" Skills = "reusable capabilities" The way I think about CLAUDE.md and Skill is this distinction. Think of CLAUDE.md as "Everything Claude needs to know about this particular project." If, when thinking about a particular detail, you start your thought with "In this project..." or "For this project..." then this information belongs in CLAUDE.md.

Instructions I created. Instructions I am continuing to hone - instructions that required me to study my own old essays, identifying what I do when I write. The sentence rhythms. The way I move between timescales. The zooming in and out from concept to detail. The instructions tell Claude how I would like ideas composed. I pull together concepts and experiences from my lived expertise to formulate a point of view - in this case, on this new AI technology.

This extends to the software development community, which is seeing a near-ubiquitous presence of AI-coding assistants as teams face pressures to generate more output in less time. While the huge spike in efficiencies greatly helps them, these teams too often fail to incorporate adequate safety controls and practices into AI deployments. The resulting risks leave their organizations exposed, and developers will struggle to backtrack in tracing and identifying where - and how - a security gap occurred.

As a contracting front-end developer and Design Systems consultant, I don't always get to work on new things. Sometimes I work within codebases. Sometimes alongside them. Sometimes these codebases are years and years old. When you dive into these projects, you're not just reading code, you're excavating years of decisions, technological limitations, and creative workarounds from days gone by. Over the last decade, I've called this Front-End Archaeology.

One thing I always do when I prompt a coding agent is to tell it to ask me any questions that it might have about what I've asked it to do. (I need to add this to my default system prompt...) And, holy mackerel, if it doesn't ask good questions. It almost always asks me things that I should have thought of myself.

The recently updated SWEBOK Guide v4.0a represents a needful industry standard, following a thorough peer review and a consensus-based approach. With the rise of AI, a significant skills gap in IT and cybersecurity is emerging alongside changes in the global workforce. There has never been a greater need for a consensus-based framework. This guide, created and thoroughly reviewed by industry professionals, serves as a dynamic and evolving resource.