Five Advanced Git Commands That Can Sharpen Your Development Workflow

·5 views

A technical guide highlights five underused Git features that can help developers work more efficiently and recover from common mistakes. Interactive rebase (git rebase -i) allows developers to clean up commit history before submitting pull requests, while git bisect uses binary search to pinpoint the exact commit that introduced a bug. Git worktrees enable checking out multiple branches into separate directories simultaneously, useful when switching context mid-task. The git reflog command logs every Git action from the past 90 days, making it possible to recover lost commits or branches. Interactive staging via git add -p lets developers selectively commit specific changes within a file rather than staging everything at once.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

gRPC over QUIC cuts seek latency 28x but lags TCP on bulk transfers

Developers testing KeibiDrop, a post-quantum encrypted peer-to-peer filesystem, evaluated replacing gRPC over TCP with gRPC over QUIC to handle IP address changes without dropping connections. Tests were conducted on a 12-core macOS laptop, a 4-core Linux VPS, and a real 72ms round-trip WAN link between Barcelona and the VPS. On the real-world link, a single QUIC stream was up to 16 times slower than TCP for bulk transfers under Wi-Fi packet loss, but random seeks completed in 109ms on QUIC versus roughly 3 seconds on TCP — a 28x improvement — because each seek gets its own independent stream. A teardown deadlock caused by closing a QUIC stream concurrently with a write was identified and fixed by using a stream reset instead of a graceful close. The team settled on a hybrid design: QUIC for interactive on-demand reads where seek isolation and connection migration matter, and TCP for bulk transfers on lossy links.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Four ATS platforms expose public JSON APIs that make job scraping unnecessary

A developer discovered that major applicant tracking systems — Greenhouse, Lever, Ashby, and SmartRecruiters — serve job listings through unauthenticated public GET endpoints, eliminating the need for headless browsers or proxies. Companies like Stripe, Spotify, and Ramp post openings through these platforms, each accessible via a company-specific slug found in the careers page URL. Greenhouse returns full job descriptions in a single response, though its content field requires HTML-entity decoding, while Ashby offers the most structured data including remote status, compensation bands, and plain-text descriptions. Lever and Ashby return flat arrays with minimal extra requests, whereas SmartRecruiters requires paginated calls plus separate per-job detail requests to retrieve full descriptions. The author recommends writing a thin normalizer per provider so downstream code remains unaware of which ATS a given company uses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to fetch Google Play and App Store reviews via JSON without a browser

A developer discovered that both Google Play and the Apple App Store expose app reviews as plain JSON accessible via direct HTTP requests, eliminating the need for headless browsers or proxies. Apple provides reviews through a documented RSS-to-JSON endpoint supporting up to 10 pages of 50 reviews each per storefront, while Google Play uses an undocumented batchexecute API with token-based pagination. The author used the got-scraping library, which mimics a real browser's TLS fingerprint, to avoid 403 errors that standard HTTP clients like axios triggered due to Play Store's TLS-level fingerprinting. Key differences between the two platforms include Play reviews lacking titles and developer replies being absent from Apple's public feed, requiring a nullable title field when merging data from both stores. The author also warns that Google's positional JSON format for Play reviews is inherently fragile, as slot indices can shift without notice, and recommends adding request throttling before using this approach at large scale.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Scraping product data is easier by reading embedded JSON, not parsing HTML

Web developers building product scrapers often rely on CSS selectors, which break whenever a site undergoes a redesign. A more reliable approach involves extracting JSON data already embedded in the page, available in three main forms: schema.org JSON-LD script tags, framework state blobs like __NEXT_DATA__ or __NUXT__, and internal XHR API calls made by the page itself. JSON-LD offers a standardized product shape usable across retailers but can be inaccurate for real-time stock status. Framework state blobs typically contain richer data including variant details and inventory, while direct API calls — as used with SHEIN's mobile API — bypass HTML rendering entirely. Using these JSON sources reduces dependence on headless browsers and makes scrapers significantly more resilient to frontend changes.

0 comments Read more at DEV Community