← Latest papers
💻 computer science

Corporate Training in Brazilian Software Engineering: A Qualitative Study of Useful Learning Experiences

This qualitative study of 195 Brazilian software engineering professionals reveals that perceived training usefulness is primarily driven by continuous technical updating and practical application, while also valuing formal education, social learning, and soft skills as complementary dimensions that organizations should integrate into cohesive learning ecosystems.

Original authors: Rodrigo Siqueira, Antonio Oliveira, Breno Alves de Andrade, Lidiane C S Gomes, Danilo Monteiro Ribeiro

Published 2026-04-08
📖 5 min read🧠 Deep dive

Original authors: Rodrigo Siqueira, Antonio Oliveira, Breno Alves de Andrade, Lidiane C S Gomes, Danilo Monteiro Ribeiro

Original paper dedicated to the public domain under CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a chef working in a busy, high-end kitchen. Every day, new ingredients arrive, new cooking techniques are invented, and customers want dishes they've never seen before. To keep up, you need to learn constantly.

This paper is like a group interview with 195 software engineers (the "chefs" of the tech world) in Brazil. The researchers asked them a simple question: "What was the most useful thing you ever learned for your job, and why?"

Instead of just counting how many people liked a specific type of class, the researchers listened to their stories to understand what actually makes learning stick. Here is what they found, explained with some kitchen metaphors.

The Big Picture: It's Not Just One Thing

The researchers expected to find that engineers just wanted to learn the newest "spices" (programming languages). But they discovered that useful learning is more like a well-balanced meal. It needs a few different ingredients to be satisfying.

They identified five main "flavors" of learning that professionals found valuable:

1. The "New Spice" Rack (Continuous Technical Updating)

Frequency: The most popular answer.
The Metaphor: This is like a chef learning about a new, trendy ingredient that just hit the market.
What it means: Software changes incredibly fast. Engineers need constant updates on new tools, languages (like Java or AI), and certifications. They don't just want to know about the new spice; they want to know how to use it right now to solve a problem they are facing today.

  • Key Takeaway: If you teach them something they can't use immediately, they feel it's a waste of time.

2. The "Tasting Kitchen" (Practical and Applied Learning)

Frequency: The second most popular.
The Metaphor: Reading a cookbook is nice, but actually chopping the vegetables and tasting the sauce is where the real learning happens.
What it means: Engineers love "hands-on" learning. They want to build things, break things, and fix them. They value training that lets them practice immediately, rather than just listening to a lecture.

  • The Connection: The study found that "New Spices" (T1) and "Tasting Kitchen" (T2) almost always go together. You can't just learn the new spice; you have to cook with it right away.

3. The "Culinary School" Degree (Formal Academic Education)

Frequency: Surprisingly high.
The Metaphor: This is the 4-year degree you get from a fancy culinary school.
What it means: Even though many people complain that universities don't teach "real" job skills, these engineers still value their degrees. They see it as the foundation. It taught them the basic rules of chemistry (algorithms) and how to think like a chef. It didn't teach them the specific new spice, but it gave them the brainpower to figure out how to use it when they needed to.

  • The Insight: They don't see school and work as enemies; they see school as the sturdy table that holds up the fancy new gadgets.

4. The "Food Network" & "Chef's Table" (Social Learning)

Frequency: Very important.
The Metaphor: Watching a famous chef on TV, chatting with other chefs at a food festival, or having a mentor show you a trick.
What it means: Engineers learn a lot by watching others. They value conferences, online communities, and mentors. Seeing how a senior engineer solves a problem is like watching a master chef plate a dish—it teaches you the "why" and the "how" that a manual can't explain.

5. The "Restaurant Manager" Skills (Leadership & Soft Skills)

Frequency: Important for those moving up.
The Metaphor: Knowing how to cook is great, but knowing how to manage a team, handle a angry customer, or calm down a stressed sous-chef is what makes you a Head Chef.
What it means: As engineers get older, they realize that being good at code isn't enough. They need to learn how to talk, lead, and manage emotions. This is the "soft" side of the job that keeps the kitchen running smoothly.

The "Secret Sauce" (What Makes It All Work?)

The researchers found something really interesting: None of these work well in isolation.

  • If you only give them the "New Spice" without letting them cook with it, they get bored.
  • If you only let them cook without teaching them the new spice, they get stuck using old methods.
  • If you only teach them the "Culinary School" theory without showing them the kitchen, they feel disconnected.

The Best Training Ecosystem:
The paper suggests that companies shouldn't just throw isolated training events at employees. Instead, they should build a Learning Garden.

  • Plant the seeds of Theory (University).
  • Water them with New Tools (Technical Updates).
  • Let the plants grow by Cooking (Practical Application).
  • Have the Gardeners chat (Social Learning).
  • Teach the Head Gardener how to lead (Soft Skills).

The One Grumpy Chef (The Skeptic)

A tiny group of engineers (only 5 out of 195) said, "I don't trust company training at all. I learn everything myself."
This is like a chef who refuses to listen to the restaurant owner and only learns by reading books at home. While they are a small group, their voice warns companies: If you don't make your training useful and relevant, people will just ignore you and learn on their own.

The Bottom Line

For a company to train its software engineers effectively, it needs to stop treating learning like a single event (like a one-day seminar). Instead, it needs to create a continuous environment where:

  1. Learning is practical: You learn it, then you use it immediately.
  2. Learning is social: You learn from your peers.
  3. Learning is deep: You have a strong foundation of theory to support the new tricks.

In short: Don't just teach them the recipe; let them cook the meal, taste it, and talk to the other chefs about it.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →