Multiple blasts rock Bangladesh's Dhaka

Developer Tutorial: Build a Browser-Based AI Posture Monitor Using MediaPipe and React

A developer tutorial published on DEV Community walks readers through building a real-time posture monitoring tool using MediaPipe Pose, TensorFlow.js, and React. The system uses a device's webcam via WebRTC to detect body landmarks and calculates the neck angle between the ear and shoulder to identify forward head posture. When the calculated angle falls below a set threshold, the app triggers a local browser notification to alert the user. All processing happens entirely within the browser, meaning no images or data are sent to external servers. The tutorial targets developers with basic React knowledge and aims to address the common problem of poor posture during long hours at a computer.

What Makes a Progressive Web App: HTTPS, Service Workers, and a Manifest

Progressive Web Apps (PWAs) are websites that behave like native apps, offering home screen installation, offline access, and push notifications without requiring app store distribution. They are built on three core pillars: HTTPS for security, a Service Worker that intercepts network requests and manages caching, and a Web App Manifest JSON file that defines the app's name, icons, and display settings. The Service Worker supports multiple caching strategies — including Cache First, Network First, and Stale While Revalidate — allowing apps to function even without an internet connection. A valid manifest combined with a registered Service Worker triggers the 'Add to Home Screen' install prompt in Chrome and most Android browsers. Tools like PWABuilder can help developers audit an existing site and auto-generate the required manifest, icons, and Service Worker files.

In Pir Panjal, new strategy to keep terrorists from slipping between Jammu and Kashmir

Developer builds errval to bring Go-style error handling to TypeScript

A developer who works primarily in TypeScript and Go built errval, a lightweight TypeScript library that brings Go-style explicit error returns to TypeScript projects. The library weighs just 1.86 kB minified and gzipped, has zero dependencies, and works across Node, Bun, and Deno runtimes. It uses a tuple pattern — const [err, value] — where the error is placed first to prevent developers from accidentally ignoring it. Benchmarks show errval handles failure-path requests at 226 ns per request, slower than neverthrow's 198 ns but significantly faster than plain try/catch at 2,623 ns on the failure path. The project is at version 0.1, currently maintained by a single developer, and is available via npm and GitHub.

Tehran has seven demands for Donald Trump

Flash floods toll may climb as high as 10,000, says Nepalese Finance Minister

India and Nepal working on PM Balen Shah visit in November

Git's rerere Feature Can Automatically Reuse Your Past Conflict Resolutions

Git includes a built-in feature called rerere (reuse recorded resolution) that remembers how a developer resolved a merge conflict and replays that resolution if the identical conflict appears again. Once enabled via a single config setting, Git stores a preimage of each conflict and the corresponding postimage resolution under the .git/rr-cache/ directory. By default, rerere writes the saved resolution into the file but leaves it unstaged, allowing the developer to inspect the result before proceeding. An optional autoupdate setting can also stage the file automatically, though the rebase or merge operation still pauses for a manual review. Recorded resolutions can be discarded with git rerere forget, and rerere only triggers when a conflict matches byte-for-byte, so any change to either side of a conflict prompts a fresh resolution.

How to Undo a Git Commit: The Right Command Depends on Two Questions

Undoing a Git commit has multiple correct approaches, but choosing the right one requires answering two questions first: where does the change currently live, and has anyone else pulled it? For local, uncommitted changes, commands like 'git restore' or 'git restore --staged' are appropriate depending on whether the edit is in the working tree or the index. Committed but unpushed changes can be safely undone with 'git reset --soft HEAD~1', which removes the commit while preserving the staged content. Once a commit has been pushed and shared with others, rewriting history is risky, and 'git revert' is the safer choice as it adds an inverse commit rather than deleting history. Using 'git reset --hard' is the most destructive option, permanently discarding uncommitted changes with no recovery path through the reflog.

How Git Bisect Can Pinpoint a Buggy Commit in Just Four Test Runs

Git's built-in bisect tool uses binary search to identify which commit introduced a regression, requiring only a known good commit, a known bad commit, and a test that returns an exit code. In a 12-commit example repository, running 'git bisect run' with an automated test script narrowed down the culprit in just four steps without any manual intervention. The offending commit, labelled 'Perf: simplify addition loop', had stripped minus signs from numeric arguments, silently converting all negative numbers to positives. Git bisect works by checking out the midpoint of the commit range, running the test, and halving the search space based on the result — a process that scales logarithmically regardless of how many commits are involved. For reliable results, the test script must be independent of files added after the known-good commit, and endpoints must be verified, as an incorrect 'good' baseline will lead bisect to the wrong answer.

Git Worktrees Let You Handle Interruptions Without Stashing Your Work

Git has supported a feature called 'git worktree' since version 2.5, allowing developers to create a second working directory that shares the same repository database without cloning it. When interrupted mid-feature, a developer can run 'git worktree add' to check out a separate branch in a new folder, leaving the original work completely untouched. The hotfix can be made, committed, and pushed from that second directory, after which the developer returns to find their uncommitted changes exactly as they left them. Git enforces a safety rule preventing the same branch from being checked out in two worktrees simultaneously, avoiding race conditions on branch pointers. Once the hotfix is merged, the extra directory can be cleanly removed with 'git worktree remove', while the branch itself is preserved.

AI Hallucinations in High-Stakes Work Pose Greater Risk Than Capability Gaps

A recent incident involving the US military highlighted the dangers of AI-generated intelligence reports containing hallucinated information that nearly influenced a real operational decision. Unlike accuracy benchmarks, no standard metric measures an AI model's ability to recognise when its own outputs are wrong — a gap that poses serious risks in critical applications. A model that is correct 97% of the time but states errors with full confidence can be more dangerous than one that is less accurate but flags its uncertainty. In practical settings such as cross-border commerce, undetected AI errors can manifest as fabricated product specs, non-existent legal citations, or incorrect customer-facing policies. Experts argue that the more durable approach is designing systems that assume AI output may be wrong and route high-stakes, irreversible actions through independent verification or human checkpoints.

Dr. T: AI Platform Combines Clinical Triage, Diagnostics, and Blockchain Micropayments

Dr. T is a multilingual AI healthcare platform designed to support patients, caregivers, and clinicians through real-time voice-based triage, empathetic mental wellness guidance, and personalized medical communication. The system integrates clinical automation tools including pharmacogenomics-based drug interaction prediction, EHR summarization using FHIR standards, and AR-assisted skin lesion analysis for malignancy risk estimation. A built-in media production module converts peer-reviewed research and discharge plans into educational 2D and 3D videos using multimodal AI reasoning paired with verified clinical citations. The platform also incorporates a decentralized micropayment engine built on Algorand's MainNet, enabling AI agents to pay for API calls in USDC with near-instant finality and fees under one-tenth of a cent. Patient data privacy is maintained through zero-knowledge proofs and differential privacy protocols designed to meet HIPAA standards and keep users in full control of their biometric and genetic information.

After acquittal in Nithari case, Surendra Koli was approached by documentary makers, faced financial crunch

Etihad flight cancelled; chaos erupts in Delhi

Ed Sheeran breaks silence on Macklemore tour controversy at Philadelphia show

Ed Sheeran addressed the recent controversy surrounding rapper Macklemore at a concert in Philadelphia. The show marked Sheeran's first performance since Macklemore was removed from his tour. Several other artists also withdrew from the tour around the same time. Sheeran took the opportunity to speak publicly about the situation for the first time during the live event.

Developer Builds Open Source TUI Tool 'Portop' to Simplify Linux Port Monitoring

A Linux developer created Portop, an open source terminal UI written in Go, to quickly identify which processes, services, or containers are using specific network ports. The tool reads kernel socket tables directly from the Linux /proc filesystem and maps them to processes, systemd services, and Docker containers without requiring a privileged background daemon. Users can search, filter, inspect, and terminate processes from a single live interface, with detailed process metadata available on demand. Following community feedback after the initial release, the developer added Docker Compose integration, allowing users to compare configured ports against what is actually running on the machine. Portop also supports JSON output, making it suitable for scripting and automated workflows beyond interactive use.

Why a Code Audit Should Come Before Any Work on Inherited Software

Taking over software built by someone else — whether a departed developer, a vanished agency, or an acquired company — leaves new owners unable to answer basic questions about cost, stability, or security. A code audit addresses this by having an expert read the existing codebase and deliver a written assessment of what to keep, fix, or rewrite before any money is spent on changes. The review goes beyond code quality, examining account ownership, infrastructure costs, and active security risks that rarely appear on anyone's to-do list. Skipping the audit and immediately building new features is a common mistake, since unknown codebases make accurate estimates nearly impossible and hidden vulnerabilities can threaten the entire product. The author argues that a full rewrite is rarely the right answer — most inherited products have a salvageable core that needs only targeted repairs.

Why a Code Audit Should Be Your First Step After Inheriting Software

Inheriting a software product — whether a developer left, an agency contract ended, or a company was acquired — often means taking ownership of a system no one fully understands. A code audit examines the existing codebase, infrastructure, and architecture to produce a written assessment of what should be kept, fixed, or rebuilt. Beyond technical review, audits frequently uncover critical non-technical risks such as unprotected access credentials, absent data backups, or untracked running costs. Skipping this step and immediately adding features or fixes can lead to unpredictable timelines and hidden costs, since changes to unfamiliar code are difficult to scope accurately. Experts argue that while a full rewrite is often the instinctive recommendation from new teams, there is usually a viable core worth preserving alongside a limited set of concrete issues to address.