Cloud and Infrastructure Skills Dominate Tech Job Market, Outpacing Most Languages

·1 views

An analysis of 15,265 open roles across 1,077 tech companies found that cloud and infrastructure skills are among the most in-demand, with Python leading at 38% of postings, followed by AWS at 25% and Kubernetes at 21%. Six of the top twelve most-requested skills are cloud or infrastructure-related, including Google Cloud, Docker, Azure, and Terraform. Notably, Kubernetes appears in more job postings than Java, React, TypeScript, or Go, despite rarely being highlighted in standard coding bootcamps or beginner roadmaps. Only about one in thirteen of these roles are dedicated infrastructure positions such as DevOps or SRE, meaning cloud familiarity is increasingly expected in mainstream backend, full-stack, and data engineering roles. Analysts attribute the sustained demand partly to the high-stakes nature of infrastructure work, where AI-generated errors can have serious consequences, making human oversight difficult to eliminate.

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)

Ash Framework: AshJsonApi, AshGraphQL, and AshTypescript for Elixir API Integration

The Ash framework for Elixir offers a suite of tools — AshJsonApi, AshGraphQL, and AshTypescript — designed to reduce boilerplate and streamline API development. Building scalable, production-ready applications typically requires significant effort beyond core business logic, including database setup, API design, and infrastructure configuration. Ash addresses this by automating repetitive integration tasks, similar to how Go's oapi-codegen generates server code from Swagger contracts. The article introduces these three Ash extensions as a way to establish predictable, well-documented contracts between frontend and backend without rewriting compatibility layers repeatedly. The author's goal is to orient developers toward these tools and encourage hands-on exploration rather than provide an exhaustive tutorial.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Caching Bug in Next.js Badge App Triggered Duplicate GitHub API Calls Under Load

A developer discovered a 'thundering herd' bug in CommitPulse, a Next.js app that renders GitHub contribution data as SVG badges. Although the cache functioned correctly for sequential requests, multiple concurrent requests for the same username each independently checked the cache, all found a miss, and all fired separate calls to GitHub's API before any response had returned. This pattern becomes costly because GitHub's GraphQL API enforces a rate limit of 5,000 points per hour, and a traffic spike — such as a trending repository or Hacker News post — can trigger dozens of simultaneous identical upstream requests. The root cause is the absence of in-flight request deduplication: the cache only prevents redundant calls after a response is stored, not while the first fetch is still pending. The fix involves tracking in-progress Promises in a separate Map so that any concurrent request for the same key awaits the already-running fetch instead of launching a new one.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How the STAR Framework and STRIDE Model Make Threat Modeling Easier to Grasp

Threat modeling is a structured approach to identifying and understanding security risks within a system before they can be exploited. The STAR framework begins with Scope, using Data Flow Diagrams to map processes, data stores, external entities, and trust boundaries across an environment. In cloud settings, this mapping grows more complex due to shared responsibility models, IAM roles, and rapidly changing architectures. Once the environment is mapped, the STRIDE model helps analysts systematically categorize threats — including spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Together, these frameworks ensure security teams examine potential attack paths from every angle rather than trying to predict specific future incidents.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

The 80/15/5 Rule That Could Save Your AI Engineering Budget

AI engineers are increasingly adopting a three-tier model selection framework to balance performance and cost when building LLM-powered applications. The approach suggests that roughly 80% of routine tasks — such as bug fixes, API integrations, and data cleaning — can be handled efficiently by lightweight budget models like GPT-Mini. A middle tier of frontier models is recommended for the 15% of tasks requiring deeper contextual reasoning, such as multi-step logic or translating abstract requirements into working code. Only the most complex enterprise-grade challenges, estimated at just 5%, justify the significant expense of the largest, most capable models. The framework warns that defaulting to top-tier models for all tasks is financially unsustainable, while relying solely on budget models risks failure under real enterprise complexity.

0 comments Read more at DEV Community