Coding trends 2026

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

736 Comments

  1. Tomi Engdahl says:

    https://etn.fi/index.php/13-news/19225-tekoaely-muuntaa-ubuntun-koodin-rustiksi

    Linux-jakeluversio Ubuntusta ehkä parhaiten tunnettu Canonical käynnistää Bristolin yliopiston kanssa tutkimushankkeen, jossa tekoälyn avulla yritetään muuntaa suuria C-koodikokonaisuuksia turvallisemmaksi Rustiksi. Ensimmäisinä käytännön testikohteina ovat Ubuntun tietoturvalle tärkeät AppArmor ja snap-confine.

    Taustalla on Linux-maailman vanha ongelma. Suuri osa järjestelmäohjelmistoista on kirjoitettu C:llä, mutta Rust tarjoaa paremman suojan monia muistiturvallisuusvirheitä vastaan. Koko olemassa olevan C-koodin kirjoittaminen käsin uudelleen olisi kuitenkin hidasta, kallista ja riskialtista.

    Canonicalin mukaan perinteiset C:stä Rustiin kääntävät työkalut pystyvät käsittelemään paljon koodia, mutta lopputulos säilyttää usein C:n rakenteet liian kirjaimellisesti. Rust-koodi saattaa kääntyä, mutta käyttää edelleen runsaasti unsafe-toimintoja ja vaatia paljon käsityötä.

    Kielimallit taas osaavat tuottaa pienistä kokonaisuuksista siistiä ja Rustille luontevaa koodia, mutta niiden ongelmana ovat suuret ohjelmistovarastot ja ennen kaikkea luotettavuus. Hyvältä näyttävä Rust-koodi ei vielä tarkoita, että ohjelma toimisi täsmälleen kuten alkuperäinen C-versio.

    Siksi Canonical ei aio jättää muunnosta pelkän tekoälyn varaan. Kehitteillä oleva järjestelmä jakaa ensin suuren koodivaraston sopiviin osiin niin, että tyyppien, riippuvuuksien ja ohjelman toiminnan kannalta tärkeä konteksti säilyy. Sen jälkeen kielimalli muuntaa C-koodin Rustiksi.

    Seuraavassa vaiheessa uusi Rust-versio tarkistetaan alkuperäistä C-koodia vastaan. Menetelmissä on tarkoitus käyttää muun muassa fuzz-testausta ja formaalimpia vastaavuuden tarkistusmenetelmiä. Jos validointi epäonnistuu, järjestelmä yrittää paikantaa ongelman ja korjata käännöstä automaattisesti.

    Reply
  2. Tomi Engdahl says:

    Same As It Ever Was
    https://hackaday.com/2026/08/29/same-as-it-ever-was/

    Whether you like it or not, the use of LLMs to write code is kind of a big deal at the moment. We’ve been asking ourselves what, if anything, this means for us here at Hackaday. Should we try to figure out what percentage of a project was done by an actual human and how much was done by a machine? Does it really matter? What is our AI policy anyway?

    Reply
  3. Tomi Engdahl says:

    https://hackaday.com/2026/09/06/wordstar-lives-again-and-again/

    The idea is simple. Take a vintage copy of WordStar for MSDOS, wrap it with DOSBox, and package it up with some basic scripts for Linux, Mac, or Windows. In addition, there’s a WebAssembly version for the browser if you’re into that sort of thing.

    On Linux, the wordstar.sh file grabs the current directory and sends it to launch.sh. This script makes sure everything is ready, builds a DOSBox config file from a template, and launches everything. The only problem is that it doesn’t correctly resolve symlinks if you want a link on your path.

    Reply
  4. Tomi Engdahl says:

    A 1024 Byte Python Interpreter
    https://hackaday.com/2026/09/08/a-1024-byte-python-interpreter/

    Like many of us, [Austin] finds writing code satisfying — especially if it is challenging. His latest challenge: shoehorn something that looks like Python into 512 bytes. Ok, that didn’t work out, but would you believe 1024 bytes of source code?

    The goal was to properly execute a fizzbuzz program using a decidedly Python-like syntax. Since he is only interpreting Python, some things were simplified. In addition, he tried hard to minimize things like whitespace and variable names. Still, there were other things to do, and he borrowed from tips for code golfing.

    https://austinhenley.com/blog/python1024.html

    Reply
  5. Tomi Engdahl says:

    Sonia Sirletti / Bloomberg:
    Bending Spoons agrees to acquire Miro in an all-cash transaction valuing the workplace-collaboration platform at $1.36B

    https://www.bloomberg.com/news/articles/2026-09-10/bending-spoons-agrees-to-buy-workspace-miro-for-1-36-billion

    Reply
  6. Tomi Engdahl says:

    We don’t need Claude Code anymore and the best replacement is free | Read More: bit.ly/3UVb2vA

    Being tied to Anthropic’s AI models and subscription plans is probably one of the most disappointing aspects of Claude Code! You end up paying quite a lot every month, even when you can’t access all models. But what if we no longer need Claude Code? What if you could bring the models you want into a more open coding agent? I’ve been testing one of the best replacements for Claude Code recently — Qwen Code — and it is more flexible than you imagine. The best part? It is completely free to use.

    Reply
  7. Tomi Engdahl says:

    Tekoäly on jo vaatimus joka toisessa softaprojektissa
    https://etn.fi/index.php/13-news/19295-tekoaely-on-jo-vaatimus-joka-toisessa-softaprojektissa

    – Tämä ei ole hypeä, vaan näkyy konkreettisesti liiketoiminnassa, sanoo IT-palveluyhtiö Wittedin toimitusjohtaja Markus Huttunen. Yhtiön uusista ohjelmistokehityksen toimeksiannoista jo noin puolessa tekoälyn käyttö on keskeinen vaatimus.

    Wittedin mukaan tekoäly ei näissä projekteissa ole enää pelkästään kehittäjän työtä nopeuttava apuväline. Sitä käytetään koko tuotekehityksessä liiketoiminnan tarpeiden määrittelystä arkkitehtuurisuunnitteluun ja koodin tarkastamiseen.

    Yhtiön sisäisessä kyselyssä 82 prosenttia ohjelmistoammattilaisista kertoi käyttävänsä tekoälytyökaluja päivittäin. Yhtä suuri osuus katsoi tekoälyn muuttaneen tapaansa tehdä työtä.

    Erityisen suuri ero näkyi AI-agenttien käytössä. Niitä säännöllisesti käyttävistä 96 prosenttia arvioi työnsä muuttuneen merkittävästi. Agentteja käyttämättömistä näin arvioi 45 prosenttia.

    Reply
  8. Tomi Engdahl says:

    LabVIEW’ta koodaava Nigel tallentaa keskustelut vain paikallisesti
    https://etn.fi/index.php/13-news/19294-labview-ta-koodaava-nigel-tallentaa-keskustelut-vain-paikallisesti

    Emerson on kertonut uusia yksityiskohtia NI Nigel -tekoälynsä tietoturvasta ja tulevasta kehityksestä. LabVIEW-koodia ja TestStand-testisekvenssejä tuottava Nigel käyttää OpenAI-malleja Microsoftin Azure-ympäristössä, mutta käyttäjän keskustelut tallennetaan vain paikallisesti.

    Emersonin mukaan Nigel toimii yhtiön suojatun pilvialustan päällä ja hyödyntää Azuressa ajettavia OpenAI-malleja. Käyttäjän promptit tallennetaan kuitenkin paikallisesti, eikä Emersonilla ole pääsyä Nigel-keskusteluihin, ellei käyttäjä itse erikseen jaa niitä yhtiölle.

    Tietoturvaratkaisu on olennainen erityisesti testausympäristöissä, joissa tekoälylle voidaan antaa käsiteltäväksi tietoja testattavasta järjestelmästä, mittausjärjestelyistä ja ohjelmistosta. Nigel on integroitu suoraan NI:n testausohjelmistoihin yleiskäyttöisen selainpohjaisen tekoälypalvelun sijaan.

    Reply
  9. Tomi Engdahl says:

    https://www.facebook.com/share/p/19ZEiapNXM/

    Marco Grossi built one of the internet’s most useful websites almost by accident.

    In 2010, he needed a simple way to work with a PDF.

    So he created his own tool.

    That personal project became iLovePDF.

    Today, millions of people use the site to merge, split, compress, convert and edit PDF files.

    But despite its huge popularity, Grossi has kept the company independent.

    He has said he has no outside investors and no interest in selling it.

    He doesn’t even entertain acquisition proposals.

    And while iLovePDF now offers paid premium features, many of its most useful tools remain free.

    What started as one person solving his own problem became a tool used around the world.

    Sometimes the best businesses begin with one simple question:

    “Why isn’t there an easier way to do this?”

    Reply
  10. Tomi Engdahl says:

    Alix Coutures / The Information:
    Some developers are using the Claude Code harness to access cheaper non-Anthropic models, such as OpenAI’s GPT-5.6 Sol, via proxies and services like OpenRouter

    https://www.theinformation.com/newsletters/ai-agenda/developers-find-ways-use-claude-code-without-anthropic-models

    Reply
  11. Tomi Engdahl says:

    Someone just vibe-coded an operating system from scratch, and it can actually run DOOM | Read More: bit.ly/4gTmEI7

    Reply
  12. Tomi Engdahl says:

    “In reality, nobody is thinking anymore.” https://trib.al/OalxLSM

    Code Red
    Software Engineer Says AI Is Causing Chaos Among Coders Who Now Just “Press Enter” All Day, Have Stopped Thinking or Understanding Software
    “In reality, nobody is thinking anymore.”
    https://futurism.com/artificial-intelligence/software-engineer-ai-chaos-press-enter-all-day?fbclid=IwdGRjcAUgzONjbGNrBSDMxHBkb2YFZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEefWnPdo2eueJOKmbizrYgNEo-Gpy5JGxEJfX7lvazLVC8NMjfvm24S5F_BcU_aem_81ha9Mmh96RBShDIzXdFMg

    The advent of powerful AI coding tools has quickly made programmers heavily reliant on the tech, with experts warning that they’re slowly but surely losing the ability to write code by hand.

    It’s a growing existential crisis that’s significantly raising the chance of errors or security issues in AI code that hasn’t been properly vetted. Experts are warning of a “class divide” between those, who are over relying on AI tools and more experienced coders, or “craftsmen,” who are left wading through the former’s group’s output and applying any necessary fixes.

    Reply
  13. Tomi Engdahl says:

    You reap what you sow. https://trib.al/ZUaiTbQ

    Code Overload
    The Effects of AI-Generated Code Tearing Through Corporations Is Actually Kind of Funny
    Womp womp!
    https://futurism.com/artificial-intelligence/ai-code-tearing-through-corporations?fbclid=IwdGRjcAUiTvFjbGNrBSJOz2V4dG4DYWVtAjExAHBkb2YFc3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEeYkU3864V42sO4SrzUjv8Jw-MJyna-AnD8Z4zZPt91H5dvGZ4z6okH1gGIuA_aem_V9l4gaSeeVtqdetGj7Vdsw

    Corporations are rapidly embracing AI to churn out mountains of code.

    Outwardly, this is presented as a revolution in productivity. But a behind the scenes look in The New York Times paints a slightly different, and somewhat comic, picture. Beleaguered programmers are being saddled with more code than what they know what to do with, while their employers struggle to find the best way to get them to check all the AI’s hastily written work.

    One financial services company, for example, saw its coding output increase tenfold after embracing the popular AI tool Cursor — creating an epic backlog of one million lines of code that needs to be reviewed, according to Joni Klippert, CEO of the security startup StackHawk, which works with the financial firm.

    And the code glut isn’t something that can be ignored. Left unchecked, bad code — regardless of whether it’s AI-generated or human-written — can gum up software and cause security flaws. Amazon and Meta both recently experienced disruptions after AI tools took unauthorized actions, and those are just the ones we’ve heard about.

    “The sheer amount of code being delivered, and the increase in vulnerabilities, is something they can’t keep up with,” Klippert told the NYT. The accelerated output created a “lot of stress” in other departments, like sales and marketing support, she added.

    Companies are still grappling with how to address the code glut. “The blessing and the curse is that now everyone inside your company becomes a coder,” Michele Catasta, the president and head of AI at the startup Replit, told the NYT.

    Sachin Kamdar of the AI agent startup Elvix took a hardline approach: all code must be reviewed by a human, because it’d be harder to fix down the line if no one understood what the AI cooked up in the first place.

    “It’s just going to break something, and they’re not going to know why it broke,” he told the NYT.

    Another solution is throwing more AI at the problem. Anthropic and OpenAI have released AI agents designed to review code. And in December, Cursor, the provider of the much hyped AI coding tool, bought the startup Graphite, which builds an AI code reviewing platform.

    Reply

Leave a Comment

Your email address will not be published. Required fields are marked *

*

*