Some conference tracks group talks by technology — same language, same framework, same layer of the stack. Others group talks by question. Engineers as Humans belongs to the second category: five talks that couldn’t be more different from each other — in format, tone, technical depth — brought together because they all answer, from opposite angles, the same uncomfortable question: what’s left of engineering as a craft once you strip away the code itself?
It’s not a rhetorical question for a closing panel. Put in front of five different perspectives, it produces insight that sticks with you longer than any single technical talk — precisely because it forces discussion, often disagreement, with the speaker or with colleagues over coffee right after. That’s exactly the kind of value you take home from a live conference, and that a recorded video, watched alone months later, can’t really replicate.
Here are five insights this track brings to the room.
Insight #1: The voice that wins a design review is a trained muscle, not a gift
The first insight comes from an unexpected place: public speaking. Not as a skill for people who want to be on stage, but as a technical competency that transfers directly to any high-stakes conversation — a design review where you need a risky architecture approved, a board you need to convince to fund a refactor, a skeptical team you need on your side. The message is blunt: people who communicate well on stage don’t have a gift. They’ve repeated a method enough times that it’s become invisible.
The question worth arguing about: how many technical disagreements do we actually lose at work not because the idea was wrong, but because the pitch was weak? It’s an uncomfortable question, because it shifts the blame from “I was right and nobody listened” to “I wasn’t clear enough to be heard” — and in the room, that’s exactly the kind of conversation worth having face to face, not in a Slack thread.
Insight #2: We’re blunt in pull requests and cowardly in standups
The second insight might be the sharpest in the whole track: the same engineers who ruthlessly critique naming, abstractions, and missing tests in a pull request go strangely quiet in every other setting — a standup that’s going off the rails, a design review where a critical requirement gets ignored, a retro where nobody says the uncomfortable thing out loud. People who request changes on GitHub without a second thought will soften, postpone, or offload the exact same conversation onto a manager when it has to happen in person.
The question worth arguing about: why does code give us permission to be direct that people don’t? It’s a question that stings — in the right way — because almost everyone in the room recognizes doing exactly this last week. And that’s exactly what makes a talk memorable: not because it teaches something new, but because it says out loud something everyone already knew and nobody was saying.
Insight #3: The most extreme AI predictions deserve a debate, not a shrug
The third insight arrives in a completely different format: an interactive talk where the audience itself grabs the mic to tear down or defend deliberately exaggerated claims about AI’s impact on the job market — SaaS is dead, software agencies will close within eighteen months, a senior dev is just a junior who’s memorized the APIs. None of these claims are meant to be true. They’re meant to be argued.
The question worth arguing about: most people form their opinion on AI’s impact by reading threads alone, never actually debating it out loud with someone who disagrees. A format that forces you to take a public position — and immediately hear the counter-argument from someone who sees it differently — produces sharper thinking than any article read solo on a commute.
Insight #4: Curiosity without an immediate payoff is still the fastest way to learn a new tool
The fourth insight starts as a personal, almost playful story: a 1982 Atari 2600 game that required two human players by design, because the hardware — 128 bytes of RAM, no frame buffer — left zero room for an AI opponent. Decades later, that game gets hand reverse-engineered, wired up via MCP to an AI model, and turned into the opponent the original hardware could never afford.
The question worth arguing about: how much of our strongest skill with new tools — MCP, agents, orchestration — actually comes from a work problem with a deadline, versus a personal project with zero delivery pressure? It’s worth asking in the room, ideally next to someone who learned a new tool the exact same way: by playing with it, not because they had to.
Insight #5: The technical interview is still evaluating the wrong person
The fifth insight is about a ritual nearly every senior engineer has sat through on both sides of the table: the technical interview. The claim is direct: AI has already changed how engineers work day to day, but most hiring processes still evaluate candidates as if AI didn’t exist — measuring the ability to write an algorithm from scratch instead of the judgment to recognize when AI-generated output is wrong, incomplete, or misleading.
The question worth arguing about: if the evaluation criteria are broken, how many recent hires — ours, not just other companies’ — rewarded the wrong person? It’s a question that hits a nerve for anyone who runs interviews, and a room full of peers is the best place to sit with that discomfort before going back to the office and actually changing the process.
Why these five talks share a track
It’s not a coincidence that these five talks — one on public speaking, one on directness in feedback, one on job-market predictions, one on a personal project involving AI and an Atari, one on technical interviews — sit in the same thematic bucket. None of them is about a language, a framework, or an architecture. They’re all about the same thing: what happens to the human side of engineering once writing code stops being the hardest part of the job.
The value of actually sitting in that room — not reading a summary of it afterward — comes down to this: every talk leaves you with an open question designed to keep the conversation going with whoever’s sitting next to you, over coffee, right after. It’s a kind of learning no recorded video, watched alone months later, can quite give back.
Want to experience these talks live — and turn what you learn into a certification?
These five talks are part of the program at Codemotion AI & Tech Conference in Milan. If code is only half your job — and you suspect the other half is worth training just as seriously — this track was built for you.
Buying a ticket also gets you 40% off Linux Foundation certifications: a concrete way to turn the insight you bring home into a credential the market actually recognizes.
See the full program, reserve your seat, and unlock the certification discount →
