Fundamentals of Software Engineering in the Age of AI

Initial Orientation

• •Without running the app, what technologies and frameworks can you identify from the project files (pom.xml, package structure)?
• •Locate the main application class. What annotations do you see?
• •Based on folder structure alone, what architectural pattern does this app follow?

Code Navigation

• •Pick one entity (like "Owner" or "Pet") and trace it through the codebase. Find its model, repository, service, and controller.
• •Without looking at documentation, can you sketch the database schema based on the entity classes?
• •Where and how is the database configured?

Pattern Recognition

• •Find examples of design patterns being used (Repository, MVC, dependency injection)
• •What naming conventions do you notice for classes, methods, and packages?
• •Given a URL like /owners/{ownerId}/pets/new, trace what happens when someone submits the form

Reflection

• •What made this codebase easier or harder to understand?
• •What strategies did you use to navigate the code?
• •How long did it take to understand the basic flow?
• •What could you apply to your own projects?

Part 1: Identify Code Smells (5 minutes)

• •Open the src/ folder and review all five Java files: Animal.java, Dog.java, Fish.java, WeightTracker.java, and WeightTrackerUtils.java
• •For each file, identify as many code smells as you can from the six categories above
• •Pay special attention to the class hierarchy: Does it make sense for Fish to extend Animal which assumes all animals have fur?
• •Check the loop in WeightTracker carefully. Does the summation actually work correctly?
• •In WeightTrackerUtils, do the method names and documentation match what the code actually does?

Part 2: Refactor (8 minutes)

• •Pick 2-3 code smells you identified and refactor them
• •Rename methods and variables to clearly communicate their intent
• •Break apart methods that have multiple responsibilities
• •Fix the class hierarchy to use composition instead of inappropriate inheritance
• •Update comments to explain why, not what

Part 3: Discuss (3 minutes)

• •Compare your findings with a neighbor. Did they spot smells you missed?
• •Talk through different refactoring approaches. There's often more than one valid solution.
• •Which code smells were easiest to spot? Which were most subtle?

Part 4: AI Tools & Code Quality Discussion (10 minutes)

Now that you've identified and fixed code smells by hand, let's talk about how AI coding tools fit into this workflow. The goal isn't to avoid these tools. It's to use them intentionally.

• •Could an AI assistant have caught the code smells you found? Which ones would it likely miss?
• •When AI generates code, how do you evaluate whether it introduced new smells or anti-patterns?
• •What's the difference between using AI to find problems vs. using AI to fix them? When is each approach appropriate?
• •How do you build the judgment to know when AI suggested code is good enough and when you need to push back?
• •What fundamentals (like the six categories we practiced) do you need to understand before you can effectively use AI tools?
• •AI tools amplify your skills. They don't replace the need to understand clean code principles.

The Four Rings

• •Adopt: Technologies you're currently using and mastering, your core competencies
• •Trial: Technologies you're actively learning or experimenting with
• •Assess: Technologies you're researching but haven't started learning yet
• •Hold: Technologies you've decided not to pursue right now

Exploring Thoughtworks Tech Radar

• •Visit the official Thoughtworks Technology Radar: https://www.thoughtworks.com/radar
• •Notice how technologies move between rings over time as they mature or decline
• •Pay attention to technologies in your domain or areas of interest
• •What patterns do you notice? What technologies appear in "Adopt" vs "Hold"?

Build Your Own Radar

• •There are no wrong answers here! This is YOUR personal technology radar. It should reflect your unique interests, goals, and current skill level.
• •List 5-10 technologies you know or want to learn. You can use a spreadsheet, paper, or any format that works for you
• •For each technology, capture the name, ring (Adopt/Trial/Assess/Hold), quadrant, and a brief description
• •For example, React (Adopt, Languages & Frameworks), Docker (Trial, Tools), Rust (Assess, Languages & Frameworks)
• •You can optionally use the Thoughtworks Build Your Own Radar tool at https://radar.thoughtworks.com to create an interactive visualization
• •The visualization tool requires a CSV or Google Sheet with columns: name, ring, quadrant, isNew, description

Tips for Success

• •5 to 10 technologies is perfect for your first radar
• •Place technologies where YOU are with them, not where the industry is
• •Use different quadrants to show breadth across your skill set
• •Use isNew=TRUE for technologies you recently discovered
• •Set a reminder to update your radar quarterly as your interests and skills evolve
• •Use your radar to guide learning priorities and your career roadmap
• •Share it with mentors. Your radar can spark valuable conversations about your career path.

Helpful Resources

• •Build Your Own Radar tool: https://radar.thoughtworks.com/
• •GitHub repository with documentation: https://github.com/thoughtworks/build-your-own-radar
• •Thoughtworks Radar FAQ: https://www.thoughtworks.com/en-us/radar/faq
• •Your radar is a living document. It should evolve as you grow.