# hooks Hooks are predefined points where registered callback code can interact with or modify other code. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## Inside the Git Hooks: Tagging Every AI Agent Commit (Part 3) DevFeed: [Inside the Git Hooks: Tagging Every AI Agent Commit (Part 3)]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [Git](), [hooks](), [AI Agent](), [observability](), [Security]() Tags: [ai-agent](), [ai-agents](), [ai-coding](), [capture](), [commit](), [eugene-petrenko](), [git](), [git-hooks](), [infrastructure](), [jonnyzzz](), [provenance](), [repo](), [sandbox](), [tag-41199d53f463](), [workflow]() ### AI overview This third-part tutorial explains a best-effort Git hook layer for AI agents running inside a sandbox. The hooks stamp session IDs on commits, preserve the tags through amend, rebase, and squash, and capture restorable copies of pushed changes while continuing to run repository-local hooks. ### Source excerpt Part 3 -- the build for the lighter solution. How a set of git hooks stamps a session id on every commit an AI Agent makes, survives squash and rebase, and captures each push -- all best-effort, all inside the sandbox. ## 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. ## 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. ## 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. ## Build and Deploy a Simple ReactJS Website: Part 1 DevFeed: [Build and Deploy a Simple ReactJS Website: Part 1]() Original publisher: [Read original article]() Author: Claire Rhoda Published: 2023-06-30T19:08:00Z Content type: tutorial Language: en Sources: [Apartment 304]() Topics: [React](), [JavaScript](), [CSS](), [Web Development](), [Code](), [hooks]() Tags: [apartment-304](), [aws](), [bash](), [beginners](), [css](), [custom-software-solutions](), [devops](), [devops-engineer](), [editor](), [github](), [guide](), [how-to](), [javascript](), [reactjs](), [software-architecture](), [software-development](), [software-engineer]() ### AI overview This tutorial is the first part of a series on building and uploading a personal website. It introduces creating a ReactJS project, styling it with CSS, and using common ReactJS techniques, tools, and hooks. ### Source excerpt The first part of this series focuses on how to code a personal portfolio using the ReactJS JavaScript framework. This project will go over techniques, tools, and hooks commonly used in ReactJS along with some basic CSS to make our website look presentable. ## Sunsetting Deploy Hooks, Migrate to App Webhooks DevFeed: [Sunsetting Deploy Hooks, Migrate to App Webhooks]() Original publisher: [Read original article]() Author: Nicolás Risaro Published: 2022-08-17T22:36:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [migration](), [hooks](), [releases]() Tags: [cloud-infrastructure](), [email](), [heroku](), [http](), [irc](), [migration](), [news](), [notifications](), [payload](), [platform-updates](), [release](), [releases](), [webhooks]() ### AI overview Heroku is deprecating Deploy Hooks and recommends migrating to app webhooks. New deploy hooks will no longer be accepted from October 17, 2022, while existing hooks will continue working until February 17, 2023. The article explains webhook benefits and migration differences, including limitations for email, IRC, and dynamic URL parameters. ### Source excerpt Webhooks are a more secure, reliable, and powerful alternative to Deploy Hooks, and five years ago, we made app webhooks Generally Available. Today, we are deprecating Deploy Hooks and encouraging customers to migrate to app webhooks. Starting October 17, 2022, we will stop accepting new deploy hooks. Existing hooks will continue working until the product [...] The post Sunsetting Deploy Hooks, Migrate to App Webhooks appeared first on Heroku. ## 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. ## How and When to Use Context in React with Hooks DevFeed: [How and When to Use Context in React with Hooks]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2021-06-15T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [React](), [hooks](), [context](), [Redux](), [Code]() Tags: [api](), [code](), [dashboard](), [graph](), [hooks](), [javascript](), [react](), [redux](), [state](), [state-management](), [table]() ### AI overview A tutorial on using React Context with modern functional components and hooks. It explains that Context can pass data across components and is useful for localized, reusable state, while Redux remains more suitable for large-scale global state management. ### Source excerpt A while ago, I wrote an article about Using Context API in React. However, most of my examples on that page used Class components, , and... ## Announcing GoReleaser Pro DevFeed: [Announcing GoReleaser Pro]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-05-30T00:00:00Z Content type: release Language: en Sources: [Carlos Becker]() Topics: [version](), [monorepo](), [hooks](), [Template]() Tags: [announcements](), [bugfixes](), [features](), [hooks](), [monorepo](), [oss](), [release](), [template]() ### AI overview The author announces GoReleaser Pro after years of maintaining GoReleaser largely for free. GoReleaser is being split into OSS and Pro, with initial Pro features including configuration file includes, improved global hooks, monorepo support, and custom template variables. ### Source excerpt After more than 4 years working on GoReleaser, I'm launching a Pro version! ## Simple video buffering loader in React DevFeed: [Simple video buffering loader in React]() Original publisher: [Read original article]() Author: Stanko Published: 2020-10-16T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [React](), [hooks](), [Code](), [JavaScript](), [Accessibility](), [User experience (UX)]() Tags: [accessibility](), [code](), [hooks](), [javascript](), [react](), [ux]() ### AI overview A tutorial for building a React video component with accessible basic controls and a buffering loader. It explains how to track buffering with video events and use debounce timings to prevent rapid state changes that cause poor user experience. ### Source excerpt For multiple projects, I had to add a simple video component with play/pause buttonAlways include at least basic video controls for accessibility and a buffering loader. It is not hard to detect the buffering state, but it can be tricky to get everything right. Therefore, I created a simple component which I now copy from project to project with slight style adjustments. Jump to the code if you are not interested in how it's made. Demo # Here you can see the final version (it might be easier to see the functionality if you open it in a separate tab). How it works # The solution is simple and relies on four video events: waiting - playback has stopped because of a temporary lack of data pause - playback has been paused play - playback has begun playing - playback is ready to start after having been paused or delayed due to lack of data We are going to use waiting event to set our loading flag to true and all other events to set it to false. If the video is already playing, and buffering happens, we'll get events fired in this order: "waiting" "playing" This is all fine and dandy, but if the video is paused, and we play it things get a little messy. Now, if buffering happens, we'll get these events fired: "play" "playing" "waiting" "playing" All of these events are fired in a very quick succession and alter the state too fast leading to some bad UX. The secret is to add a short debounce time to avoid it. What I found to work best is 200ms for waiting event and 50ms for all others. Code # I'm using React with hooks, but the same thing can be easily ported to React class or vanilla JavaScript. import React, { useEffect, useState, useRef } from 'react'; const PLAYING_DEBOUNCE_TIME = 50; const WAITING_DEBOUNCE_TIME = 200; const Video = ({ src, ...props }) => { const [isPlaying, setIsPlaying] = useState(false); const [isWaiting, setIsWaiting] = useState(false); const isWaitingTimeout = useRef(null); const isPlayingTimeout = useRef(null); const videoElementRef = useRef(); u ## React Patterns for Fetching, Storing, and Retrieving Data DevFeed: [React Patterns for Fetching, Storing, and Retrieving Data]() Original publisher: [Read original article]() Author: ryan.glover@cleverbeagle.com (Ryan Glover) Published: 2019-06-03T12:20:42Z Content type: tutorial Language: en Sources: [Pony Foo]() Topics: [React](), [hooks](), [REST API](), [Remote Procedure Call (RPC)](), [GraphQL]() Tags: [autosave](), [code](), [data](), [graphql](), [hooks](), [react](), [refs](), [rest-api](), [rpc](), [state]() ### AI overview A tutorial on common React patterns for fetching, storing, and retrieving data. It emphasizes using simple approaches such as hooks, lifecycle methods, and local state, while noting that Redux or other architectures may be appropriate in some cases. ### Source excerpt Handling data in React can be treacherous if you don't know your way around. Learn some common patterns for fetching, storing, and retrieving data in this guide to help you avoid messy code traps. React's flexibility means you can handle data in a lot of different ways. This guide will teach you patterns for fetching, storing, and retrieving data in React without the stress of maintaining a complex system. As part of my mentorship business, I have the unique opportunity to work with React daily across a wide range of projects. Teaching others how to build their own software products, I've come to find that most problems in React can be solved with some very simple techniques. While some cases may call for a full-blown architecture using something like Redux (or other fanciness), a lot of the time React's built-in lifecycle methods and local state do the trick. In my opinion, the mark of a really great developer is one who can solve a problem with as few moving parts as possible. While it can feel great to build a monument to engineering in the form of a complex system, often it's just overkill. In this tutorial, I'm going to share what I call my "data survival kit:" the most common patterns and hacks I use in my day-to-day work for managing data. By the time you finish, you'll have everything you need to build data-driven UIs that offer a polished user experience. Loading Data via Hooks As most folks are building "database apps," loading data is arguably one of the most common tasks to perform. Ultimately, where your data is coming from dictates your need for this. This pattern is best utilized in apps using a REST API or an RPC (remote procedure call) to fetch data. For example, if you're loading data via GraphQL, it's likely that you'll use this technique sparingly (e.g., when you need to fetch data programmatically as opposed to on page load), relying on tools like Apollo to load your data for you. import React, { useEffect, useState } from 'react'; function Post ## Discovering patterns with React hooks DevFeed: [Discovering patterns with React hooks]() Original publisher: [Read original article]() Author: m@peka.la (Maciek Pekala) Published: 2019-05-13T12:15:55Z Content type: article Language: en Sources: [Pony Foo]() Topics: [React Hooks](), [React](), [hooks](), [ui]() Tags: [best-practices](), [coding](), [components](), [hooks](), [patterns](), [react](), [react-hooks]() ### AI overview An exploration of patterns that emerge when building stateful React components with hooks. The article introduces the author's Choco pattern, which combines Context, a Hook, and a Component for top-level, centralized, unique UI widgets that expose functionality to other application components. ### Source excerpt One of the things I enjoy the most about coding is discovering patterns. Being aware and mindful of the patterns emerging in your codebase can make it easier to keep that codebase consistent, readable and easy to navigate. Most patterns will remain unspoken, and some, that prove notably elegant, are named and promoted as best practices. Others might even be candidates for a basis of a new abstraction, although I recommend restraint as it's worth remembering that abstractions are expensive. If you're not familiar with the topic or React hooks, there is plenty of introductory as well as in-depth materials out there. I can also shamelessly recommend my talk on hooks from a recent React Copenhagen meetup. What follows assume at least some understanding of what hooks are and how to use them. Pattern extinction level event Discovering new patterns is relatively rare when working with established technologies, but every now and then a new idea comes up that stirs things up within some ecosystem. Enter React hooks. Hooks enable a drastically different way to build stateful components in React, which means that they also invalidate 1 a lot of the established patterns. However, being an exceptionally well thought-through and composition-friendly abstraction, hooks enabled new, elegant patterns to emerge. Over the last few months, I've been building apps with hooks and I've been having a lot of fun discovering these patterns. I'd like to share one, that I've grown especially fond of. For the lack of a better name, and for sole the purpose of this blog post, let's call it the Choco pattern (from Context, HOok, COpomonent). The pattern comes useful when you need a UI widget which is top-level, centralised and unique across the application and needs to expose some functionality to the rest of the components in the app. It might sound vague at the moment, so let's try to go through solving a concrete problem where I noticed the Choco pattern manifest itself. Exhibit A: Feature tog ## A Complete Guide to useEffect DevFeed: [A Complete Guide to useEffect]() Original publisher: [Read original article]() Published: 2019-03-09T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [hooks](), [React](), [data]() Tags: [complete](), [deep-dive](), [guide](), [hooks](), [react]() ### AI overview A deep guide to understanding React's useEffect Hook, including its relationship to component lifecycles, data fetching, dependencies, refetching loops, and stale props or state. ### Source excerpt Effects are a part of your data flow. ## Making setInterval Declarative with React Hooks DevFeed: [Making setInterval Declarative with React Hooks]() Original publisher: [Read original article]() Published: 2019-02-04T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [React Hooks](), [React](), [hooks](), [Programming]() Tags: [declarative](), [hooks](), [react](), [react-hooks](), [refs]() ### AI overview This tutorial explains how to use a custom React Hook to make setInterval work with React's programming model. It covers interval setup and cleanup, the relationship between intervals and component lifecycle, and how dynamic arguments enable adjustable delays. ### Source excerpt How I learned to stop worrying and love refs. ## Why Do React Hooks Rely on Call Order? DevFeed: [Why Do React Hooks Rely on Call Order?]() Original publisher: [Read original article]() Published: 2018-12-13T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [hooks](), [React Hooks](), [React]() Tags: [classes](), [hooks](), [mixins](), [react](), [react-hooks]() ### AI overview This personal article explains why React Hooks rely on a persistent call index between component re-renders. It discusses the design rationale, the ability to use Hooks repeatedly in a component, and the implications of that controversial choice. ### Source excerpt Lessons learned from mixins, render props, HOCs, and classes. ## Why use Observable.create() and not just inherit from Observable? DevFeed: [Why use Observable.create() and not just inherit from Observable?]() Original publisher: [Read original article]() Author: Wolfram Rittmeyer Published: 2015-10-09T05:00:40Z Content type: tutorial Language: en Sources: [Grokking Android]() Topics: [RxJava](), [Inheritance](), [hooks](), [debug](), [Monitoring]() Tags: [android](), [create](), [debug](), [hooks](), [how-to](), [inheritance](), [monitoring](), [observable](), [rxjava]() ### AI overview This tutorial explains why RxJava developers should generally create Observables with Observable.create() instead of inheriting from Observable. It discusses final methods, the fluent API, and hooks that support debugging and monitoring, while noting that inheritance can still be appropriate in cases such as Subject. ### Source excerpt When starting to use RxJava you have to create Observables. They are at the very core of RxJava. But how to do so? A look at the Observable class might make you dizzy. Looking at the source even more so. Not only does this beast consist of nearly 10.000 lines (though, 7600 lines of that [...] Continue Reading "Why use Observable.create() and not just inherit from Observable?" The post Why use Observable.create() and not just inherit from Observable? appeared first on Grokking Android.