DEMISSÃO em MASSA: PROGRAMAÇÃO AINDA É A PROFISSÃO DO FUTURO em 2026? [com FABIO AKITA]

Thesis

Programming remains a viable profession in 2026, but the role has changed: surface-level skills (bootcamps, memorized interview tricks) won’t survive. AI (GPT and similar) amplifies capabilities but does not replace the need for real knowledge, practice and experience.

In short: AI speeds up those who already know how to build and think; it does not make novices into experts.

Technology and product concepts

• AI / code generation: AI is a powerful tool — like a hammer or typewriter — that accelerates skilled practitioners but can hide gaps in fundamentals for inexperienced teams.
• GPT / generative models: the arrival of GPT accelerated market changes and exposed weaknesses in teams that relied on surface-level knowledge.
• Cloud and large vendors (e.g., Google, Gemini): big companies can stagnate after layoffs if they don’t bring in fresh talent; internal culture and new blood are necessary to adopt innovation.
• Tools vs fundamentals: better hardware or premium tools (MacBook Pro, iPad, pro subscriptions) don’t substitute for deliberate practice and domain knowledge.
• Security and production risks: hobbyist or inexperienced developers shipping products may introduce critical flaws (unsecured databases, poor testing) that cause data leaks and real harm.

Practical guidance, tutorials and how-to lessons

1. Learn by doing and failing Progress through stages — student → trainee → junior → senior — by making mistakes and learning from them; there is no substitute or formal “senior certificate.”

2. Avoid rote memorization Interview cramming is not the same as being able to design, test, and maintain systems in production.

3. Use AI correctly Learn to ask the right questions, verify outputs, and rely on AI to accelerate skilled work rather than replace domain knowledge.

4. Prioritize testing and QA Build adequate tests and security practices before shipping; inexperienced builds often fail under real-world conditions.

5. Mentoring and knowledge transfer Seniors must mentor juniors to create sustainable teams and avoid single-person knowledge silos. Mentoring helps choose the best subset of solutions under time pressure.

6. Don’t conflate tools with expertise Just as artists need fundamentals (color theory, composition, typography, lighting), programmers need architecture, debugging, and systems thinking beyond generated outputs.

7. Hiring strategy Hiring many low-skilled people during a boom creates long-term liabilities. Balance experienced hires with fresh talent to maintain innovation.

8. If you’re a hobbyist Be honest about scope — hobby projects are fine for learning, but don’t release critical systems you can’t support.

Warnings and industry analysis

• The 2022 hiring bubble produced many underqualified hires; subsequent layoffs and GPT adoption exposed the gap between marketing (quick-bootcamp success stories) and real skill.
• Companies that retained only pre-2022 staff and didn’t bring in new talent risk stagnation.
• Over-reliance on a single senior without mentorship is a liability; plan for succession and training.
• AI will change workflows and speed, but underlying competence remains the deciding factor for who thrives.

References and examples mentioned

• “Sami Arts” — example illustrating limits of claiming authorship over AI-generated work when manual adjustment or iteration isn’t possible.
• Anecdote about Google / Gemini and internal stagnation after layoffs.
• A Twitter anecdote referencing “Steve Yag” (or “Steve Y.”) commenting on internal company issues (name uncertain).

Main speakers and sources

• Fabio Akita (primary speaker / guest; the video title indicates his participation)
• Channel host / Flow channel (host refers to “I created this channel” and promotes membership)
• Referenced technologies and companies: GPT / generative AI, Google (Gemini)
• Anecdotal references: “Steve Yag” and “Sami Arts”