So, I get that AI must be used. But who the f*ck wants YouTube videos auto dubbed (badly)? Like if I want bad dubbing, at least let me choose it, don't make it a default!

I had the opportunity to make myself unhireable for the small price of self vindication on LinkedIn. I am quite proud to say I let it go and I remain (barely) hireable.

#ruby (and #rails) people. What is a fat model for you? I feel like 'fat model' has become a short hand for: this has a lot of lines Rather than: This does too many things

A few days ago, Asli and Sami joined me to talk about bootcamps. Do you think bootcamps are here to stay? More here: open.spotify.com/episode/40F1...

I said this on a slack I am part of: I am more and more opposed to code reviews and see less and less sense to them. Especially asynchronous code reviews. A friend called on me to expand, so here are the thoughts I shared (not very organized, sorry): 👇

🚨 New Episode Alert!🚨 A few days ago I was joined by Dave and Steven to discuss misunderstood concepts in tech. We strayed away from that so as a bonus you also get: - A comparison of the state of the car industry vs the tech industry 60 years in. 👇

With all these bugs I have, I don't have time to write tests!

What kind of insanity is scented tissues?

🚨 New Episode Alert 🚨 A couple days ago Aslihan and Sami joined me to talk about bootcamps. What has been their experience joining the industry? What would they recommend to new graduates? What is the place of bootcamps today and in the future? open.spotify.com/episode/40F1...

What is stopping us from releasing more often and more predictably is a question we should ask ourselves more often.

Processes should be at the service of alignment, either intra-team or extra-team. You should not be afraid of removing processes but you should not be afraid of adding them either.

It seems I'll never learn that the faster I try to do something, the slower I am.

I started using AI to code again when returning to work. I am less impressed than before, it doesn't code worse 'per se', but it is really hard to keep it contained at a pace I want. Basically, word predictor is going to word predict.

My son is afraid of 'the boars' at night. There are no boars in my garden (that I know of) I think my snoring reminds him of boars 😅🥲

It's crazy to think how many 'divergent' 'standard' ways of working in a software team there are! (And how convinced everyone is there is only one)

🚨 New Episode Alert 🚨 I had the honor to host Thierry and Martin to discuss team practices for writing excellent software. I learned a lot from them and hope you will too! Listen here: open.spotify.com/episode/6GSW...

Got myself an upgrade!!

Heard more than once lately the classic: 'youngsters don't know how to work these days' From people in my generation (Y)... Just, remember when they said that about us? Both are equally false, but come on! It annoyed you then, don't repeat it!

🚨 New Episode Alert🚨 A couple days ago Kevin joined me for an enlightening discussion around PWAs Are they viable? What niche do they serve? All that and more: open.spotify.com/episode/3JpV...

In defense of companies adding a 'make longer with AI' button (aka slopify), most of them are adding a 'sumarize with AI' button to de-ai-fy. It's like sending a zipped message, but with more bytes, burning the planet in the process and getting an approximate result.

At any given point there is only one most important thing you should be doing. Sadly, that seldom coincides with the most urgent. A solution to that is to carve a space dedicated to the important rather than the urgent... blog.codemanship.dev/separating-t...

There are two types of #Rails codebases: One follows the 'rails way', uses minitest doesn't add other subfolders under /app, uses ERB. The other uses RSpec, has services and/or interactors, uses slim. Which one do you work on? Me: Second, wish it was first.

At any given point there is only one most important thing you should be doing. Sadly, that seldom coincides with the most urgent. A solution to that is to carve a space dedicated to the important rather than the urgent.

My code ain't (too) bad, but I believe I truly shine in domestic cooking situations. Today's 'fun' menu: Lunch: Katsudon Dinner: Rosejat Both were different, both went great today! (the alioli was a disaster though) (Attached, the rosejat)

Especially in smaller companies, the goal is not to write the most code, it is to write the right code. Most places work at maximizing the amount of code written. An advantage of Software Teaming is that it forces you to write less code.

Everyone is rightly asking for a successful project that was vibe coded. But where are even the dumb and whacky projects? Those are the ones that actually would fit the vibe coding use case!

Service Objects in Rails (or OO) are weird. The first one is free, easy. Each subsequent one locks you in and makes your codebase more complex and harder to change

Code so that the person who comes 5 years from now won't hate you.

This article from the great Kent Beck resonates a lot with me: substack.com/app-link/pos... The IDE does not help me not lose track of what is happening with the AI assistant. (When I tried a CLI it was worse). It's worth thinking of what you want when reviewing code.

Sales funnel: business term in which everyone works and the sales person funnels the commission.

By show of hands, who here is actually talking to the end user? It feels like it should be the most important and yet it is the most easily postponed...

This is a great talk!

Maybe we were better off with the duck than with the parrot.

If your results depend on your motivation, you have a problem.

Whenever I talk to people working in agile environments they seem happy and consider themselves much more productive. Yet, it feels like truly a minority of people work that way. Is it a case of survivors bias? What is going on?

If you are doing canonical TDD (tidyfirst.substack.com/p/canon-tdd), I have a question for you: Does the order in which you select the tests change your design? If yes, are you deliberate about it?

I think I have an I tuition of what I would like an AI code assistant to be (for me) And... It's not anything I have seen. I don't know if it'd be possible. But basically, way less eager, way more interactive. Basically way more Pairing and less Delegating.

We are recording an episode on Progressive Web Apps this Friday. Any topics you'd like me to bring to the guests?

Design Patterns are a shared vocabulary, if I say I implemented a chain of responsibility, the idea is that you all understand what I am saying, but that only works if we all have the same understanding.

A thing that annoys me about technical jargon is that it seems that the understanding is still fuzzy on most terms. Jargon is there to be precise and take shortcuts (e.g. openings in chess) but if it means different things to different people, it loses all meaning.

I started two projects vibe coding as I don't have much attention to spare. One, a simple crud "works". With some flaws but it works. The other (surprisingly the one I paid more attention to) I lost control of. I don't even know if it works anymore, it's a thing of its own.

A great way to start the day!

What agent/code tool is best at writing the least amount of code at a time?

Even as someone with coding experience, it's super easy to lose control of AI assisted code. I frankly pity those who drank the kool-aid and think they can "vibe code" something meaningful.

I get why companies complain about people applying with AI. But, to be fair, karma is a b*tch.

The amount of hubris and self delusion you need to start a company or publication is admirable. It's not only: 'the world needs this'. It's also: 'I can do it better than others'. Genuinely admirable

Two types of Software Developers: Those who think their job is writing code And Those who know it is not

Learning to code is great, it gives you a lot of immediate feedback that allows you to learn by yourself. But code lies to you. It works today, but until a year or two from now you might not know if it's actually good.

Taste: the art of writing code that does not suck tomorrow.

Out of curiosity, in your current job, who can answer this question: What should we do next? How easy is that person to access?