In the tech world, there is a constant flow of changes and keeping up with them means the choice for tools and technologies which are the most appropriate to invest your time in.
In 2026 the best programming language or technology stack to learn really depends on your personal aims, hobbies, and apps you are going to create.
The use of AI is increasing. AI as a “Pair Programmer” is becoming the default. Code completion, refactoring, and boilerplate generation are used often. Devs spend more time reviewing and steering code than typing it. “Explain this error” and “why is this slow?” prompts are useful.
In prompt-Driven Development programmers describe the intent in natural language and then let AI generate first drafts of functions, APIs, or configs. Iterate by refining prompts rather than rewriting code. Trend: Knowing how to ask is becoming as important as syntax.
Strong growth in: Auto-generated unit and integration tests and edge-case discovery. Trend: “Test-first” is easier when AI writes the boring parts.
AI is moving up the stack. Trend: AI as a junior architect or reviewer, not the final decider.
AI comes to Security & Code Quality Scanning. Rapid adoption in: Static analysis and vulnerability detection, secret leakage and dependency risk checks. AI can give secure-by-default code suggestions. Trend: AI shifts security earlier in the SDLC (“shift left”).
Instead of one-off prompts: AI agents that plan → code → test → fix → retry. Multi-step autonomous tasks (e.g., “add feature X and update docs”) can be done in best cases. Trend: Still supervised, but moving toward semi-autonomous dev loops.
AI is heavily used for explaining large, unfamiliar codebases and translating between languages/frameworks. It helps onboarding new engineers faster.
What’s changing: Less manual boilerplate work
More focus on problem definition, review, and decision-making. There is stronger emphasis on fundamentals, architecture, and domain knowledge. Trend: Devs become editors, designers, and orchestrators.
AI usage policies and audit trails is necessary. Trend: “Use AI, but safely.”
Likely directions:
Deeper IDE + CI/CD integration
AI maintaining legacy systems
Natural-language → production-ready features
AI copilots customized to your codebase
816 Comments
Tomi Engdahl says:
https://en.wikipedia.org/wiki/Liberty_Alliance
Tomi Engdahl says:
I created the same complex website in VS Code, Cursor, and Google Antigravity; only one worked like a senior developer
https://www.xda-developers.com/created-same-complex-website-in-vs-code-cursor-google-antigravity-only-one-worked-like-senior-developer/
Tomi Engdahl says:
Love Language
Maybe Vibe Coding Should Be Called “Cuck Coding” Because You Just Sit in a Chair and Watch
Hey, front row seats!
https://futurism.com/artificial-intelligence/vibe-coding-cuck-coding?fbclid=Iwb21leAVGDBdjbGNrBUYMFWV4dG4DYWVtAjExAHBkb2YFc3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEewvsU2pvLsm8hvlrkMIbcS9t_DPiztILboocRlBaFfkH6f9ZioTvxRyCXW7w_aem_rzoz9prLrFYg4SA0F98TFA
Vibe coding is the act of telling an AI what you want to program and letting it write all the code for you. When it was first adopted, it was supposed to embody the sort of care-free optimism that was running in AI circles at the time, high off the possibilities of the tech. AI models had become so powerful that you could build an app using the same conversational language that you deploy while confiding in ChatGPT.
But the “vibes” are different now. Programmers were quickly forced to grapple with the new reality that AI coding tools brought to their profession. Now that everyone’s using AI to churn out code, you have to crank out even more work to keep up and meet your boss’s quota. It may be more “efficient” — and even that’s contested, since someone needs to do the hard work of verifying all that AI pablum — but it hasn’t exactly made people’s jobs easier. Meanwhile, everyone with a Claude subscription and a half-baked app idea fancies themselves a bona fide programmer, too.
Tomi Engdahl says:
Respan spent two years building on LiteLLM. One upgrade made it start over.
Respan rebuilt its AI gateway in Rust around a small plugin core after 100,000 lines of LiteLLM patches. Custom plugins still mean compiling your own.
https://thenewstack.io/respan-rust-ai-gateway/
Tomi Engdahl says:
Seitsemän yleisintä tapaa, joilla tiimit tuhlaavat pilvirahaa – ja miten sen voi korjata
https://corellia.fi/seitseman-yleisinta-tapaa-joilla-tiimit-tuhlaavat-pilvirahaa-ja-miten-sen-voi-korjata/?fbclid=Iwb21leAVEqHZleHRuA2FlbQEwAHBkb2YFYWRpZAGrOSIpQc__c3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEewOqxdiuPUftJs_Lv1LpoetdRKb5bVSYdMIEOn9M62aqEJ1lSA3sIjc__Ad8_aem_EvWC-O17sTJLeV-UZXhrzA
Tomi Engdahl says:
https://rakettitiede.com/blogi/miten-ottaa-moniagenttinen-ohjelmistokehitys-haltuun-vuoden-tauon-jalkeen
Tomi Engdahl says:
https://venturebeat.com/orchestration/researchers-made-ai-agents-better-by-turning-academic-papers-into-working-code-no-retraining-required
Tomi Engdahl says:
Linus Torvalds Eliminates Unsafe __get_user() & __put_user() Functions In Linux 7.4
https://www.phoronix.com/news/Linus-Kills-Get-Put-User-Linux
Tomi Engdahl says:
Kriittisiä haavoittuvuuksia PHP:ssa
21. lokakuuta 2026 klo 10.06, päivitetty 21. lokakuuta 2026 klo 17.58
21.10.2026 klo 10.06, päivitetty 21.10.2026 klo 17.58
PHP on julkaissut korjauspäivitykset kahteen kriittiseen haavoittuvuuteen, jotka koskevat kaikkia julkaistuja PHP-versioita. Haavoittuvuutta hyväksikäyttämällä hyökkääjä voi mahdollisesti suorittaa etänä mielivaltaisia komentaja palvelimella ja ottaa sen täysin hallintaansa. Kaikki PHP:tä käyttävät sovellukset tulee päivittää välittömästi korjattuun ohjelmistoversioon.
https://www.kyberturvallisuuskeskus.fi/fi/haavoittuvuudet/haavoittuvuus-2026-37
Tomi Engdahl says:
https://www.xda-developers.com/steam-better-way-run-windows-apps-linux-than-wine-not-just-games/
Tomi Engdahl says:
PHP Updates Released For Two Critical Code Execution Vulnerabilities
Written by Michael Larabel in Programming on 21 October 2026 at 09:43 AM EDT. 14 Comments
PROGRAMMINGPHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 were just released to fix two critical vulnerabilities that can allow for unauthenticated remote code execution. Server administrators are advised to update immediately.
The first vulnerability is out-of-memory handling can interrupt PHP causing OOM corruption and remote code execution. The second remote code execution vector is via stale global state surviving after its backing memory has been freed.
Both of these remote code execution vulnerabilities are rated critical at 9.2 out of 10.
More details on these security vulnerabilities and the updated PHP versions at PHP.net.
https://www.phoronix.com/news/PHP-New-Critical-CVEs-October
Tomi Engdahl says:
Claude’s new rich text editor replaced Google Docs for me, and it already knows my entire project before I type anything
https://www.xda-developers.com/claude-new-rich-text-editor-replaced-google-docs/
Most AI-generated files end up living somewhere completely different from where they were created. A chatbot can draft your task list or spec sheet, then you put it in a Google Doc, owned by a completely different company. Wherever you put the notes, that doc ends up with no idea about the conversation behind it. Then Anthropic launched its own editor inside Claude in September, which completely cuts out the middleman between AI synthesis and note-taking. I’ve been using it in regular chats and in Claude Code, and I think it might have started replacing Google Docs for me.
Tomi Engdahl says:
Today’s PHP Security Release, and How We’re Strengthening PHP Security
https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/
Earlier today, the PHP project released PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. These releases fix two critical vulnerabilities that, under the right conditions, allow an unauthenticated attacker to execute code on servers running PHP. If you run PHP, it is imperative that you update now. The announcement on php.net contains and references technical details on the vulnerabilities, attack vectors, and instructions on how to update on which systems.
Tomi Engdahl says:
https://www.infoq.com/news/2026/10/vercel-zig-fx-agent/
Tomi Engdahl says:
https://corellia.fi/seitseman-yleisinta-tapaa-joilla-tiimit-tuhlaavat-pilvirahaa-ja-miten-sen-voi-korjata/?fbclid=Iwb21leAVEqHZleHRuA2FlbQEwAHBkb2YFYWRpZAGrOSIpQc__c3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEewOqxdiuPUftJs_Lv1LpoetdRKb5bVSYdMIEOn9M62aqEJ1lSA3sIjc__Ad8_aem_EvWC-O17sTJLeV-UZXhrzA
Tomi Engdahl says:
ARStack61850 — Real-Time IEC 61850 Instrumentation Stack
ARStack61850 is the real-time, hardware-aware evolution of ARIEC61850.
ARIEC61850 understands IEC 61850. ARStack61850 measures and executes IEC 61850 in real time.
The portable C++20 stack remains rooted in the ARIEC61850 behavioral model, but the project north star is now broader: build an open, deterministic IEC 61850 instrumentation platform for hardware-timestamped Sampled Values/GOOSE/PTP injection, analysis, commissioning and real-time closed-loop testing.
https://github.com/masarray/arstack61850