@kratzen@berg.mobilecourant.org
2026-10-31 18:37 UTC
continuing: "lifetime of experience, judgment calls, and understanding . You are also (hopefully) much less prone to hallucination and being mislead by bad or malicious inputs , and are accountable to yourself, your teammates, and to Proton in a way a model can never be. Together you can do far more, far faster than either can do alone.
It is also not the death of good engineering practices. Maintainability and velocity is better on well-architected codebases. Documentation and tests remain crucial. That said, we need to be open to best practices changing as costs and capabilities change. Testing is a good example of this. Old best practice says that too many tests (particularly end-to-end tests) are a bad tradeoff in a world where writing and maintaining tests are expensive. If writing and maintaining tests become cheap, the place where we draw that line willikely change as well.
The second reason we have not been able to take full advantage of the Al revolution is that we have been almost completely stuck at phase 1 - using LLMs to speed up tasks as part of existing workflows. But writing code is not the only part of the software development lifecycle, and what happens when you eliminate a bottleneck? Another takes it is place. Maybe it is the speed and capacity of the CI. Maybe it is design, approvals, specifications, and code reviews (yes, we need to and will get to a point where most human code review will end). Maybe the workflow does not change much but LLMs allow us to finally invest in automnation which was cost-prohibitive before. If we do not look at all of our processes holistically and ruthlessly eliminate bottlenecks, we will not achieve our full potential. Often eliminating these botlenecks will not only involve optimization of parts of our existing workflows but reworking and rethinking them altogether. This is phase 2, and we need to get there now.
The third reason is a collective action problem. Using LLMs effectively to write code is something an individual engineer can do for themselves. Rebuilding or optimizing the CI process for a whole team, business unit, or company is a much heavier lit, and it comes with opportunity costs and tradeoffs. Not impossible, and many people at Proton have done amazing things on their own, some of which have spread far and wide. But to retool the company at large requires amounts of both organization and resourcing that we simply have not invested in yet. Regarding the software development lifecycle discussion in the previous paragraph, in many cases we do not even know where the bottlenecks are because we have not invested in the tools necessary to find out. Some caution may have been warranted in the past -- it took some time to figure out how to best use these new tools and we wll continue to encourage experimentation. But it is past time to commit, as an organization, to the transformation that the moment requires.
So what does this mean for you, the engineer? Well, your agency and responsibilities have both expanded. Not only are you responsible for the work getting done, you also now own how it gets done, and therefore are responsible for continual optimization and maximal automation (and sharing those enhancements with your colleagues - success at Proton is a team sport). It is also your responsibility to flag and escalate needed improvements that you cannot execute on your own. Proton, for its part, will organize and resource the critical investments that are required to get through phase 2 and fully achieve the potential of the Al revolution."
(2/3)
Replies (1)
-
@kratzen@berg.mobilecourant.org 2026-10-31 18:39
continuing: "The bottomlineis thatweareinanewworld. "Programming" isdead. Engineeringisnot,noris expertise. Youroldjobis gone. Yournew jobasabuilder willletoudo more and have more impactthan youever have, ifyouseize the opportunity. AndProton willset.youtt dothat,efforts youwillhear more aboutin the coming daysand weeks. The eraof experimentation continues, butthe time toactis now. The futureishere-ltt's make itours." The documents are signed off with a "-Bart" (3/3)