Tutorial: Build a TypeScript CLI to Map GitHub Codebase Relationships as a Graph

·1 views

A new developer tutorial published on DEV Community walks through building a command-line tool in TypeScript that transforms GitHub pull request data into an in-memory engineering graph. The project maps four node types — repositories, pull requests, files, and people — connected by relationships such as authored, modified, and reviewed. By querying these relationships, developers can identify who has experience with a specific file, who reviewed related changes, and which files frequently change together. The CLI uses only TypeScript and GitHub's REST API, requiring no graph database, vector database, or AI model. The guide covers project setup, graph construction, GitHub data ingestion, query design, and basic testing, and is aimed at developers inheriting unfamiliar codebases.

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)

Why GPU Cloud Cost Per Hour Is a Misleading Metric for Real Workloads

A technical analysis argues that comparing GPU cloud providers solely by hourly rate leads teams to overspend despite believing they secured a good deal. The true measure of value is cost per unit of work — such as per token, per training run, or per job — since a cheaper GPU with lower throughput can end up costing more overall. Hidden factors like GPU utilization, data transfer fees, provisioning delays, and spot instance evictions can significantly inflate the real cost beyond the advertised rate. For example, a GPU running at 30% utilization due to poor autoscaling may prove more expensive than a pricier provider sustaining 80% utilization. The article recommends benchmarking actual workloads and calculating fully-loaded costs before choosing a provider, treating GPU spend as a broader FinOps discipline.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

FinOps Must Evolve Beyond Cloud Bills to Tackle Rising AI Token Costs

As AI adoption grows, token spend has emerged as a major operational expense that traditional FinOps frameworks were not designed to handle. Unlike cloud infrastructure costs, AI token spend is scattered across cloud bills, separate API invoices, and vendor platform fees, making it difficult to get a unified view. The cost is tightly coupled to application behavior, meaning a single inefficient prompt or a looping AI agent can cause token volumes to spike unexpectedly. Standard cost-attribution methods like resource tags fall short because most teams route requests through shared API keys with no visibility into which feature, team, or customer is responsible. Experts argue that organizations must aggregate all AI spend into one view, enforce granular attribution, right-size model usage, and deploy anomaly detection to bring AI costs under meaningful financial control.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Technical SEO Audits Need Clear Decisions, Not Just Health Scores

A technical SEO audit that scores 97% healthy can still overlook a single critical flaw—such as an accidental noindex or a misconfigured canonical—that should halt a release. The article argues that aggregate health scores compress vastly different risks into one misleading number, masking gaps in evidence and untested checks. In response, the author outlines a decision-based audit framework used at Edikka, featuring 44 replayable checks across 13 domains, each classified by both compliance status and severity level. A structured release rule determines whether a site gets a GO, NO-GO, or requires arbitration, and crucially, this rule must be defined before audit results are known. The framework also draws a clear distinction between publicly observable evidence and private data accessible only through tools like Google Search Console, keeping conclusions honest and falsifiable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Fleet Management Emerges as Solution to Kubernetes Edge Deployment Challenges

Kubernetes deployments at the edge — spanning retail stores, factories, and remote cell sites — have hit a scaling wall, as managing hundreds of small clusters individually proves unworkable. Unlike datacenter clusters, edge clusters are often offline, resource-constrained, and lack on-site technical staff, making traditional one-at-a-time management impractical. Fleet management addresses this by shifting operations from individual clusters to an entire population, using declarative, pull-based configuration so clusters self-reconcile when they reconnect to the network. Tools such as k3s, Rancher Fleet, Argo CD ApplicationSets, and Flux support this model through label-based grouping and staged rollouts that limit the blast radius of faulty updates. Analysts also flag cost visibility as an overlooked challenge, since hundreds of edge clusters create as many places for over-provisioning to go undetected by standard tooling.

0 comments Read more at DEV Community