Fundamentals of Software Engineering okładka

Fundamentals of Software Engineering

Fundamentals of Software Engineering

Autor: Dan Vega Nate Schutta
Słuchaj bezpłatnie, bez subskrypcji

Das größte Angebot der Saison | 0,99 € pro Monat für die ersten 3 Monate + 15 € Audible-Guthaben

Danach 6,99 €/Monat. Bedingungen gelten. Monatlich kündbar.
O tym tytule
Programmer, coder, developer—there are any number of titles used to describe people who create software, but what does it mean to be a software engineer? Despite the way software is often taught, being a software engineer is about far more than simply producing syntactically correct programs.© 2026 Dan Vega, Nate Schutta
  • E13 - Are You Behind on AI? Probably Not
    Sep 28 2026
    In this episode of Fundamentals of Software Engineering, Nate and I dig into a feeling almost every developer has right now: that everyone else is further ahead on AI. New models, agents and protocols seem to arrive every week, and between the two of us we make a lot of content about this stuff and still feel behind. We start with what I call social media driven development, the stream of posts about coding agents that cleared three issues overnight or SaaS apps built while someone slept, and why treating those as a benchmark will always leave you feeling behind. From there we talk about why this industry has always moved fast, why you cannot learn everything, and how setting career goals lets you work backwards to what actually deserves your time. We also get honest about burnout, time boxing your exploration, and why sometimes the right call is to close the laptop and go touch grass.Then we get practical. We cover prioritizing what your company asks you to learn, leaning on a network of people you trust, and taking AI doomsday headlines with a grain of salt. Nate explains how the Thoughtworks Technology Radar gets made, from blips submitted by technologists working with real clients to the debates that decide what makes the cut, and why Agile practices like testing and frequent check ins with your product owner matter even more when code can be generated this fast. I share a talk we saw at Commit Your Code from the PGA Tour, whose engineers started their agent on simple issue triage and only handed it harder tickets as their confidence grew. We finish on blast radius, why a startup and a Fortune 500 enterprise should not read the same amount of code, and why it is worth giving yourself some grace.__________________________________________________Key Highlights📱 Social media driven development: Posts about agents fixing issues overnight or apps built in your sleep are written for engagement. Measure yourself against them and you will always feel behind, when most of us are somewhere in the middle.📚 You cannot learn everything: Set career goals and work backwards to what deserves your time. Technologies are like buses: another one comes along in ten or fifteen minutes, so it is fine to let some waves go by.🔋 Burnout is real, so time box exploration: Every evening spent on a new LLM is time you cannot spend on something else. Sometimes the right choice is friends, family, or a walk.🤝 Let your network be the filter: Trusted friends and a daily AI news brief tell you what is worth a closer look, so you are not drinking from the fire hose or falling down every rabbit hole.📡 How the Thoughtworks Technology Radar is made: It starts as blips from technologists using things on real client work, then gets debated down twice a year. There is no pay to play, which is why it stays so objective.🏌️ The PGA Tour's agent earned its trust: Their engineers started the agent on issue triage, then low priority tickets, and only moved up to critical ones as confidence grew. None of it happened overnight.💥 Stakes decide how much code you read: A startup with six months of runway can move fast, but a core pricing engine deserves scrutiny on every line. Tests, build results and observability are how you read the rest.__________________________________________________Resources & Next Steps🌐 fundamentalsofswe.com for the book, the podcast and the YouTube channel📡 Thoughtworks Technology Radar📕 If Anyone Builds It, Everyone Dies by Eliezer Yudkowsky and Nate Soares🎤 Commit Your Code conference, run by Danny Thompson🛠️ Tools mentioned: Claude Code, Copilot, OpenAI Codex, Perplexity and NotebookLM✈️ Catch Dan and Nate at Dev2Next, Porto Tech Hub and QCon San Francisco🎧 Subscribe to Fundamentals of Software Engineering on Apple Podcasts__________________________________________________Chapter Timestamps00:00 Are you behind on AI? Probably not02:42 The book turns one, and conferences coming up07:33 The question of the day: do you feel behind on AI08:25 Social media driven development10:37 You cannot learn everything, so set career goals13:19 Why every new tool floods your feed17:00 Burnout and time boxing your exploration20:09 Prioritize what your job asks of you first22:19 Lean on your network23:27 Taking AI doomsday claims with a grain of salt27:17 The two sides of AI for software engineers31:00 There are no dumb questions33:35 Learning what the career you want demands35:25 Every language you learn makes the next one easier36:55 A daily AI brief instead of the rabbit hole39:46 How the Thoughtworks Technology Radar is made43:15 Agile practices matter more, and nobody is an expert yet46:05 How the PGA Tour eased agents into its workflow51:03 Startups vs enterprises: why the stakes matter52:26 Reading code and earning trust in your agent56:44 Give yourself some grace58:13 Dad joke and wrap up
    Rozwiń Zwiń
    59 min
  • E12 - How Developers Can Start Speaking at Conferences
    Sep 16 2026
    In this episode of Fundamentals of Software Engineering, Nate and I dig into public speaking, recorded live from a conference floor between our own talks. We start where most people actually start, which is nowhere near a keynote stage. Nobody goes from never having spoken to opening a major conference, and pretending otherwise puts people off before they begin. We talk about the places that genuinely welcome a first talk: the lunch and learn at your own company, a local meetup, a book club with a few colleagues. Lower stakes, smaller rooms, shorter slots. I make the case that volunteering to speak on something is the best motivation there is for learning it properly, because you have to learn it once to know it and again to teach it.From there we get into the craft. We cover writing an abstract that survives a committee reading hundreds of them, why one talk should carry one idea, and what happens to your slides when you keep shrinking the font to fit more words in. We talk about live demos and why a recording is not cheating, tethering off your phone when the venue Wi-Fi dies, and building expansion joints into a deck so the same material can fill twenty minutes or four hours. Then the part nobody admits to: nerves. I still get them after twenty years. We finish on delivery, filler words, starting on time, ending on time, and why the room is almost always on your side.__________________________________________________Key Highlights🎤 Nobody starts at the keynote: Going from zero to keynoting KubeCon is vanishingly rare. The realistic first stops are a lunch and learn, a local meetup, or a book club with colleagues.📚 Volunteer to speak on what you want to learn: The best motivation for learning a topic is agreeing to teach it. You learn it once to know it, and again to explain it to a room.✍️ One idea, one talk: If you have two ideas, that is two talks. Abstracts fail when they try to be broad, and committees are reading hundreds of submissions for very few slots.🖥️ Slides are not a handout: A deck that works as a read-it-later document serves neither the room nor the reader. If the font keeps shrinking to fit the words, the words belong somewhere else.📹 Record the demo, and bring your own Wi-Fi: Recorded demos are not cheating, especially for anything slow. Tethering off your phone saves the talk when conference Wi-Fi fails, and it is worth testing beforehand.⏱️ Build expansion joints into the deck: Know what you can skip and what you can stretch, so the same talk fits a twenty minute slot or a four hour workshop. Start on time, end on time.😬 The nerves do not go away, and the room is on your side: After twenty years the nerves are still there. Almost nobody in that room wishes they were giving your talk instead: they came to learn something.__________________________________________________Resources & Next Steps🗣️ Start with a lunch and learn, a local meetup, or a book club at work🎥 Record yourself on a video call and watch it back to hear your own filler words📶 Tether off your phone as a backup for venue Wi-Fi, and test it before the talk🎧 Subscribe to Fundamentals of Software Engineering on Apple Podcasts__________________________________________________Chapter Timestamps00:00 Recording live from the conference floor01:30 Why a mixed conference beats one full of your own crowd04:30 Nobody goes from zero to keynoting06:00 Volunteer to speak on what you want to learn07:30 Lunch and learns, meetups, and book clubs as a first step09:00 Handling questions, including the ones you cannot answer10:30 Finding your own presenting style12:00 Telling the audience what they are getting into13:30 Submitting on a topic you have not learned yet15:00 Writing an abstract around one hook16:30 One idea is one talk18:00 What committees see: hundreds of submissions, few slots19:30 When the font keeps shrinking, the words are in the wrong place21:00 Slides that try to be a handout serve nobody22:30 The night before, with no venue Wi-Fi24:00 Recording demos, especially the slow ones25:30 Tethering off your phone as a backup plan27:00 Expansion joints: the same talk at any length30:00 Nerves, after twenty years of doing this31:30 The room is on your side33:00 Knowing your first sixty seconds by heart36:00 Watching yourself back to hear your own pace37:30 Filler words and the power of a pause40:30 Arrive early and check the room42:00 Start on time, end on time, the room is not yours45:00 Practising a nine minute keynote to the second46:30 Evergreen material and giving a talk more than once49:30 Your first attempts will be bad, and that is the job52:30 You already know something most people do not
    Rozwiń Zwiń
    54 min
  • E11 - What Is Software Architecture
    Aug 22 2026
    In this episode of Fundamentals of Software Engineering, Nate and I dig into the question the whole show is named after and the one our book only had a single chapter for: what software architecture actually is. We start where Neal Ford and Mark Richards start, with architecture as the things you cannot Google, and we work out why that definition holds up. By the time a decision reaches an architect, the easy answers are gone. Nobody escalates a variable name. What gets escalated is whether this should be a modular monolith, a set of microservices, or something event driven, and none of those have an answer that survives being lifted out of your context.From there we get into the part that makes architecture uncomfortable: it is trade-offs all the way down. We talk about quality attributes, the ilities that routinely conflict with each other, and why a manager asking for all of them at once is asking for something that does not exist. We cover architectural malpractice, the habit of picking a pattern because it is fashionable rather than because the problem demands it, and what happens when a whole platform gets rewritten around one team's favourite language. We also talk about legacy systems and why reimagining beats dragging, about evolutionary architecture and fitness functions, about the difference between design and architecture, and we close on what we would tell an engineer who wants to grow into the role.__________________________________________________Key Highlights🔎 Architecture is the things you can't Google: Neal Ford and Mark Richards coined it and it holds. The answer always depends on your constraints and the forces you are actually up against.🏛️ No easy answers reach the architect: If a question had an obvious answer, it would have been solved further down. What lands on your desk is what is left.⚖️ The ilities conflict with each other: Scalability, maintainability, simplicity and the rest pull in different directions. Prioritising them is the job, not a failure to deliver all of them.🚨 Architectural malpractice: Reaching for microservices because they are in fashion, when the team shape and the actual demand say otherwise, is malpractice rather than ambition.🐍 Don't replatform a whole team for one capability: If your people are strong on the JVM, moving the organisation to Python to reach one library is rarely the trade you think it is.🔄 Reimagine legacy, do not drag it: Carrying every old defect and unfixed feature into the next system is a choice, and usually the wrong one.🌱 How to grow into the role: Talk to the architects around you about how they got there, what they like, and what they do not. Ask what the path looks like before you try to walk it.__________________________________________________Resources & Next Steps📘 Fundamentals of Software Engineering, the book and the podcast📚 Building Evolutionary Architectures by Neal Ford, Rebecca Parsons and Patrick Kua (second edition out now)📖 Software architecture writing by Neal Ford and Mark Richards🖥️ Fundamentals of Software Engineering on YouTube for the video version🎤 Catch Dan and Nate at KCDC, Devnexus, Dev2Next and QCon San Francisco🎧 Subscribe to Fundamentals of Software Engineering on Apple Podcasts__________________________________________________YouTube Chapter Timestamps00:00 Cold open: reading Carnegie is as useful as another framework03:19 Conference season: what is coming up06:53 Dev2Next and Venkat's conferences07:36 QCon San Francisco and some good news09:31 Today's topic, and where to find the book10:28 Why one chapter on architecture was never going to be enough11:36 Three shelves of architecture books and what they have in common13:31 By the time the question reaches you, the easy answers are gone14:30 Architecture is the things you can't Google16:43 Knowing which questions to ask, and how to get answers18:36 Does this problem actually require Kafka20:34 Structure, teams and what architecture you can realistically run23:21 Architectural malpractice, defined24:43 Designing for scale you do not have yet27:23 AI on the JVM, and not replatforming a team to chase a library28:48 New leadership, rewrites, and the defects you carry across31:34 Who should be an architect these days34:45 Where design ends and architecture begins42:29 Evolutionary architecture and fitness functions46:23 The ilities, quality attributes and real trade-offs55:46 Advice for engineers who want to grow into architecture
    Rozwiń Zwiń
    1 godz. i 1 min
adbl_web_anon_alc_button_suppression_t1
Brak recenzji