Burnout in IT: how scanners find balance | Guide for developers

# Scanner, Not Diver: How to Stop Burning Out in IT and Create an Environment for Growth

After 15 years in programming, I discovered a pattern: every 1–1.5 years at a new job, burnout would set in. Only adopting the "Scanner" concept and consciously creating an environment for a wide range of interests helped me break the vicious cycle. Here's how it applies to your career.

Burnout Pattern: The Numbers Don't Lie

Analyzing my career, I identified a clear pattern. First job — 5 years (Java developer), second — 3 years (Salesforce developer), subsequent ones — 1–1.5 years each. I used to blame external factors: poor management, outdated tech stacks, mismatched teams. But the real cause ran deeper.

At the first job, I stayed for 5 years because the company kept offering new challenges: from servlets and JSP to Alfresco, GWT, and FileNet. The learning curve stayed steadily upward. At the second, a radical stack switch to Salesforce. The transition was smooth thanks to my Java foundation, and short projects (from a week to a couple) provided quick feedback and dopamine hits. But after a year or so, the stack became familiar, tasks predictable, and the learning curve flatlined. My battery drained.

The Exception: How DINS Created a Scanner-Friendly Environment

One company bucked the trend — DINS. I worked there happily, even though I wanted to leave at one point. The key was the team lead who encouraged tackling any problem without red tape. They gave me time for learning, prototyping, and implementing. I generated novelty myself instead of waiting for it from tasks. That was the scanner-friendly environment.

Turning Point: AI as a Creativity Catalyst

Last summer, my brother recommended Perplexity. In chats with Claude Sonnet, I saw a qualitative leap: task analysis, code generation, and idea brainstorming became way more efficient. In 4 months, I launched over 40 projects:

• Plugins for IntelliJ IDEA and Obsidian
• Tools for automating routine tasks
• Multi-user platforms
• An attempt to write an OS in Zig

The idea flow accelerated, my schedule shifted: 4 hours of sleep, jotting ideas right after waking. It was a peak productivity period without burnout.

Scanner Concept: Not a Flaw, But an Architecture

When projects piled up, I asked AI: "How to organize ideas and pick monetizable ones?" The response led me to Barbara Sher's book Refuse to Choose. She describes two types:

Divers — dive deep into one topic for life. Depth is their element.

Scanners — crave breadth. Their brains are wired for variety. Breadth isn't a defect; it's their architecture.

Sher identifies 9 scanner subtypes:

• Plate Spinner — juggles multiple projects at once.
• Serial Specialist — dives deep, then switches fields completely.
• Double Agent — lives two parallel passions.
• Trophy Hunter — masters a skill, then loses interest.
• Curious — gathers knowledge for its own sake.
• Encyclopedist — prioritizes breadth over depth.
• Bee — connects people and ideas.
• Sybil — fixed time slots for each passion.
• Projector — lives from project to project.

Recognizing myself in this, I understood the root of my burnout patterns and success at DINS.

How I Changed My Approach to Work

Armed with this insight, I stopped waiting for interesting tasks. Now, spotting routine, I propose solutions: build a prototype and demo it. I've already rolled out two automation projects at my current company. It recreates that DINS vibe, but now I manage it consciously.

Type Test: Technical Implementation

Instead of passive reading, I built a tool. Combining Sher's model with Patrick Lencioni's "6 Working Geniuses," I coded a test in Java 21 + Spring Boot 3.

Stack: Thymeleaf, Gradle, Docker. No SPA or database.

i18n via JSON-pivot: one JSON per language instead of properties files. Adding a language = new file.

{
  "language": "ru",
  "ui": {
    "welcomeTitle": "Who you: Scanner or Diver?",
    "statsLink": "📊 Statistics"
  },
  "sherQuestions": [
    {
      "id": "q1",
      "text": "When I start a new project...",
      "options": []
    }
  ]
}

Algorithm: Weighted Voting

Each answer adds points to multiple types. Highest score wins.

public SherResult calculate(List<Answer> answers) {
    Map<SherType, Integer> scores = new EnumMap<>(SherType.class);

    for (Answer answer : answers) {
        answer.weights().forEach((type, weight) ->
            scores.merge(type, weight, Integer::sum)
        );
    }

    return scores.entrySet().stream()
        .max(Map.Entry.comparingByValue())
        .map(e -> new SherResult(e.getKey(), e.getValue()))
        .orElseThrow();
}

Stats without a database: LongAdder for increments, persistence via JSON snapshots.

public record StatsSnapshot(
    long startedSher,
    long completedResult,
    Map<String, Long> sherTypeCounts,
    Map<String, Long> geniusCounts
) {
    public double completionRate() {
        if (startedSher == 0) return 0;
        return (completedResult * 100.0) / startedSher;
    }
}

Deployment for developers from RF: free hosting without a credit card — Hugging Face Spaces in sdk: docker mode. Requirements:

• YAML header in README.md:

---
title: Scanner Profile
emoji: 🔬
colorFrom: green
colorTo: blue
sdk: docker
app_port: 7860
pinned: false
---

• App listens on port 7860.

After git push, HF builds the image and deploys. Completely free.

Key Takeaways

• Burnout in IT often stems from a mismatch between personality type (scanner/diver) and work environment.
• Scanners need an environment where they can freely generate and implement ideas without bureaucracy.
• Consciously applying the scanner model lets you create growth environments in any company.
• Technical tools (like this Java test) aid self-diagnosis and career management.

— Editorial Team