Learning - POLPROG | Articles on software, automation and integrations Skip to content

Learning

Practical know-how on frontend, AI tools and software development.

Practical know-how

Latest articles

Core Web Vitals in 2026: LCP, INP and CLS in practice

Core Web Vitals in 2026 still consist of three metrics: LCP for loading the main content, INP for interaction responsiveness and CLS for layout stability. The scores alone do not tell you what to fix. Effective optimization requires separating real-user field data from lab tests, finding the actual LCP element, slow interaction or layout shift source, and then monitoring the result after deployment.

CORS: what it is and why the browser blocks an API

CORS is not a mechanism that simply blocks connections to an API. It is a browser protocol built on the same-origin policy that decides whether JavaScript from one origin may read a response from another origin. In some cases the HTTP request is sent and the browser only blocks script access to the response. In other cases the browser sends an OPTIONS preflight first and uses its result to decide whether the actual request may be sent at all.

DDD in frontend: when Domain-Driven Design makes sense

Domain-Driven Design is not a folder convention and it is not reserved for backend systems. Its purpose is to make complex business domains manageable through shared language, explicit models, and clear context boundaries. In frontend systems, DDD can be highly valuable in large product applications, but it can also become expensive architectural overkill. The key is to identify where the client truly contains domain complexity and where it is simply a presentation layer.

Docker Compose vs Kubernetes: what your project really needs

Docker Compose and Kubernetes solve problems at different levels. Compose is excellent for defining and running a multi-container application, especially on a single host. Kubernetes is a cluster orchestration platform that adds multi-node scheduling, self-healing, stable network services, controlled rollouts and autoscaling. The decision should not be driven by container count but by availability requirements, scale, deployment frequency and the team's ability to operate the platform.

  • AI
  • min read

GPT-6 Astra is here: benchmarks, pricing, 1.05M context, API changes, and comparison with GPT-5.6 Sol and Claude Fable 5.1

OpenAI officially announced GPT-6 Astra on September 3, 2026. The rollout is staged: the model first reached a limited set of organizations, with OpenAI saying access would expand over the following days to ChatGPT Plus, Pro, Business, and Enterprise, as well as the API, Microsoft Azure, and Amazon Bedrock. Astra provides a 1,050,000-token context window, up to 128,000 output tokens, and Standard API pricing of $10/MTok input and $50/MTok output. This article separates OpenAI-reported results from independent testing and methodology caveats.

  • AI
  • min read

Grok 4.7 has not been officially released: what is actually confirmed as of September 4, 2026

As of September 4, 2026, there is no official Grok 4.7 announcement in SpaceXAI news, the model documentation, or API release notes. The latest confirmed flagship remains Grok 4.6, released on August 12, 2026. Rather than assigning invented specifications, pricing, or benchmarks to Grok 4.7, this article separates confirmed facts from speculation and documents what is officially available today.

  • AI
  • min read

MCP, Model Context Protocol: what it is and how it works in practice

Model Context Protocol, or MCP, is an open standard for connecting AI applications to tools and data sources. Instead of building a separate integration for every model and service, an MCP server describes its capabilities in a standardized form that compatible clients can discover and invoke. By 2026, MCP has moved well beyond its original release: the current specification uses a stateless HTTP core, formal extensions, stronger authorization rules, and mechanisms for long-running work.

Monorepo vs Multirepo in 2026: when to choose each approach

Monorepo and multirepo solve the same organizational problem in different ways. A monorepo stores multiple applications, libraries, or services in one repository, while multirepo separates them into distinct repositories. In 2026 the choice is no longer just about repository size. Modern tooling can limit CI to affected projects, cache results, enforce architectural boundaries, and partially check out very large Git trees. The real question is not which model is universally better, but which coordination costs an organization wants to pay and where it needs shared context versus isolation.