061: As a Gopher I'm excited about Gleam, maybe you'll too
I finally gave Gleam a serious look and ho boy I'm excited. I've looked at Gleam a long time ago back when it started with the ML-like syntax. I've always been an Elm fan, I discovered functional programming with Elm. Near 2016-2017 I tried Elixir and Phoenix, and gave it a try multiple times following the years, but I'm not fully sure why it never clicked completely for me.As someone engage with Go for the last 10+ years, I won't lie that I was looking for some excitement lately. Not because I'm tired of Go or anything, I've dabbled seriously into Python/Django in the last 3-4 years. But Gleam, at least so far, as this I don't know what that I felt when I started Go back in 2014.There's so many programming languages these days that I suppose it's really comes down to a matter of taste. I do have some minimal checkboxes that a language must checked before I even considered looking at it, and Gleam was checking them all. It's a refreshing language after 10 years of Go. Just another tool in the toolbox, but I'm extremely picky about which tool I put in my toolbox haha, so Gleam for now is in the evaluation phase, but so far I'm excited and I haven't felt like this for a long time.
--------
35:33
--------
35:33
060: 10x Developer, or 10x Distraction? A Reality Check on AI
The message is everywhere: LLMs are here to make us 10x more productive and change software development forever. Venture capitalists are pouring billions into the vision, and big tech companies are pushing hard for us to adopt the tools. But as a software engineer who’s seen the demos and lived the reality, something feels profoundly wrong.This week, I’m taking a step back to reflect on the current state of our industry. We'll explore the inconvenient truth that often gets lost in the hype: that relying on AI can sometimes make us slower, introduce more technical debt, and even erode the fundamental skills that make us valuable.But maybe the real problem isn't the technology itself. Maybe it's that we're looking for a quick fix for a deeper issue. Join me as we discuss what really drives developer productivity, the crucial importance of domain knowledge, and whether anyone is even considering the quality of life for the people building our systems.Because while the "going from 0 to 1" demo is impressive, our jobs are about maintaining complex systems from 1 to 1000. And maybe, just maybe, an agentic flow that doesn't care about our codebase isn't the real solution we need.p.s. And yes, I used LLM to improve my description draft ;)
--------
28:18
--------
28:18
059: Is Go over with John Arundel
Let's talk with a friend of the pod, John Arundel. We talk about state of thing a little regarding Go's maturity, a bit of AI, I personally am a bit fatigue of the noise and "agent". The podcast is returning slowly. , John has written a new Go book that's beginner-friendly, but goes deeper than you'd expect, he produce excellent learning and training resources.Links:The Deeper Love of GoJohn's newsletter
--------
1:02:03
--------
1:02:03
058: Starting in Go with Yann Bizeul
Go is used by multiple programmers and software engineers. Lots of path can lead to want to try Go, and this week I talk with Yann whom eventually found Go and talks about his experiences writing internal tools at his company.Links:HuploadYBFeed
--------
1:06:12
--------
1:06:12
057: I unite with another technical professional, and we talk about being blind in tech (part 2)
The part 2 of my talk with Ivan Fetch. We cover the remaining listener questions and go over some aspects in more details of being blind in tech.
New Zealand