Dette gir faktisk mening for meg, fordi AI er flott for bilder, video, brukergrensesnitt og alt der vi kan verifisere med øyet. Og Replit genererer nyttige prototyper hvis funksjonalitet umiddelbart kan verifiseres visuelt. Det gjør enkelt alt som skal være enkelt.
Amjad Masad
Amjad Masad30. juli 2025
A public company CEO told me AI coding has had negligible impact on his engineering teams, instead the real transformation has been on their product and design teams using Replit. I asked him how does he reconcile this with CEOs saying that 25-50% of code is generated by AI? He said that’s also true in their case—AI does generate a lot of their code—but that whatever time saved in generating the code is lost back in debugging, reverting bugs, and security audits. So if you measure time to ship, PRs merged, or whatever high-level metric you don’t see any impact. Whereas his non-technical teams gained a fundamentally new super power of being able to make software. Prototyping with Replit makes iteration speed incredibly faster before it gets to engineering. And non-product teams—like HR—can for the first time solve problems where vendors don’t have the exact solutions they’re looking for. I was surprised to hear the part about engineering teams, and I’m sure every company will be different, but it made sense the profound impact coding agents are having on non-technical folks.
Det er slik jeg tenker om Replit i dag. Det er nesten som konseptet minimum beskrivelseslengde (MDL) fra informatikk. Hvis det er konseptuelt enkelt, hvis det du ønsker faktisk kan beskrives i noen få setninger eller en interaktiv økt (fordi spørsmål også er en ferdighet), så gjør Replit det enkelt. For enhver form for dataanalyse eller CRUD-app eller eksempelkode om hvordan et API skal fungere, er Replit bare utrolig nyttig selv om du er en dyktig utvikler. Og for den ikke-tekniske, men verbale brukeren, kan de nå sende PM til hva som helst. Hvis de anstrenger seg, kan de vise hva de tenker på.
108,84K