Code and Collaboration: Lessons from Our Summership

Our goal: Bringing the Real Engineering World to Our Interns

This summer was not about teaching a checklist of testing techniques. It was
about letting interns explore what it actually means to build and maintain
software.

They started with the fundamentals manual testing, test cases, and
automation, and then went beyond them. They wrote code themselves,
experimented with AI-assisted development, designed automation solutions,
worked with pipelines and CI/CD, reviewed and merged code, and learned
how the different pieces of the engineering process connect.

We also wanted them to experience something that no tool or technology can
replace: collaboration. Their work did not stop at the boundaries of their own
team. They had to communicate with other teams, understand dependencies,
share knowledge, and see how their decisions could affect someone else’s
work.

And throughout the process, we kept coming back to one question: does the
code we build today remain healthy tomorrow? Together with CodeScene,
interns could monitor their code quality, identify areas that needed attention,
and see how their changes affected the health of the codebase.

They tried a lot. They learned a lot. And, most importantly, they experienced
that software engineering is about much more than making something work.

It is about building it well, and building it together.

Challenges we encountered

• Fast Code, Faster Reviews
  
  Interns were moving quickly, which meant multiple code changes landed for review throughout the day.

• When AI overthinks 
  
  AI sometimes turned simple tasks into over-engineered solutions. The code
  worked, but it wasn’t always the simplest or cleanest way to solve the
  problem.
  

• Learning what "Good" looks like
  
  We wanted interns to understand that good code is not about writing more, it is
  about writing code that is simple, clean, maintainable, and easy for others to
  build on.

• Beyond "It works"
  
  As the codebase grew, we needed to look beyond functionality and help
  interns understand the long-term health of their code.

This is where our collaboration with CodeScene became especially
valuable. It gave us another perspective on the code the interns were
producing and helped turn code quality from an abstract concept into
something they could actually see, measure, discuss, and improve.

Making Code Quality Visible

We did not want code quality to be something interns heard about only during
code reviews, we wanted them to see it, understand it, and use it to make
better decisions.

We used CodeScene to give interns a broader view of the codebase and help
them understand not just what they were changing, but how their changes
affected the bigger picture.

• Authors and Knowledge islands
  
  Understanding who works on different parts of the code helped us identify
  knowledge gaps and areas where knowledge sharing was needed.

• Hotspots

  We identified frequently changed areas of the codebase that deserved extra attention, testing, and refactoring.

• Code Health

  Interns could see the health of their code and understand how refactoring and better implementation choices could improve it.

The goal was not just to show interns a score. It was to teach them how to
read the codebase, understand its risks, and make better engineering
decisions

What were the takeaways

The collaboration created value on both sides

• A stronger quality mindset
  
  Interns experienced firsthand why code quality matters and how it
  affects the long-term health of a codebase.

• Skills for the AI era

  They gained practical experience in reviewing, refactoring, and
  maintaining code, skills that become even more important as AI makes
  generating code faster and easier.

• A Fresh Perspective on CodeScene

  As first-time users, interns provided valuable feedback on the user experience, helping highlight what felt intuitive and where the experience could be improved.

• Real world feedback

  Their experience also helped CodeScene better understand which parts of the platform are most valuable when introducing code quality practices into an automation focused engineering environment

For us, it was more than the Summership project. It was a chance to learn from each other and see how better engineering practices can be built
through collaboration.

Looking back, looking ahead

This summer was an incredible experience, and I am very glad I had the
opportunity to be part of it. The collaboration we built this year made a real
difference, and the results exceeded our expectations. We are already looking
forward to doing it again.

The final presentation was one of the highlights. Interns shared what they had
learned, what they explored, and the ideas they developed along the way.
Some of those ideas were things we simply hadn’t had the time to explore in
our day-to-day work and the Summership gave us the space to experiment
with them, challenge our usual ways of thinking, and even identify ideas that
could eventually make their way into our real projects.

In that sense, the Summership became more than a learning experience. It
became a small research lab, a place where fresh minds could question
assumptions, explore new ideas, and show us possibilities we might
otherwise have overlooked.

And perhaps that is one of the greatest values of the Summership: we teach,
but we also learn.

This year reminded us that collaboration can create value in unexpected
ways. We are proud of what the interns accomplished, grateful to everyone who
contributed, and excited to see where we can take the next Summership.