Skip to content

An interactive course · 18 chapters · EN / PT

Software engineeringin the AI era

Learn the competencies to build better in the present — by playing with the ideas, not just reading them.

Scroll to bring order to the chaos

Code became abundant. Judgment became scarce. Your job is the system that turns intent into reliable outcomes.

The thesis

An engineer’s excellence comes to depend on their ability to turn intent into reliable systems, directing AI execution and continuously improving the environment in which people and agents work. Technical mastery is what makes it possible to expand that delegation — and to answer for the result.

The new unit of contribution

Not lines of code. A useful, understood, verified and sustainable change.

  1. 01Relevant problem
  2. 02Explicit intent
  3. 03Delegable execution
  4. 04Evidence of correctness
  5. 05Observed effect
  6. 06Reusable learning
Explore what breaks at each step →

The journey

Four parts. Eighteen interactive chapters.

Part 1

The shift

What the engineer’s job becomes when code production is delegable.

  1. 01The central shiftYour unit of contribution is no longer code. It is a useful, verified change in the real system.✓6min
  2. 02The evidenceCapability, productivity and outcome are three different questions. Learn to keep them apart.✓5min
  3. 03The mindsetSeven habits of mind for engineers who direct agents and answer for outcomes.✓7min
  4. 04Competency mapPreserve, deepen, learn, deprioritize: four decisions about where your learning time goes.✓5min

Part 2

The craft

The fundamentals to keep, the new skills to learn and what to let go.

  1. 05FundamentalsYou can delegate the syntax. You cannot delegate the mental model of what the code does.✓9min
  2. 06Working with agentsSpecify, provide context, equip with tools, decompose and keep long runs on track.✓10min
  3. 07Verification & evalsTrust is built from evidence with independent origins, not from a convincing explanation.✓8min
  4. 08Security & autonomyUseful autonomy needs an effective perimeter: control what can happen and how far it can reach.✓7min
  5. 09What to deprioritizeAdapting requires withdrawing investment. Rebalance your study week deliberately.✓7min
  6. 10SpecializationA common core for everyone, plus selective depth where your judgment is hardest.✓3min

Part 3

The practice

A full technical case, delivery flow, learning and a 90-day plan.

  1. 11Case studyRace conditions, idempotency keys and the transactional outbox — simulated step by step.✓10min
  2. 12Delivery flowA 10× faster implementation can make delivery only 1.56× faster. Find where time really goes.✓7min
  3. 13Learning with AIReceiving a solution and understanding it are different outcomes. Design for the one you need.✓6min
  4. 1490-day planFour phases, real deliverables and a criterion for advancing. Track your own progress.✓6min
  5. 15Career levelsRate yourself on ten dimensions and see your profile take shape.✓6min
  6. 16The excellent engineerOne sentence that summarizes the whole report.✓2min

How to trust what you read

Every claim carries its label.

The course is built on a targeted review of primary sources from 2025–2026. Throughout the chapters, content is marked by its nature so you always know how much weight it can bear.

Premise

Ideas from the manifesto that frame the problem.

Evidence

Research, documentation and published experiences — with their limits.

Applied synthesis

Recommendations derived from sources plus engineering reasoning.

Example

Explicitly illustrative scenarios and numbers — not observed results.

Read the report’s full methodology note

This report takes as its premise the manifesto “AI @ Proton, Engineering Manifesto”, provided in three images. The public version was located on Proton's website, published on November 1, 2026, and attributed to Bart Butler, the company's CTO. The text of the images is the starting source; the publication and the author's official page make it possible to verify its attribution. F01 F02

The question guiding the research is: what does an engineer need to understand, learn, preserve, and stop prioritizing in order to perform this new role with excellence? The transformation described in the manifesto is treated as a present working condition. The methodological qualifications in this report serve to guide its implementation, select investments, and measure results.

There are four types of content:

  • Premise: the ideas from the manifesto that frame the problem.
  • Evidence: results from research, documentation, and published experiences, with references.
  • Applied synthesis: recommendations formulated in this report based on those sources and on engineering reasoning.
  • Examples: scenarios, numbers, and working templates that are explicitly illustrative, with no claim to be observed results.

The research is a targeted review of primary sources, not an exhaustive systematic review. Priority was given to studies from 2025–2026, technical accounts by the authors themselves, official documentation, and durable engineering references. Observational surveys, experiments, methodological proposals, and vendor reports have different strengths and limits. Those limits appear alongside the relevant claims. The references at the end contain links, dates, and the nature of each source.

Reading paths:

  • To understand the professional shift, read sections 1 to 4.
  • To reorganize your technical development, read sections 5 to 10.
  • To turn the diagnosis into practice, read sections 11 to 16 and the appendices.
  • To go deeper into the research, use the annotated bibliography in section 17.

Reading paths

What do you want to get out of this?

Start with the shift.

Each chapter takes a few minutes and ends with a quick check. Your progress is saved in this browser only.

Start the journey →