# hooks Published articles for hooks. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Rider and ReSharper 2026.2.2 Are Out! DevFeed: [Rider and ReSharper 2026.2.2 Are Out!]() Original publisher: [Read original article]() Author: Alexander Kurakin Published: 2026-09-16T14:12:44Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [rider](), [resharper](), [AI-assisted coding](), [test-coverage]() Tags: [2026](), [ai-agent-hooks](), [ai-agents](), [code-coverage](), [coverage](), [hooks](), [jetbrains](), [macos](), [mcp](), [net](), [net-tools](), [releases](), [resharper](), [rider](), [update]() ### AI overview JetBrains releases Rider, ReSharper, and .NET tools 2026.2.2, adding an AI Agent Setup widget in Rider, more targeted hook feedback for coding agents, TUnit coverage support, and fixes including a macOS freezing issue. ### Source excerpt We've released version 2026.2.2 of ReSharper, Rider, and .NET tools. You can install this update from inside the tools themselves, through the Toolbox App, or on our website. Here's what's new in this update. Rider 2026.2.2 AI Agent Setup widget We've recently added a wide range of features to help you work with coding agents [...] ## Ensuring transaction-safety in Google App Engine DevFeed: [Ensuring transaction-safety in Google App Engine]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-06-27T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Transactions](), [Databases](), [Code](), [Google]() Tags: [cache](), [code](), [database](), [engineering](), [google](), [hooks](), [infrastructure](), [news](), [tracing](), [transactions]() ### AI overview The article explains how Khan Academy uses transactions and user-write locks with Google App Engine to prevent database corruption caused by concurrent requests overwriting one another. It describes hooks that detect transaction-safety violations and highlights caching and code-path mistakes that can cause stale data to be used inside transactions. ### Source excerpt By Craig Silverstein In last week's exciting post, I described an alternative to transactions that we use at ... Read more ## Build with Claude Code: Enrollment for a Two-Day Cohort Course DevFeed: [Build with Claude Code: Enrollment for a Two-Day Cohort Course]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-15T19:31:01Z Content type: article Language: en Sources: [ByteByteGo]() Topics: [Claude Code](), [Development](), [Code](), [Git]() Tags: [build](), [claude-code](), [code](), [development](), [git](), [hooks](), [how-to](), [learn](), [mcps](), [parallel]() ### AI overview The article announces the relaunch of Build with Claude Code, a two-day cohort-based course taught by John Kim. It covers Claude Code fundamentals and production workflows, including context engineering, memory, Skills, MCPs, hooks, Git worktrees, subagents, and agent teams. ### Source excerpt We're relaunching Build with Claude Code, a 2-day intensive cohort-based course taught by John Kim, who has trained hundreds of engineers at Meta to use Claude Code in real production workflows. ## How I Run My 1.5M+ Follower Content Business With Codex | Riley Brown DevFeed: [How I Run My 1.5M+ Follower Content Business With Codex | Riley Brown]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-08-16T14:03:09Z Content type: article Language: en Sources: [Behind the Craft]() Topics: [codex](), [Artificial Intelligence]() Tags: [ai](), [codex](), [create](), [follower](), [hooks](), [uses]() ### AI overview Riley Brown's article describes how he uses Codex within his AI stack to research topics, write video hooks, and create thumbnails for his content business. ### Source excerpt Riley revealed his full AI stack including how he uses Codex to research topics, write video hooks, and create viral thumbnails. ## The npm worm that installs itself into your coding agent DevFeed: [The npm worm that installs itself into your coding agent]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T15:20:55Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [npm](), [Claude Code](), [Visual Studio Code](), [GitHub](), [JavaScript](), [Command-line interface]() Tags: [agent](), [claude-code](), [code](), [github](), [hooks](), [npm-worm](), [repo](), [shai-hulud](), [vscode](), [worm]() ### AI overview The article analyzes a Shai-Hulud npm worm that plants executable hooks in .claude/settings.json and .vscode/tasks.json. Opening a compromised repository can trigger the payload in VS Code or Claude Code, creating an attack path that install-time defenses may not detect. ### Source excerpt A Shai-Hulud wave plants hooks in .claude/settings.json and .vscode/tasks.json, so opening a repo runs the payload. Agent config is executable surface now. ## Scheduling Claude Code for Nightly Repository Maintenance DevFeed: [Scheduling Claude Code for Nightly Repository Maintenance]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-07-28T12:03:08Z Content type: tutorial Language: en Sources: [Eric Roby]() Topics: [Claude Code](), [Security](), [Refactoring](), [ci](), [hooks](), [Code]() Tags: [automated](), [ci](), [claude-code](), [github-action](), [hooks](), [how-to](), [refactor](), [repo](), [security]() ### AI overview The article explains how to schedule Claude Code in headless mode for recurring repository maintenance. It recommends focused jobs for security sweeps, refactoring scans, and enhancement reviews, using structured JSON output and the --bare option for consistent scripted runs. ### Source excerpt How to schedule headless runs for nightly security sweeps, refactor scans, and enhancement ideas ## AI Coding Tip 027 - Force Code Standards DevFeed: [AI Coding Tip 027 - Force Code Standards]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-07-10T14:24:14Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [pull-requests](), [Language models]() Tags: [agents](), [ai-coding](), [analysis](), [code](), [coding](), [harness](), [hooks](), [how-to](), [large-language-model](), [linter](), [pull-request](), [reviews](), [skills](), [trust](), [windows]() ### AI overview A tutorial on enforcing coding standards in AI-assisted development. It recommends converting prose standards into machine-checkable rules, running them through hooks and validator skills, and using an LLM judge for ambiguous semantic violations before code reaches human review. ### Source excerpt TL;DR: Wire your standards into hooks, skills, and a judge, so the harness blocks violations before a human opens the diff. Common Mistake ❌ You paste your coding standards into AGENTS.md and trust t ## Introducing Kempt DevFeed: [Introducing Kempt]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-06-23T00:00:23Z Content type: release Language: en Sources: [Zac Sweers]() Topics: [formatting](), [pre-commit](), [hooks](), [ci](), [repo](), [Java](), [Kotlin](), [Rust]() Tags: [ci](), [formatting](), [gradle](), [hooks](), [java](), [kotlin](), [open-source](), [pre-commit](), [repo](), [rust]() ### AI overview The article introduces Kempt, a small project designed to replace heavy Gradle-based formatting setups with a repo-local pipeline for formatting and commit hooks. It supports Kotlin, Java, and Rust, and can run locally, in pre-commit hooks, and in CI. ### Source excerpt Formatting should be boring, in the best possible way. ## What Did the Agent Just Push? Auditing Git for AI Agents DevFeed: [What Did the Agent Just Push? Auditing Git for AI Agents]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [Git](), [AI Agent](), [audit](), [Clash](), [hooks](), [repo]() Tags: [ai-agents](), [ai-coding](), [audit](), [eugene-petrenko](), [git](), [hooks](), [infrastructure](), [jonnyzzz](), [proxy](), [pull-request](), [repo](), [tag-41199d53f463](), [workflow]() ### AI overview This article presents an approach for auditing autonomous AI agents that work with Git repositories. It recommends keeping real credentials away from agents, using a Git proxy as a hard boundary to limit which branches can change, and using Git hooks as a lighter, best-effort layer for provenance and telemetry. ### Source excerpt When you hand a repo to an autonomous AI Agent, you need to bound what it can touch and capture what it did. Part 1 -- the approach -- keep the keys away from the agent, a git proxy as the hard boundary, and git hooks as the lighter alternative. ## Prompts Are Guidelines. Code Is the Config. DevFeed: [Prompts Are Guidelines. Code Is the Config.]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-08T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Artificial Intelligence](), [Prompt Engineering](), [Claude](), [API](), [hooks](), [JSON](), [context]() Tags: [agent-reliability](), [agents](), [ai](), [ai-agents](), [api](), [claude](), [hooks](), [schema](), [stateless](), [stop-reason](), [structured-output](), [til](), [tool-use]() ### AI overview A Today I Learned field note about building more reliable AI agents by assigning probabilistic judgment to the model and deterministic guarantees to application code. It discusses using code-enforced gates and hooks for requirements that must always hold, branching on stop_reason rather than model text, handling turns that contain both chat and tool calls, and avoiding the assumption that a valid schema guarantees a correct answer. ### Source excerpt Where the model's judgment ends and your code has to take over -- a Today I Learned field note on building AI agents that hold up in production: stop_reason, forced tool use, hooks, stateless history, and why a valid schema isn't a true answer. ## Build a Repository Harness for Claude Code Coding Agents DevFeed: [Build a Repository Harness for Claude Code Coding Agents]() Original publisher: [Read original article]() Author: Engin Diri Published: 2026-05-26T00:00:00Z Content type: opinion Language: en Sources: [Pulumi]() Topics: [Claude Code](), [AI-assisted coding](), [Tooling](), [Code](), [Command-line interface](), [MCP]() Tags: [ai](), [ai-agents](), [claude](), [claude-code](), [coding-agents](), [devops](), [extension](), [hooks](), [ls](), [mcp](), [perspectives](), [plugins](), [skills](), [tooling]() ### AI overview The article argues that, in real codebases, the context and tooling surrounding Claude Code can matter more to performance than the underlying model version. It presents a repository-level AI harness built from seven components, including CLAUDE.md, hooks, skills, plugins, LSP, MCP, and subagents, and discusses agentic navigation without a separately maintained codebase index. ### Source excerpt Anthropic shipped a piece earlier this month called How Claude Code Works in Large Codebases. I have not read anything more useful about coding agents this year. The core claim, in their words: "the ecosystem built around the model--the harness--determines how Claude Code performs more than the model alone." In my phrasing: in a real codebase, the model is the smaller variable. The layer of context and tooling you wire around the agent matters more than which version of Sonnet or Opus is behind it. The post stays high-level, which is the right move for a launch piece. What I want to do here is land it. Same seven pieces, but with the wiring you would actually put in a repo, in the order I would put it. How Claude Code navigates without an index Anthropic's writeup says Claude Code works from the live codebase and does not require a codebase index to be built, maintained, or uploaded. The agent navigates the way an engineer would, with grep, find, ls, file reads, and reference-following. Anthropic calls this agentic search, and the upside is obvious: no separate index exists for you to keep fresh. The downside is also obvious. An engineer who has never seen your repo and only has shell tools will flounder if you drop them in the root with no map. That is your agent on day one. Everything that follows is about giving it the map. The AI layer in seven pieces Every codebase used to have two artifacts engineers cared about: the code and the tests. A third exists now. Call it the AI layer, or the harness, or whatever you want. This layer is the set of context and tools you give your coding agent to operate in this specific repo. Anthropic breaks it into seven pieces, and each one solves a different scaling problem. Anthropic gives each piece a role: CLAUDE.md is the foundation, hooks do self-improvement, skills are progressive disclosure, plugins handle distribution, LSP gives navigation, MCP is extension, subagents split exploration from editing. They are not equal in usag ## Accelerating Delivery: How AI Agents Can Own the Initial Code Draft DevFeed: [Accelerating Delivery: How AI Agents Can Own the Initial Code Draft]() Original publisher: [Read original article]() Author: Stephen Walker Published: 2026-05-05T21:58:00Z Content type: article Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Artificial Intelligence](), [Loop Engineering](), [Pull Request](), [human review](), [jira](), [coding](), [hooks](), [Script]() Tags: [agents](), [ai](), [ai-agents](), [ai-and-emerging-tech](), [code](), [hooks](), [human-review](), [jira](), [pull-request](), [review](), [sandbox]() ### AI overview The article describes a pragmatic workflow in which coordinated AI agents turn a Jira ticket into a code draft and pull request for human review. It emphasizes safety through branch permissions, scoped access, scripts and hooks, plus deterministic structures around probabilistic language models. The supplied text is truncated before the full reliability hierarchy and later conclusions. ### Source excerpt Why This Matters in the Era of Agentic Everything The gap between a Jira ticket and the first pull request (PR) is often a graveyard of productivity. Context switching, boilerplate setup, and requirement analysis can eat up hours of a senior engineer's day before they write a single line of business logic. Recently, industry leaders have showcased "Harness Engineering" [1][2] -- the practice of building autonomous agent workflows that handle end-to-end coding tasks. While their results are inspiring, the barrier to entry can feel insurmountable. The challenge for most teams is finding a starting point that balances long-term vision with immediate ROI. We recently helped a large-scale, high-traffic consumer services platform bridge this gap. Instead of an all-or-nothing architectural overhaul, we took a pragmatic first step: automating the journey from Jira ticket to PR. The Vision: "Let's work on FEAT-123" Our goal was simple. We wanted to enable a developer to provide a single prompt -- "Let's work on FEAT-123" -- and have a coordinated team of AI agents handle the planning, coding, and verification. This culminates in a PR ready for human review. To make this a reality, we focused on three strategic pillars: safety, determinism, and quality. Safety Through Pragmatic Guardrails One of the primary concerns for any engineering leader is "agent drift" -- an AI making unauthorized or hallucinated changes. While an isolated digital sandbox is an ideal long-term goal, we proved that teams can achieve significant safety and progress using existing infrastructure: Branch Permissions: Restrict agent access to specific feature branches. Scoped Access: Use scripts and hooks to define exactly what an agent can and cannot touch. Human-in-the-Loop: Ensure that while the agent proposes the change, a human must always review, approve, and merge the code. By defining the agent's scope as a specialized contributor rather than a system administrator, we mitigated risk while maximizing ou ## Harness engineering: Building reliable environments for AI coding agents DevFeed: [Harness engineering: Building reliable environments for AI coding agents]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-04-03T00:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Claude Code](), [codex](), [Model Context Protocol](), [hooks](), [Software]() Tags: [agent](), [claude](), [claude-code](), [codex](), [engineering](), [hooks](), [mcp](), [memory](), [skills](), [software]() ### AI overview This commentary argues that software engineering is increasingly focused on building reliable environments around AI coding agents. It describes harness engineering as configuring files, tools, skills, hooks, feedback loops, memory, guardrails, and blast-radius controls so agents can make changes safely and teams can trust them. ### Source excerpt The role of a software engineer is shifting. Not toward writing more code but toward building the environment that makes agents reliable. Think about what you actually do with Claude Code or Codex today: you configure AGENTS.md files, set up MCP servers, write skills and hooks, build feedback loops and tune sub-agents. You're not writing as much of the software anymore. You're engineering the harness around the thing that writes the software. Mitchell Hashimoto first coined the term harness engineering -- the work of shaping the environment around an agent so it can act reliably. What the model sees, what tools it has, how it gets feedback, when humans step in. We keep hearing that agents will replace engineers. That shouldn't be the focus of the change we're seeing. What's actually happening is product people shipping features directly. A well-harnessed agent lets someone with product instinct but little engineering background make meaningful changes -- safely. The harness engineer makes that possible. Guardrails, design choices, blast radius controls, feedback loops. The scaffolding that turns "just prompt it" into something a team can trust. I say this from first-hand experience. If you want to go deeper, listen to the episode where my cohost and I dug into it. We landed on five pillars: agent legibility closed feedback loops persistent memory entropy control blast radius controls Honestly one of the most important episodes we've recorded. ## The Engineer's Guide to AI-Assisted Productivity DevFeed: [The Engineer's Guide to AI-Assisted Productivity]() Original publisher: [Read original article]() Author: Alex Razvant Published: 2026-02-12T12:01:56Z Content type: article Language: en Sources: [Neural Bits]() Topics: [Artificial Intelligence](), [code productivity](), [coding](), [Pull Request](), [Claude Code](), [cursor](), [hooks](), [Obsidian]() Tags: [agent](), [ai](), [also](), [article](), [claude](), [claude-code](), [code](), [cursor](), [developer-productivity](), [guide](), [hooks](), [obsidian](), [open-source](), [productivity](), [pull-request]() ### AI overview This article argues that AI-assisted software development should prioritize design, planning, maintainability, and effective safeguards over raw lines of code. It presents habits involving Cursor Rules, Claude Code Skills, agent plugins, pull-request rules, reviews, hooks, and an Obsidian-based daily memory dump. ### Source excerpt Six habits that keep you fast and maintainable. Cursor Rules, Claude Code Skills, Agent Plugins, PR rules, non-nitpicky reviews, hooks, and Daily memory dump with Obsidian. ## Announcing Lix 2.94 "Açaí na tigela" DevFeed: [Announcing Lix 2.94 "Açaí na tigela"]() Original publisher: [Read original article]() Published: 2025-11-18T00:00:00Z Content type: release Language: en Sources: [News on Lix]() Topics: [Remote Procedure Call (RPC)](), [Cap'n Proto](), [Protocol (disambiguation)](), [implementation](), [hooks](), [Logging]() Tags: [announce](), [bugfixes](), [hooks](), [improvements](), [logging](), [performance](), [release](), [rpc](), [version]() ### AI overview Lix 2.94 is a major release focused on bug fixes, quality-of-life and performance improvements, with initial integration of the Cap'n Proto RPC runtime to replace a bespoke implementation. It includes Cap'n Proto protocol definitions for build hooks and logging, enabling multiple build hook processes to wait concurrently. ### Source excerpt We at the Lix team are proud to announce our fifth major release, version 2.94 "Açaí na tigela". This release focuses on bugfixes, quality-of-life improvements, performance improvements and started integrating Lix with the Cap'n'Proto remote procedure call runtime, in order to replace the previous bespoke implementation. ## Using Git Pre-Commit Hooks DevFeed: [Using Git Pre-Commit Hooks]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2025-10-20T15:00:00Z Content type: tutorial Language: en Sources: [Scott's Weblog]() Topics: [Git](), [Markdown](), [Bash](), [Script]() Tags: [aws](), [bash](), [cilium](), [cli](), [cloud](), [cni](), [code](), [containers](), [cri-o](), [devops](), [docker](), [git](), [git-commit](), [git-hook](), [go](), [hooks](), [iac](), [k8s](), [kubernetes](), [lint](), [linux](), [markdown](), [networking](), [oci](), [script](), [security](), [tests]() ### AI overview This tutorial explains Git pre-commit hooks and demonstrates using one to run Markdownlint on staged Markdown files before a commit. It notes that a non-zero hook exit status aborts the commit and presents a Bash implementation based on the author's site. ### Source excerpt A while ago I wrote an article about linting Markdown files with markdownlint. In that article, I presented the use case of linting the Markdown source files for this site. While manually running linting checks is fine--there are times and situations when this is appropriate and necessary--this is the sort of task that is ideally suited for a Git pre-commit hook. In this post, I'll discuss Git pre-commit hooks in the context of using them to run linting checks. Before moving on, a disclaimer: I am not an expert on Git hooks. This post shares my limited experience and provides an example based on what I use for this site. I have no doubt that my current implementation will improve over time as my knowledge and experience grow. What is a Git Hook? As this page explains, a hook is a program "you can place in a hooks directory to trigger actions at certain points in git's execution." Generally, a hook is a script of some sort. Git supports different hooks that get invoked in response to specific actions in Git; in this particular instance, I'm focusing on the pre-commit hook. This hook gets invoked by git-commit (i.e., the user running a git commit command) and allows users to perform a series of checks or tests before actually making a commit. If the pre-commit script exits with a non-zero status, then Git aborts the commit. Using a Pre-Commit Hook to Lint Markdown For my use case, I wanted to run Markdownlint to lint the Markdown files (as described in the previous article on linting Markdown) before the commit. To do that, I came up with the following script: #!/usr/bin/env bash MDLINT="/usr/local/bin/markdownlint" for file in $(git diff --cached --name-only --diff-filter=ACM | grep "\.md"); do if ! $MDLINT "$file"; then echo "Lint check failed on file '$file'." echo "Run markdownlint to identify the errors and try again." exit 1 fi done To make this script active as a pre-commit hook, you must name it pre-commit, you must place it into Git's hook directory (which defa ## Building Diving Nomads: Automating Dive Center Onboarding and Memberships with No-Code Tools DevFeed: [Building Diving Nomads: Automating Dive Center Onboarding and Memberships with No-Code Tools]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-07-25T05:00:00Z Content type: tutorial Language: en Sources: [Tobias Mende]() Topics: [Automation](), [n8n](), [No-code](), [Low code](), [Database](), [email](), [Self-hosted](), [Notion](), [Cloud]() Tags: [automate](), [automation](), [building](), [created](), [database](), [email](), [hooks](), [low-code](), [n8n](), [no-code](), [platform](), [startup-business-automation-software-development-case-study-practices]() ### AI overview This article describes how Diving Nomads uses an automation-first stack to onboard dive centers and manage memberships. It covers scraping directories into NocoDB, sending outreach through Brevo, tracking responses with webhooks, and using n8n workflows to reduce manual work. ### Source excerpt Building Diving Nomads in Public: How We Onboard Dive Centers and Automate Memberships with (Almost) No Code TL;DR We're building a platform for digital nomads with a passion for scuba diving. Our lean, automation-first tech stack allows us to move fast, deliver value early, and maybe inspire other early-stage founders to rethink how they build. ## Year in Review: 2024 DevFeed: [Year in Review: 2024]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2025-03-27T00:00:00Z Content type: article Language: en Sources: [Tania Rascia]() Topics: [coding](), [CSS](), [React](), [Web Development](), [Web platform]() Tags: [bluesky](), [burnout](), [career](), [coding](), [css](), [hooks](), [keyboard](), [meta](), [pagination](), [projects](), [react](), [redesign](), [review](), [side-projects](), [sorting](), [table](), [variables](), [year-in-review]() ### AI overview A 2024 year-in-review from a principal engineer who continues to work primarily with React and CSS. The author reflects on balancing a full-time engineering role with coding, writing, side projects, and maintaining a personal website, while highlighting several articles and a blog redesign completed during the year. ### Source excerpt I'm trying to win the award for "Latest Year in Review". 🏆 I don't know if anyone can challenge me at this point, as it's almost thirdway... ## React Router 7 Tutorial DevFeed: [React Router 7 Tutorial]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2025-01-06T05:52:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [React Router](), [Tutorial](), [React](), [Routing (disambiguation)](), [Vite]() Tags: [hooks](), [layout](), [navigation](), [react](), [react-router](), [react-router-7](), [react-router-tutorial](), [routing](), [tutorial](), [vite]() ### AI overview A step-by-step tutorial for building a React application with React Router 7. It covers project setup with Vite, navigation and links, route matching, layout routes, and related routing patterns. ### Source excerpt React Router 7 tutorial: setup, hooks, nested routes, dynamic routes, programmatic navigation, active links, layout routes, index routes and more. A step by step React tutorial for beginners ... ## Solid Queue 1.0 released DevFeed: [Solid Queue 1.0 released]() Original publisher: [Read original article]() Author: Rosa Gutiérrez Published: 2024-09-26T17:00:00Z Content type: release Language: en Sources: [37signals Dev]() Topics: [Rails](), [Job](), [Monitoring](), [Prometheus](), [PostgreSQL]() Tags: [batch](), [hooks](), [instrumentation](), [job](), [logging](), [monitoring](), [postgresql](), [prometheus](), [queues](), [rails](), [release]() ### AI overview 37signals released Solid Queue v1.0.0, adding atomic batch job operations, recurring jobs, logging and instrumentation, lifecycle hooks, and installation improvements. The article also describes its production use in HEY and ongoing adoption in Basecamp 4. ### Source excerpt The first major release of Solid Queue is out, just in time for Rails World. ## My pre-commit config for Hugo blog DevFeed: [My pre-commit config for Hugo blog]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-29T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [hooks](), [Hugo](), [Git](), [Optimization](), [make]() Tags: [bash](), [config](), [devops](), [git](), [git-pre-commit-configuration](), [hooks](), [how-to](), [hugo](), [hugo-blog-automation](), [hugo-development-tips](), [linux](), [macos](), [make](), [optimization](), [pre-commit](), [pre-commit-hooks](), [pre-commit-setup](), [static-site-optimization]() ### AI overview A tutorial showing how to configure pre-commit hooks for a Hugo blog. The configuration automates linting, syntax checks, file optimization, and related cleanup tasks when files are committed. ### Source excerpt Learn how to set up and use pre-commit hooks to automate tasks like linting, syntax checks, and optimizations for your Hugo blog. ## EU Funding for Mobile App Traffic Interception DevFeed: [EU Funding for Mobile App Traffic Interception]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2023-02-27T12:00:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [interception](), [Mobile](), [Security & Privacy](), [Android](), [iOS](), [Instrumentation](), [Open Source](), [Network]() Tags: [android](), [announcements](), [certificates](), [development](), [eu](), [frida](), [funding](), [hooks](), [http](), [instrumentation](), [interception](), [ios](), [mobile](), [mobile-apps](), [network](), [open](), [privacy](), [product-development](), [security](), [technical]() ### AI overview HTTP Toolkit announces EU-backed funding to improve HTTPS traffic interception for mobile apps on iOS and Android. The project will use Frida integrations and hooks to support app-specific interception, automatic certificate unpinning, and simpler setup. ### Source excerpt HTTP Toolkit has been selected to receive another round of open-source funding from the EU! This aims to improve interception of HTTPS traffic from mobile apps, making it easier for both security/privacy researchers and normal technical users to inspect & manipulate the data that any app they use sends & receives. This funding will directly support work to improve the precision & usability of mobile app interception, on both iOS and Android. In a couple of clicks, you'll be able to target any app installed on a connected device (on either platform) and inspect all its traffic. That means no background noise from full system interception, automatic certificate unpinning, and no fiddly manual setup required. HTTP Toolkit can already automatically intercept Android devices, but only globally for the whole device (using Android's VPN APIs), with system certificates injected but without certificate unpinning, and with no automatic setup support for iOS at all. All those caveats are going away (of course, I'm intending the existing device-wide interception to remain a fully supported option indefinitely too). This is going be powered by a set of new integrations & hooks for Frida, a popular open-source instrumentation toolkit. Many advanced HTTP Toolkit users are already using Frida independently (see the Frida certificate unpinning guide for more info) but doing so often requires quite a bit of setup and specialist knowledge. This project is going to take that away, making network interception of mobile apps easily accessible to anybody who knows what "HTTP" is. All this is being funded by the fantastic NLNet Foundation as part of NGI Zero Entrust, a program funding open-source EU projects that support transparency around data use & privacy in modern technology. This is part of the EU's Next Generation Internet (NGI) initiative, aiming to directly fund researchers & open-source developers to encourage the future engineering of the Internet towards European values: "openn ## Making unwinding through JIT-ed code scalable DevFeed: [Making unwinding through JIT-ed code scalable]() Original publisher: [Read original article]() Author: Thomas Neumann (noreply@blogger.com) Published: 2022-06-26T08:46:00Z Content type: tutorial Language: en Sources: [Database Architects]() Topics: [C++](), [Exception](), [gcc](), [Concurrency](), [Jule](), [systems]() Tags: [c-plus-plus](), [compiler](), [concurrent](), [exception](), [gcc](), [hooks](), [jit](), [lock-free](), [mutex](), [series]() ### AI overview This article explains why C++ exception unwinding remains effectively single-threaded when JIT-ed code is registered. It describes limitations in gcc and glibc mechanisms and introduces a gcc patch using a read-optimized lock-free b-tree to support parallel unwinding without atomic writes. ### Source excerpt Exceptions are a very handy mechanism to propagate errors in C++ programs, but unfortunately they do not scale very well. In all common C++ implementations the unwinding mechanism takes global lock during unwinding, which has disastrous consequences when the number of threads is high. On a machine with 256 hardware context we see worse-than-single-threaded behavior even for relatively modest failure rates. Fortunately the Florian Weimer fixed one contention point in gcc 12 on systems with glibc 2.35 or newer, which gives us scalable exceptions as long as no JIT-ed code has been registered. Unfortunately our system does register JIT-ed code... Which means exception unwinding in our code base is still single-threaded in practice. But we can fix that by teaching gcc to store the unwinding information in a read-optimized b-tree, which allows for fully parallel unwinding without any atomic writes. There is a gcc patch that does just that, but unfortunately it is quite involved and difficult to review. This article series thus explains all parts of the patch and shows how a read-optimized b-tree can be implemented lock-free. In order to keep the article length somewhat reasonable, the discusses is broken into parts: The problem (this article) Replacing the gcc hooks Optimistic Lock Coupling The b-tree b-tree operations When unwinding exceptions, the compiler has to find the corresponding unwinding information for every call frame on the stack between the throw and the catch. gcc uses two different mechanisms for that: For ahead-of-time compiled code it asks glibc to find the unwinding information using either dl_iterate_phdr (on older systems) or _dl_find_object (on systems with glibc 2.35 or newer). Note that this mapping is not static, as shared libraries could be added or removed at any time, potentially during a concurrent unwind. For that reason dl_iterate_phdr was protected by a global mutex, which clearly does not scale. _dl_find_object avoids that mutex by using a ## My tmux workflow DevFeed: [My tmux workflow]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2022-06-06T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Shell](), [hooks](), [Terminal](), [POSIX](), [ssh](), [dotfiles](), [Command-line interface]() Tags: [hooks](), [posix](), [shell](), [ssh](), [terminal]() ### AI overview A developer describes a tmux workflow for local and SSH-based remote work, including a project session selector that sorts projects by usage. The article then explains using a shell trap to avoid losing an SSH connection when exiting the last pane of a session. ### Source excerpt I wanted to share a quick thing that made my life easier on tmux lately, but before we dig into that, I feel like I need to explain how I usually work. [Next page]()