
Meta software engineer Ali Hami posted on LinkedIn about his strong discomfort working with large volumes of code written by AI agents. The post sparked a lively discussion and garnered over 600 comments in two days.
Hami is used to always understanding exactly what the code he is responsible for does. However, the speed and scale of generation by AI agents are such that the previous approach has stopped working. Now the engineer has to decide how deeply to delve into each change before moving on. He described his state as akin to a black box and admitted that he has never felt so uncomfortable at work. Checking each line, he said, would take forever. As a result, developers work with systems whose workings they do not fully understand. Hami noted that such a practice contradicts the basic principles of engineering, but admitted that this is becoming the new norm in the industry.
The discussion quickly extended beyond LinkedIn. On Hacker News, the publication garnered over 500 comments in about 17 hours, and opinions were divided. Some participants shared similar frustrations. Some went further and admitted they were considering changing professions: a craft where the usual control over the result is lost no longer brings the same satisfaction. Others see the situation differently. According to their logic, the transformation of development with the help of AI is inevitable, which means new ways of checking and understanding code will be needed. Instead of line-by-line reading, tests, automated control, and other mechanisms that allow trusting the result without studying every detail manually will come to the forefront.
Hami has been working at Meta since 2022. Before that, he worked at Microsoft for about two years. This information is confirmed by his public profile. Information about the post and reactions to it was actively spreading on October 20, 2026. The original LinkedIn post is not indexed in full outside the platform without authorization, so details are known from quotes in discussions and secondary mentions. No new statements from Hami on this topic have appeared in recent days.
The community's reaction shows that the issue of trust in generated code concerns many developers. The answer to this will likely be new tools and verification practices that the industry will have to develop.
This material is prepared solely for informational purposes and does not constitute financial advice or a recommendation.




