Ai

I’ve been playing around with Cursor and Windsurf, because I keep seeing on social media how great these tools are and how easy it is to build things. And you know what? It’s…. ummm… better than before? Okay, look, it’s impressive. If I compare it so some earlier versions of the IDEs and other tools like Bolt.new, sure, it’s improved. But sheesh, does it take poking and prodding and coddling to get somewhere. Maybe I’m using it wrong, I don’t know, but I wish I could share the transcripts of my chats with these tools so you’ll understand… (can I export those? am I missing a feature somewhere?) ...

Wow, the new Mac Studios look really impressive. I can’t find the post that I saw last night about it, so I can’t share that author’s thoughts (I thought I commented or reacted at least, apparently not…), but what was interesting is the M3 Ultra goes up to 512GB of unified memory. 512GB… Of unified memory… If you’ve been playing with LLMs locally, and you have Apple Silicon, you’ll know that Apple’s unified memory is pretty performant, and it’s great for running local LLMs because the GPU uses the same system memory as the CPU, which means it can access most if not all of the RAM. ...

The Promise vs. Reality of AI in Tech I’m genuinely excited about recent AI advancements. The tools continue improving, and we’re discovering more ways to optimize and enhance our work. I’ve personally found a good rhythm using AI to multiply my skills rather than replace or hinder them. However, I’m concerned about the industry’s direction with these improvements. Instead of creating better developers, we’re often replacing them. Rather than building amazing accessibility tools, we’re creating deep fakes and virtual companions. ...

🎯 This morning’s YouTube recommendation: someone coding purely by voice using Cursor agents and Windows dictation tools. My first thought? Not “wow, how cool!” but “seriously, is typing that hard now!?” 🙄 My second thought: “Good luck remote debugging a Linux server at 1am to fix what your AI buddy broke…” First we outsource thinking to AI, now the typing… it’s like nobody wants to actually do this job anymore! 🤦 But here’s the thing - after my initial skepticism, I realized this IS actually pretty cool. Just not for the reasons filling up your social media feed. ...

🤖 I love how every new LLM release triggers a wave of “AI is coming for your job!” posts, only for people to realize a few weeks later “oh, nope, sorry, not this yet” 😏 💡 While AI tools are certainly force multipliers for productivity, even with agents, they’re not replacing humans yet. Even the best apps I’ve generated with Bolt or Replit eventually need human intervention and fixing. 🎯 Hot take incoming: I find it amusing when people consider these simplistic example AI-generated “apps” as “real development”. Most modern webapps are already essentially just careful combinations of frameworks and styling, using existing tools that solve problems in generic ways. That’s not novel software development. ...

Over a year ago a wrote a post about how I felt that, even though ChatGPT was making me more productive, I also felt it was making me lazier and dumber. Since then, I’ve been a lot more intentional about how I use AI tools, in particular generative AI tools and coding assistants. It should be a multiplier, not a replacement or crutch, which is something I see juniors and non-developers struggle with the most, but clearly we can all fall prey too. ...

Right, so it’s been a minute since I last posted something. Like many other companies this last year, we weren’t spared layoffs. While I still have my job, my team has been greatly reduced, both from people leaving when they saw the signs and from people being let go. So while fighting survivors guilt and an increased workload, posting hasn’t been my first priority. But while doing my day to day and trying to keep my head down and deliver as much as possible as quickly as possible, I noticed something. And I’m not sure how I feel about it, other than we need to talk about it. ...

Introduction So very many years back when I was but a fledgling coder, armed with BASIC skills and deep into a Turbo Pascal with Objects book, I remember a conversation with my dad. Frustrated by the level of specificity needed to communicate with a machine, I asked, “Why has no-one made a programming language where I can just tell it ‘build this game for me’?” My dad, in his infinite wisdom, mused that cracking that puzzle – creating a natural language programming language – was a feat yet to be achieved. “Whoever manages to do that,” he predicted, “will make a fortune.” ...

I originally started writing this post at the end of 2022 but never finished it. Originally titled “Why LowCode/NoCode both excites and terrifies me!”, with the buzz around ChatGPT over the last months, I decided to 1) finish the post, and 2) update it to include AI tools like CoPilot and ChatGPT. So here, finally, is the update. Also a little different to my usual style. I didn’t like it. ...

… why developers should focus more on code than how much they make. Been meaning to do this myself for a while as a discussion post, but haven’t gotten around to it. I’m busy reading Masters of Doom, which has been on my “to read” list for a long time, but after watching the 5+ hour interview between Lex Fridman and John Carmack, I decided it’s time. And in there I was reminded of a quote attributed to Carmack about his motivations for getting into development. ...