Coding trends 2025

731 Comments

1. July 22, 2025 at 7:33 am

   Tomi Engdahl says:

   https://jsdate.wtf/

   Reply
2. July 28, 2025 at 6:19 am

   Tomi Engdahl says:

   Compared to the big beasts of the Linux world, it was always a niche player. However, as with many niche distributions, it had its devoted fans. Those fans clearly did not include Intel’s new boss.

   The Clear Linux OS repo is to be archived in read-only mode, meaning that a fork will be required if anyone chooses to pick up the baton.

   One user on the Clear Linux forums commented: “Seriously? No grace period, users are supposed to instantly migrate? That’s not very serious honestly.”

   https://www.theregister.com/2025/07/23/linux_dev_site_windows/?td=keepreading

   If you’re building a website that will eventually be hosted on a Linux server (as so many are), you have a couple of choices about where you do your development work. You can create a beta version of the site at your web host and upload all of the files there or you can create a local test server that sits in your home or office.

   The test server could be a separate Linux machine such as a Raspberry Pi or it could be your main PC if you run Linux as your desktop OS. If you’re doing your coding in Windows, you could run a local Windows web server, but that’s not the best simulation of your production environment.

   Instead, I recommend using Windows Subsystem for Linux to run a local Linux web server within Microsoft’s OS. That way you can write your code in Windows while running it on the same platform it’s destined for, no second computer or remote server required. Here’s how.

   we’ll install AlmaLinux 9 to use as our Linux distribution. By default, if you don’t install WSL with the –no-distribution option, it will install Ubuntu, but most web hosting platforms use CentOS or AlmaLinux (which is similar to CentOS) so we’re going with that.

   After that, it’s time to install a control panel app for the web server. Many hosting services use cPanel, but that comes with a licensing fee, so we’re going to use Virtualmin and its companion Webmin (Virtualmin controls the server while Webmin controls each account), which is a free alternative. If you already own cPanel or another app, use that.

   If, during the process, you are asked for a fully-qualified domain name, you can enter something like host.example.com just to move the process along. We’ll be using the IP address to get to Virtualmin, Webmin, and our local site.

   Reply
3. July 28, 2025 at 6:20 am

   Tomi Engdahl says:

   EU cloud gang wins Microsoft concessions, but fair software licensing group brands them ‘stalling tactic’
   Pay-as-you-go model, privacy protections agreed – but critics say it just buys ‘Microsoft more time to lock in customers’
   iconLindsay Clark
   Fri 18 Jul 2025 // 06:00 UTC
   Updated A trade group of European cloud providers has claimed a small victory in bringing lower prices and more flexibility in deploying Microsoft software on their infrastructure, though the Coalition for Fair Software Licensing has blasted it as a “stalling tactic” by the software giant
   https://www.theregister.com/2025/07/18/cispe_microsoft_concessions/?td=keepreading

   Reply
4. July 29, 2025 at 11:39 am

   Tomi Engdahl says:

   What happens when you learn a programming language using GenAI — instead of a course?​
   We tried it.​
   The result? Faster feedback, fewer blocks, and surprisingly
   human-like coaching.​

   Read how GenAI is becoming a real partner in learning.

   https://dev.solita.fi/2024/10/11/learning-a-programming-language-with-generative-ai.html?gh_src=ce1383253us&utm_source=facebook&utm_medium=paid_social&utm_campaign=awareness-campaigns&utm_content=blog&utm_creative_format=single_image&utm_marketing_tactic=recruitment&hsa_acc=1021896911210910&hsa_cam=6800932244308&hsa_grp=6800932244708&hsa_ad=6800944677708&hsa_src=fb&hsa_net=facebook&hsa_ver=3&fbclid=IwZXh0bgNhZW0BMABhZGlkAAAGL3k-voQBHnpjgA7H8Gj6klGNF905SyJig0wKpmg0-W19Ay_k7VGtjjhnf1fCa_dDyQJw_aem_n7bHcjPv8NQaTDgfoEcISQ&utm_id=6800932244308&utm_term=6800932244708

   Reply
5. July 29, 2025 at 3:03 pm

   Tomi Engdahl says:

   https://koodiasuomesta.fi/blogi/10-hyvaa-tekoa/haastattelussa-pasi-kovanen-osa-2/

   Reply
6. August 5, 2025 at 7:59 am

   Tomi Engdahl says:

   https://hackaday.com/2025/08/04/a-gentle-introduction-to-fortran/

   Reply
7. August 5, 2025 at 2:31 pm

   Tomi Engdahl says:

   Artificial Intelligence
   Vibe Coding: When Everyone’s a Developer, Who Secures the Code?
   https://www.securityweek.com/vibe-coding-when-everyones-a-developer-who-secures-the-code/

   As AI makes software development accessible to all, security teams face a new challenge: protecting applications built by non-developers at unprecedented speed and scale.

   Just as the smart phone made everyone a digital photographer, vibe coding will make everyone a software developer and will change the software development industry forever.

   Andrej Karpathy, co-founder of OpenAI and former AI leader at Tesla, introduced the term ‘vibe coding’ in a February 2, 2025, tweet. “There’s a new kind of coding I call ‘vibe coding’, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” He was primarily expressing an emotional response to using AI to automate a specific process; but the term took and is now universally used as the general label for AI-generated or assisted programming.

   Vibe coding is a subset of context engineering. If you get the context complete and accurate, it should be possible to plot a path through the context to provide accurate coding. The context comprises the details required for the finished code. This is provided by the coder. The interface between the coder and the AI is natural language (usually English, but not necessarily).

   The AI uses LLM capabilities in this interface, so vibe coding generally uses existing foundational models, such as the newer models of GPT, Claude, or Gemini Pro. Sometimes the LLMs can be integrated with specialized IDEs, such as VS Code, Cursor and Windsurf. Ultimately, however, all the problems that still affect LLMs (such as hallucinations and bias) can also affect the accuracy of vibe coding.

   Vibe coding is new. Although AI has been used within programs for more than 70 years, now it can be used to generate entirely new programs. It has the potential to upend the entire software development industry; but it’s new, and like all new developments, it has its teething problems. Teething problems get sorted over time, but right now we’re still in the teething phase.

   “I like to think of Generative AI in 2025 as like ‘having a website’ in 1999. It’s difficult to sort out the hype from the signal; but underneath all the noise, the reality is that it’s going to impact just about everything we do,” explains Casey Ellis, the founder of Bugcrowd

   “Vibe coding is when you tell an AI, like a chatbot, what you want your software to do using regular words, and it writes the code for you,” says J Stephen Kowski, Field CTO at SlashNext. “This means you don’t need to know how to program; you just describe your idea, and the AI turns it into working software.”

   But if you want complex or unique features, or if you don’t double-check the AI’s work, you might run into problems.

   Strengths and weaknesses

   The biggest apparent strength is speed. “Vibe coding gives you massive acceleration when prototyping web apps, especially with simple known apps with low to moderate complexity,” explains Jonathan Rhyne, co-founder and CEO at Nutrient.

   It democratizes the process of creating software. Anybody with an idea and an understanding of how the idea should work can create a working program. You no longer need to know a programming language, you merely need to know how to use AI – which itself is no mean feat.

   Speed and democratization mean more code at less cost – so the real strength is the economics or vibe coding. It is here, and it must be used lest competitors gain the competitive edge.

   The problem is these strengths come bearing their own weaknesses. ‘Democratization’ is a potential weakness. “There are communities and open-source projects dedicated to providing vibe coders with configuration files that can improve the efficacy of their AI tools,” explains Kaushik Devireddy, senior product manager at Deepwatch.

   “Vibe coders, who may be from non-technical roles, are constantly hunting for new configuration files. The result is an opportunity for bad actors to publish and gain adoption of malicious config files. This creates a brand-new attack-vector, manifesting in the application logic layer – which is a particularly thorny area to secure.”

   Speed can also be a weakness. “On the downside,” says Ellis, “AI is quite good at getting to the ‘90% OK’ solution – but the bad stuff tends to happen in the 10%. Vulnerabilities exist as a probabilistic function of the number of lines of code. We’re producing an increasingly high velocity of lines of code – and more code means more vulnerabilities. On top of this, speed is the natural enemy of quality, and security is a child of quality.”

   “Vibe coding enables non-expert professionals to develop and prototype, but the code it produces will not inherently be secure and could inject vulnerabilities into systems.”

   Inti De Ceukelaire, chief hacker officer at crowdsourced security / bug bounty firm Intigriti confirms this combination of strengths and weaknesses in current vibe coding. “Vibe coding is helpful, but it’s not a magic fix,” he says. “I used it to build a small hacking tool in just one day, which would have taken me weeks to make on my own. It’s also been great for fixing simple bugs or creating quick prototypes. But once a project gets bigger and more complex, the AI starts making more mistakes. At that point, it can take just as long to guide and correct the AI as it would to code it myself from scratch.”

   So, security teams can still benefit from vibe coding by playing to its strengths – small, individual tools focused on defined purposes that can help solve local security concerns without needing to be pretty.

   For larger scale applications with a wider audience, a ‘human in the loop’ is standard advice for all interactions with AI. It offers benefits but should not be considered a solution. “The truly pernicious scenario,” suggests Sohrob Kazerounian, distinguished AI researcher at Vectra AI, “is when keeping a human in the loop leads to a false sense of security and ultimately results in an increase in failures.”

   He almost suggests reversing the emphasis – rather than using a human to check and improve AI-generated code, use AI (in the form of specialist agentic AI) to check and improve human-generated code.

   “You can do things faster. You can be more ambitious about the things you can build, and you can build it on your own and have more fun doing it. You can do things that would have required a team, or a team of teams, of developers,” comments Gene Kim, author and former independent director at the Energy Sector Security Consortium. “There’s something so magical about that, and for me, it’s an amazing time to be alive. I’m outrageously, and I don’t think completely naively optimistic about what it does to our profession.”

   That doesn’t mean that just anybody can immediately produce good code results through vibe coding. The quality of the output is directly proportional to the quality of the input prompts, explains Pukar Hamal, founder and CEO at SecurityPal.AI.

   “You need to understand the basics of software development. You need to know what algorithms are and how they work, and how different lines of code work together to produce good software; and you must be able to phrase your prompt queries clearly and accurately aligned with your intended outcomes. If you can do all this, you are likely to get better code with fewer bugs.”

   If you don’t understand how software fundamentally works, he continues, “Chances are, when you tell an LLM to write a lottery number generating application, it will likely be highly verbose and will potentially have 150 lines of code or more. We have a term that describes this overwhelming amount of low quality generated output that usually comes from a lack of input rigor: ‘AI slop’.”

   But you don’t need to be inexperienced at coding to fall short with vibe coding. Jonathan Rende, CPO at Checkmarx, describes an internal experiment conducted by one of his heads of engineering. “He went round all the different leads in the organization, and set them a task using vibe coding. After 45 minutes he went back round. Those that understood the big picture of how certain things in vibe coding needed to fit together, did a tremendous job. Those who simply tried to apply their old methods of coding, not so much.”

   These were all engineers and developers. Some embraced the future while others simply tried to repeat the past, but faster. “Those who used vibe coding as a new tool to be used in a new way will do well, but the others will become less relevant.” This is the challenge for all coders today — learn to use vibe coding as a new tool with its own rules of engagement, or fall by the wayside since there will be a smaller demand for programmers simply because of the sheer speed of vibe coding used efficiently.

   We’re in this transition phase. Vibe coding still requires a lot of manual intervention to minimize the inherent problems with LLMs, such as hallucinations and bias. “There are inherent problems,” says Kim. “it’s the developer’s job to ensure the AI isn’t calling functions that don’t exist – which can happen. The same engineering skills that we’ve always used are even more important now because AI amplifies the strengths and weaknesses we already have.”

   Rende agrees. “LLMs will get better over time and there will be fewer hallucinations and more automated validation.” But for now, the best way to prevent or limit hallucinations is through more accurate prompts. “The better the question, the better the response; and then being able to check and validate as best as possible. Those are the keys right now: how you ask and how you validate.”

   The problem right now is AI is usually described as probabilistic, while traditional programming is deterministic. We need to shift our approach from working with probabilism rather than determinism. But change is already happening.

   Sola Security has developed a SaaS platform designed to help their security customers solve their own problems

   “You don’t need to be the most expert security person,” explains Dor Swissa, VP R&D at Sola. “Sola will give you that knowledge about security.” And then it helps you to use vibe coding to develop a unique app tailored to your own domain.

   This is perhaps one of the most exciting areas of vibe coding: it has the future potential to allow all firms to have their own uniquely tailored and integrated security apps and break free from the need to buy multiple overlapping solutions that never quite fit the requirement. This is democratization coupled with freedom of movement.

   Summary

   Will there be fewer coders in the vibe coding future? Yes and no. In one sense, everyone will become a developer, so there will be more. Employees will no longer be reliant on submitting a small request to engineering followed by an indefinite wait for a response — they’ll create their own code in minutes rather than waiting for weeks. This is the truly exciting element of vibe coding: power to the people.

   But there will be fewer specialist or full-time professional coders working on large scale, complex apps. One person will do the work of many, faster and more efficiently. And there will be lower emphasis on the creative skills of that coder. Artistry in the coding process will become redundant. Creativity will be limited to the ideation.

   Business exists to create profit, not to employ people. Creativity will be reduced to defining outcomes, while AI will perform the creation.

   Today’s creators will need to make that transition or fall by the wayside. It will apply in the relatively short term to all current ‘creators’ (including programmers through vibe coding, journalists through content creation, and graphic artists through picture generation), and even baristas through the combination of robotics and AI in the longer term. This will happen through the sheer driving force of business economics. Love it or hate it, get over it. Either run with the wind or fight it and fail.

   Reply
8. August 5, 2025 at 2:31 pm

   Tomi Engdahl says:

   Artificial Intelligence
   The Wild West of Agentic AI – An Attack Surface CISOs Can’t Afford to Ignore

   As organizations rush to adopt agentic AI, security leaders must confront the growing risk of invisible threats and new attack vectors.

   https://www.securityweek.com/the-wild-wild-west-of-agentic-ai-an-attack-surface-cisos-cant-afford-to-ignore/

   Reply
9. August 7, 2025 at 7:42 am

   Tomi Engdahl says:

   https://www.securityweek.com/vibe-coding-when-everyones-a-developer-who-secures-the-code/

   Reply
10. August 7, 2025 at 7:42 am

    Tomi Engdahl says:

    https://etn.fi/index.php/tekniset-artikkelit/17716-sulautetut-laitteet-kovassa-kyberpuristuksessa-naein-laitevalmistaja-taeyttaeae-uudet-eu-vaatimukset

    https://etn.fi/index.php/13-news/17727-ensimmaeinen-piiri-joka-estaeae-iot-laitteen-kaappauksen

    Reply
11. August 7, 2025 at 7:43 am

    Tomi Engdahl says:

    Silicon Valley Is in Its ‘Hard Tech’ Era

    Goodbye to the age of consumer websites and mobile apps. Artificial intelligence has ushered in an era of what insiders in the nation’s innovation capital call “hard tech.”

    https://www.nytimes.com/2025/08/04/technology/ai-silicon-valley-hard-tech.html?unlocked_article_code=1.bk8.t0w-.jiIF3FBqqrfO&smid=nytcore-ios-share&referringSource=articleShare

    Reply
12. August 7, 2025 at 11:49 am

    Tomi Engdahl says:

    AI coding tools make developers slower but they think they’re faster, study finds
    Predicted a 24% boost, but clocked a 19% drag
    https://www.theregister.com/2025/07/11/ai_code_tools_slow_down/

    Artificial intelligence coding tools are supposed to make software development faster, but researchers who tested these tools in a randomized, controlled trial found the opposite.

    Computer scientists with Model Evaluation & Threat Research (METR), a non-profit research group, have published a study showing that AI coding tools made software developers slower, despite expectations to the contrary.

    Not only did the use of AI tools hinder developers, but it led them to hallucinate, much like the AIs have a tendency to do themselves. The developers predicted a 24 percent speedup, but even after the study concluded, they believed AI had helped them complete tasks 20 percent faster when it had actually delayed their work by about that percentage.

    “After completing the study, developers estimate that allowing AI reduced completion time by 20 percent,” the study says. “Surprisingly, we find that allowing AI actually increases completion time by 19 percent — AI tooling slowed developers down.”

    The developers then proceeded to work on their issues, using their AI tool of choice (mainly Cursor Pro with Claude 3.5/3.7 Sonnet) when allowed to do so. The work occurred between February and June 2025.

    Artificial intelligence coding tools are supposed to make software development faster, but researchers who tested these tools in a randomized, controlled trial found the opposite.

    Computer scientists with Model Evaluation & Threat Research (METR), a non-profit research group, have published a study showing that AI coding tools made software developers slower, despite expectations to the contrary.

    Not only did the use of AI tools hinder developers, but it led them to hallucinate, much like the AIs have a tendency to do themselves. The developers predicted a 24 percent speedup, but even after the study concluded, they believed AI had helped them complete tasks 20 percent faster when it had actually delayed their work by about that percentage.

    Surprisingly, we find that allowing AI actually increases completion time by 19 percent — AI tooling slowed developers down

    “After completing the study, developers estimate that allowing AI reduced completion time by 20 percent,” the study says. “Surprisingly, we find that allowing AI actually increases completion time by 19 percent — AI tooling slowed developers down.”

    The study involved 16 experienced developers who work on large, open source projects. The developers provided a list of real issues (e.g. bug fixes, new features, etc.) they needed to address – 246 in total – and then forecast how long they expected those tasks would take. The issues were randomly assigned to allow or disallow AI tool usage.

    The developers then proceeded to work on their issues, using their AI tool of choice (mainly Cursor Pro with Claude 3.5/3.7 Sonnet) when allowed to do so. The work occurred between February and June 2025.

    The study says the slowdown can likely be attributed to five factors:

    “Over-optimism about AI usefulness” (developers had unrealistic expectations)
    “High developer familiarity with repositories” (the devs were experienced enough that AI help had nothing to offer them)
    “Large and complex repositories” (AI performs worse in large repos with 1M+ lines of code)
    “Low AI reliability” (devs accepted less than 44 percent of generated suggestions and then spent time cleaning up and reviewing)
    “Implicit repository context” (AI didn’t understand the context in which it operated).

    Other considerations like AI generation latency and failure to provide models with optimal context (input) may have played some role in the results, but the researchers say they’re uncertain how such things affected the study.

    Other researchers have also found that AI does not always live up to the hype. A recent study from AI coding biz Qodo found some of the benefits of AI software assistance were undercut by the need to do additional work to check AI code suggestions. An economic survey found that generative AI has had no impact on jobs or wages, based on data from Denmark. An Intel study found that AI PCs make users less productive. And call center workers at a Chinese electrical utility say that while AI assistance can accelerate some tasks, it also slows things down by creating more work.

    Whomp-whomp: AI PCs make users less productive
    110 comment bubble on white
    People just don’t know how to wrangle chatbots into useful things, Intel says
    https://www.theregister.com/2024/11/22/ai_pcs_productivity/

    Reply
13. August 7, 2025 at 11:49 am

    Tomi Engdahl says:

    https://www.uusiteknologia.fi/2025/03/20/tekoaly-tulee-sulautettuihin-ratkaisuihin-ohjelmointi-ja-sovellukset/

    Reply
14. August 7, 2025 at 7:11 pm

    Tomi Engdahl says:

    Why Developers Are Quietly Returning to VS Code and Ditching Cursor
    Developers lose interest in AI coding tools as Microsoft’s Visual Studio Code gains features, reliability.
    https://analyticsindiamag.com/ai-features/why-developers-are-quietly-returning-to-vs-code-and-ditching-cursor/

    Some shifts in tech are loud. Others, like this one, are a silent walk back to a familiar ground. Over the past few weeks, developers have been gradually admitting that they’re switching back from the AI coding tool Cursor to the integrated development environment Visual Studio Code. The reasons are consistent: reliability, progress of Copilot, and a dawning realisation that features mean little when the basics break. Cursor, once the standout of the AI developer tool scene, is now seeing loyal users migrate, not because it failed, but because Microsoft quietly caught up. Even those who still like Cursor are leaving without drama. Copilot Catches Up to Cursor Santiago Valdarrama, a computer scientist, took to X and said, “I’m officially going back to VS Code. Incredible pro
    Subscribe or

    Reply
15. August 14, 2025 at 11:46 am

    Tomi Engdahl says:

    Ransomwaren koodaajat löysivät Rustin
    https://etn.fi/index.php/13-news/17779-ransomwaren-koodaajat-loeysivaet-rustin

    Heinäkuun kyberuhkakatsaus kertoo selkeää kieltä: kiristyshaittaohjelmat eivät ole hiipumassa, vaan niiden kehitys kiihtyy. Check Point Researchin mukaan kiristyshaittaohjelmatapaukset kasvoivat maailmanlaajuisesti 28 % viime vuoden heinäkuuhun verrattuna. Kolme ryhmää – Qilin, Inc. Ransom ja Akira – hallitsivat kenttää, ja erityisesti Qilin ja Akira ovat siirtyneet käyttämään ohjelmointikieli Rustia hyökkäystyökalujensa kehittämisessä.

    Miksi Rust kasvattaa suosiotaan verkkorikollisten parissa? Rust on moderni ohjelmointikieli, joka yhdistää korkean suorituskyvyn ja vahvat muistiturvaominaisuudet. Se käännetään suoraan natiiviksi konekoodiksi, mikä mahdollistaa tiedostojen nopean salauksen ennen kuin uhri ehtii havaita hyökkäystä.

    Rustin monialustatuki helpottaa haittaohjelman rakentamista eri käyttöjärjestelmille – Windowsille, Linuxille ja ESXi-ympäristöille – samasta lähdekoodista. Lisäksi Rustin käännösjälki ja modulaarinen rakenne tekevät haittaohjelmien tunnistamisesta ja purkamisesta vaikeampaa perinteisille tietoturvatyökaluille. Binäärit voivat näyttää analysointityökaluissa epätavallisilta, mikä heikentää tunnistusta, ja kielen rakenteet tukevat helposti obfuskointia eli koodin tarkoituksen peittämistä.

    - Rustin käyttö on osoitus siitä, että hyökkääjät seuraavat ohjelmistokehityksen trendejä yhtä tarkasti kuin puolustajat. Kyberrikolliset hyödyntävät samoja moderneja kehitystyökaluja, jotka tekevät laillisista sovelluksista nopeampia ja turvallisempia

    Heinäkuussa Qilin hyödynsi Rust-pohjaisia salausohjelmia erityisesti terveydenhuollon ja koulutusalan organisaatioihin kohdistuvissa hyökkäyksissä, kun taas Akira käytti Rustia optimoidakseen hyökkäyksensä virtualisointiympäristöihin.

    Reply
16. August 15, 2025 at 2:25 pm

    Tomi Engdahl says:

    Why LLMs Can’t Really Build Software. LOL. Vibe coding and auto code generation are only good if you know what you’re doing and have a background/experince in programming. But, like everything in life, a few people overhyped it.
    https://www.facebook.com/share/16yvB3udLn/

    Read blog https://zed.dev/blog/why-llms-cant-build-software if you want details

    Reply
17. August 15, 2025 at 2:26 pm

    Tomi Engdahl says:

    I am a software developer, but with “vibe coding” I have been able to make quite a few apps / tools in coding languages I have next to no experience with.

    Yesterday I made a OpenStreetMaps webapp, that can plan routes both on roads and small paths pretty similar to Google Maps. I have not had my hands directly on any of the code.

    Of course it always helps having experience. If an LLM runs into problems that it cannot easily solve it might end up running into a very annoying error loop where it keeps trying the same 3-4 solutions.

    I would compare it a bit to doing web searches… if you know what you are searching for its much easier to come up with good keywords. Its the same when having an LLM making an app for you, it helps a lot to know how to describe what you want, and what the different concepts and such are called.

    It also helps a LOT that I have used LLMs for more than 3 years now and mainly to do coding stuff. So I have become better at “prompting” and the LLMs have gotten better tools for what they do. Claude Code is pretty amazing, but VS Codes agent feature is also quite strong and its actually better than Claude Code in some ways because of having such good integration that when you install extensions in VS Code the LLM can have access to information from those extensions as well.

    I have made a lot of apps where I did not look at the code at all. Of course an important thing to mention is that these apps are all hobby projects. At work I do not think I have done a full tool or app only using vibe coding. For production use I would not trust AI coded stuff enough to not double check it all… well, unless maybe its some local tool with a simple input and output requirement. If there is no web access needed, the possible security problems should be minimal.

    https://www.facebook.com/share/16yvB3udLn/

    Reply
18. August 18, 2025 at 7:32 am

    Tomi Engdahl says:

    https://hackaday.com/2025/08/17/recto-in-case-programming-isnt-hard-enough/

    Reply
19. August 18, 2025 at 8:44 pm

    Tomi Engdahl says:

    https://thehackernews.com/2025/08/cursor-ai-code-editor-vulnerability.html

    Reply
20. August 18, 2025 at 8:44 pm

    Tomi Engdahl says:

    Vibe Coding: The Shadow IT Problem No One Saw Coming
    Vibe coding promises easy AI-generated software but creates massive shadow IT risks for enterprises. Learn why this trend threatens security, compliance and scale.
    https://thenewstack.io/vibe-coding-the-shadow-it-problem-no-one-saw-coming/

    Reply
21. August 18, 2025 at 8:46 pm

    Tomi Engdahl says:

    https://thenewstack.io/platform-engineering-is-failing-heres-why-infrastructure-comes-first/

    Reply
22. August 18, 2025 at 8:46 pm

    Tomi Engdahl says:

    The Problems With React Server Components
    React Server Components (RSCs) are struggling to find their foothold among developers, according to a recent panel at the React Summit 2025.
    https://thenewstack.io/the-problems-with-react-server-components/

    Reply
23. August 19, 2025 at 5:16 pm

    Tomi Engdahl says:

    “Learn to Code” Backfires Spectacularly as Comp-Sci Majors Suddenly Have Sky-High Unemployment
    “Every kid with a laptop thinks they’re the next Zuckerberg.”
    https://futurism.com/computer-science-majors-high-unemployment-rate

    It looks like the “learn to code” push is backfiring spectacularly for those who bought in.

    As Newsweek reports, recent college graduates who majored in computer science are facing high unemployment rates alongside the increasing probability of being laid off or replaced by artificial intelligence if and when they do get hired.

    In its latest labor market report, the New York Federal Reserve found that recent CS grads are dealing with a whopping 6.1 precent unemployment rate. Those who majored in computer engineering — which is similar, if not more specialized — are faring even worse, with 7.5 percent of recent graduates remaining jobless. Comparatively, the New York Fed found, per 2023 Census data and employment statistics, that recent grads overall have only a 5.8 percent unemployment rate.

    Reply
24. August 19, 2025 at 5:58 pm

    Tomi Engdahl says:

    A new worst coder has entered the chat: vibe coding without code knowledge
    In the age of AI, being able to make applications and create code has never been easier. But is it any good? Here’s what vibe coding is like for someone without technical skills.
    https://stackoverflow.blog/2025/08/07/a-new-worst-coder-has-entered-the-chat-vibe-coding-without-code-knowledge/

    Reply
25. August 19, 2025 at 5:58 pm

    Tomi Engdahl says:

    Turn ideas into apps in minutes.
    Turn any sentence into a working app. Not a mockup, an actual app. Its not magic, but it might feel like it. Prepare to have your mind blown…
    https://go.famous.ai/app?fbclid=IwQ0xDSwMEB_hleHRuA2FlbQIxMQABHsiPoP8Y0wd-rHgh3KdBXVTjPxv2rnyvqtM-pUKSY6GG3d2zdLcG3wGBb5BJ_aem_EpOJ2eJv9x6Db9a74MPuJw

    Reply
26. August 19, 2025 at 5:59 pm

    Tomi Engdahl says:

    Trust in AI coding tools is plummeting
    According to Stack Overflow’s 2025 developer survey.
    https://leaddev.com/technical-direction/trust-in-ai-coding-tools-is-plummeting

    A new Stack Overflow survey highlights a steep decline in trust and reliance on AI coding tools, as users get more discerning.

    Stack Overflow’s annual survey of nearly 50,000 developers acts as a useful benchmark of how software engineers are feeling, and this year’s results suggest a steep decline in sentiment around AI coding tools.

    This year, 33% of developers said they trust the accuracy of the outputs they receive from AI tools, down from 43% in 2024. At the same time, how favourably developers think of adding AI tools into their workflow fell steeply, from 72% in 2024 to 60% this year.

    Reply
27. August 19, 2025 at 6:06 pm

    Tomi Engdahl says:

    https://thenewstack.io/endor-fire-up-a-dev-environment-in-seconds-with-webassembly/

    Reply
28. August 19, 2025 at 6:07 pm

    Tomi Engdahl says:

    The International Obfuscated C Code Contest is back for 2024
    Yes, 2024 – the prizes in the 40th anniversary edition prizes were just awarded
    https://www.theregister.com/2025/08/09/ioccc_2024/

    Reply
29. August 19, 2025 at 6:08 pm

    Tomi Engdahl says:

    https://thenewstack.io/vector-search-is-reaching-its-limit-heres-what-comes-next/

    Reply
30. August 20, 2025 at 7:48 am

    Tomi Engdahl says:

    AWS:n Kiro on uusi, laadukasta koodia tuottava apuri
    https://etn.fi/index.php/13-news/17796-aws-n-kiro-on-uusi-laadukasta-koodia-tuottava-apuri

    Amazon Web Services (AWS) on julkistanut Kiron, uuden tekoälyavusteisen koodieditorin, jonka tarkoitus on viedä AI-kehitys prototyypeistä tuotantoon. Kiro eroaa monista muista tekoälyapureista siinä, että se ei tyydy pelkkään “promptaa ja koodaa” -malliin, vaan ohjaa kehittäjää suunnitelmallisempaan ja dokumentoidumpaan prosessiin.

    Perinteinen vibe-koodaus eli nopea, iteratiivinen prototypointi, jossa tekoälyn annetaan tuottaa koodia, on hauskaa ja hyödyllistä, mutta siihen liittyy ongelmia. AI tekee usein oletuksia, joita ei dokumentoida, ja lopputulos voi näyttää toimivalta mutta sisältää teknistä velkaa, heikkoa ylläpidettävyyttä tai puutteita turvallisuudessa ja skaalautuvuudessa. Kiron idea on ratkaista nämä ongelmat tuomalla AI-kehitykseen rakenteen ja suunnittelun.

    Kiron ydin on niin sanottu spec-driven development eli vaatimuksiin perustuva kehitys. Ennen kuin koodia kirjoitetaan, Kiro auttaa laatimaan speksit eli vaatimukset: käyttäjätarinat, hyväksymiskriteerit ja tekniset suunnitelmat. Näin oletukset tehdään näkyviksi ja niihin voidaan palata myöhemmin. Spesifikaatioiden pohjalta Kiro generoi automaattisesti myös suunnitteludokumentit, kuten kaaviot ja API-määrittelyt.

    Kun suunnitelmat on hyväksytty, Kiro luo niistä tehtävälistan (tasks.md), jossa työ jaetaan selkeisiin vaiheisiin. Jokainen tehtävä linkittyy vaatimuksiin, ja mukana ovat myös testit, lataustilat, mobiiliresponsiivisuus ja saavutettavuusvaatimukset. Kehittäjä voi sitten suorittaa tehtävät yksi kerrallaan, seurata etenemistä ja tarkastella AI-agentin tekemiä muutoksia.

    Reply
31. August 20, 2025 at 7:58 am

    Tomi Engdahl says:

    Lisp In 99 Lines Of C With TinyLisp
    https://hackaday.com/2025/08/19/lisp-in-99-lines-of-c-with-tinylisp/

    As one of the oldest programming languages still in common use today, and essential for the first wave of Artificial Intelligence research during the 1950s and 60s, Lisp is often the focus of interpreters that can run on very low-powered systems. Such is the case with [Robert van Engelen]’s TinyLisp, which only takes 99 lines of C code and happily runs on the Z80-based Sharp PC-G850V(S) pocket computer with its 2.3 kB of internal RAM and native C support.

    https://github.com/Robert-van-Engelen/tinylisp

    Reply