Link
0 notes
Link
0 notes
Link
0 notes
Link
0 notes
Link
0 notes
Link
0 notes
Link
0 notes
Link
0 notes
Quote
Probably the single most important lesson I’ve learned in my career, the thing that I would argue is the hallmark of “experience”, is understanding just how much work it takes to turn a working program into a viable product. It’s why developer estimates are so notoriously optimistic - and why experienced developers are so notoriously cynical. Let’s say you crank out a bit of code that’ll take responses from a web form and add them in an Excel spreadsheet. That’s not that hard… yay! we just built a Typeform competitor in one afternoon! Except, no, you didn’t. You made one thing work one time on one computer. You haven’t considered encoding, internationalization, concurrency, authentication, telemetry, billing, branding, mobile devices, deployment. You haven’t hit any of the weird limits yet - ever had a system work brilliantly for the first 65,535 requests and then fall over? You don’t have a product. At best, you have a proof-of-concept of a good idea that, if some very smart people work very hard, might become a viable product.
The Problem with “Vibe Coding”
0 notes
Video
youtube
Panel Discussion with GEOFF GRAHAM at Smashing Meets CSS - April 1, 2025
0 notes
Quote
The term “Vibe Coding” was recently coined by Andrej Karpathy. It refers to a coding approach that involves presenting natural language descriptions of a problem to solve and relying on an AI for the actual code generation4. This contrasts with the traditional Craftsman approach of programming by hand from reasoning and memory.
The Last Solo Programmers
0 notes
Link
0 notes
Video
youtube
FOSDEM 2025 tightening every bolt - with Daniel Stenberg
0 notes
Video
youtube
Ruby Galaxy v0.1 Yukihiro "Matz" Matsumoto - Beyond Ruby3
0 notes