Josh HudsonThere's a meme going around about the longer you work in tech and the more you want to quit it all and start a farm. Well I am a developer in tech and also have an allotment farm!!
MarcelDevibecoding 🔧
In my last post I defined vibecoded code as code nobody on your team has fully understood. But what happens when you take that code and make it yours?
I think we need a term for this: devibecoding.
💻 Devibecoding is the process of taking code you don't fully grasp — whether AI generated or not — and systematically working through it until you truly own it. Understanding it, restructuring it, making it maintainable.
🧠 This is not just code review. It's a mix of reverse engineering, refactoring and deep comprehension — without being able to ask the original author about their intent. Because there was no human author.
💬 Someone in the replies to my last post described exactly this: putting in the effort to understand and reformat AI output until it becomes their code. That's devibecoding in practice.
🚀 And here is my take: this will become its own discipline. With its own tools, its own best practices, maybe its own specialists. Think tools that don't just lint but explain. That visualize where your understanding gaps are. Possibly even AI helping you understand AI code — ironic but inevitable.
⚡ The more vibecode exists in the world, the bigger the need for people who can devibecode it.
What do you think — is this already part of your workflow? And what tooling would help you most? 🔍
#SoftwareDevelopment #AI #Vibecoding #Devibecoding #CodeQuality #DevLife #Refactoring
🤖 Everyone talks about vibecoding but most definitions focus on how the code was created. I think that misses the point.
My take: vibecoded code is code that nobody on your team has fully understood. It doesn't matter if an AI wrote it, a junior dev copied it from Stack Overflow, or a senior dev hacked it together at 2am. If nobody has truly reviewed and comprehended it — it's vibecode.
That distinction matters because it shifts the conversation from "did you use AI?" to "do you actually know what this does?" 🔍
This also means: code that an AI generated but you thoroughly reviewed and understood is NOT vibecode. The tool doesn't define the category — your level of understanding does.
Why does this matter? Because it changes the risk assessment entirely. Using AI to write code you then deeply review is just a productivity tool. Shipping code you don't fully grasp is a conscious risk decision — sometimes justified, sometimes not.
Do you agree with this definition? Or would you draw the line somewhere else?
Michael AndersenSenior developers love complexity. I know because I built systems so abstract they needed a manual. Felt brilliant at the time. Came back months later and couldn’t understand my own work. Complexity isn’t skill. Simplicity after mastery is.
MikeMilzz
Tysk GamesTurns out friends will immediately test how unhinged the chat can get 😅
So today became “add a profanity filter” day. It’s now catching the obvious stuff, which should make the game feel a lot less gross when people get silly.
Curious what you’d want from it: super strict, or mostly just blocking the worst words?
Sheldon@helmers where did you get the Señor Developer sticker?!? I have to have one of those!
I've freelanced my entire career as a developer and never had a title. I had to come up with one to help with some interviews a couple of years ago.
I deliberately went with "Sr. Developer" so I could correct people who assumed it meant Senior and tell them it was actually short for Señor.
Sheldon (@[email protected])
I just got promoted to Sr. Developer after 20 years. I know a lot of people hit the ground running and became Sr. Developer after 2 or 3 years, but I'm on a different timeline. Before this, I was... actually I had no title and I'm truthfully I'm still not Sr. anything. I've been a freelancer with no title my entire 20 years as a developer & I just now needed to come up with a title to participate in a hiring process. They couldn't start off an interview like this: "Hi, welcome to the interview. We'd like to introduce you to our... uh, Sheldon. We're not actually sure what he is, but everyone knows him." Titles are weird when you're a #freelance agent who exists outside of everyone else's hierarchies. You never really know where you stand. You never get a promotion. You don't get performance reviews. The only feedback you get is that they keep asking you back and the greatest compliment you can get is that they lose sight of the reason they hired you because they've been using you like duct tape. #devlife
kipriyanovichMy code doesn't work. My code now works. I have no idea why either happened. #DevLife #CodingMystery #fedi #growth
GhostlyI’ve noticed something interesting:
I’m often more productive coding on the couch or even in bed than at a desk.
It feels less formal and I get into flow faster.
Curious how others feel about this — do you prefer a classic desk setup, or do you have a more relaxed coding spot?
Spent today wrestling with the game's growing memory. Every village, item, and little change needs to stay connected, and missing one link can make something weird break somewhere else. Working on a cleaner way to keep all that info organized so the world can keep growing without turning fragile. It's a quiet kind of progress, but it matters.
