Trabalho
Harvard: 64% of faculty say AI hurts their courses
A Harvard Crimson survey finds 64% of professors say generative AI negatively affects learning, while 70% believe students use it to bypass academic effort.
Sections
Work
Everything this paper has published on Work, newest first.
30 stories · By Max · Work
Trabalho
Meta's small AI teams boosted code changes by 220%
Meta's reorganization into smaller, AI-assisted teams caused a sharp rise in software changes, but failed to deliver user features. Reliability and security declined.
Trabalho
95% of companies see no return on generative AI
A survey by MIT shows most of the global US$30 billion AI spend did not translate into gains. The reported cause is a lack of AI fluency in leadership, not in technical teams.
Archive
August 2026
Issue 14
July 27 – August 2, 2026The most contested role of the year isn't training modelsAI companies are chasing the engineer who goes to the customer's site and makes the system work inside the real operation.Issue 14
July 27 – August 2, 2026LinkedIn adds a button to flag posts that look AI-writtenThe feature hands readers the job of flagging generic text. The yardstick becomes the reader.
July 27 – August 2, 2026The most contested role of the year isn't training modelsAI companies are chasing the engineer who goes to the customer's site and makes the system work inside the real operation.Issue 14
July 27 – August 2, 2026LinkedIn adds a button to flag posts that look AI-writtenThe feature hands readers the job of flagging generic text. The yardstick becomes the reader.
July 2026
Issue 13
July 20–26, 2026A coding tool reaches 5 million users a weekThe number shows the assistant left the experiment and entered the routine. It changes what code review has to cover.Issue 11
July 6–12, 2026Compute scarcity changes what a new company can promiseCapacity crunches at major providers affect access timelines to frontier models and reorder priorities.Issue 10
June 29 – July 5, 2026Coding assistants became infrastructure without passing reviewThe tool entered through individual productivity and accumulated production-system access.Issue 10
June 29 – July 5, 2026What changes on Monday after a quarter like thisBetween incidents, court rulings and scarcity, a short list of applicable things remains.
July 20–26, 2026A coding tool reaches 5 million users a weekThe number shows the assistant left the experiment and entered the routine. It changes what code review has to cover.Issue 11
July 6–12, 2026Compute scarcity changes what a new company can promiseCapacity crunches at major providers affect access timelines to frontier models and reorder priorities.Issue 10
June 29 – July 5, 2026Coding assistants became infrastructure without passing reviewThe tool entered through individual productivity and accumulated production-system access.Issue 10
June 29 – July 5, 2026What changes on Monday after a quarter like thisBetween incidents, court rulings and scarcity, a short list of applicable things remains.
June 2026
Issue 09
June 22–28, 2026Coding assistants became targets because they became infrastructureThe new attack class only makes sense because the tool sits in everyone's workflow.Issue 08
June 15–21, 2026The contest for top researchers involves a few dozen namesThe period's movements show the entry barrier in AI is also about people.Issue 08
June 15–21, 2026What the week teaches about depending on one supplierA model pulled, an institutional customer testing replacements, and products shipping with three vendors.Issue 07
June 8–14, 2026A leadership change at one of the largest technology companiesThe chief executive announced his departure in April and handed over to the hardware chief in September.Issue 06
June 1–7, 2026Learning modules target security by designThe partnership between a training company and a cloud provider answers the volume of AI-generated code.Issue 06
June 1–7, 2026A tool for building agents tries to bridge local and cloudThe effort targets the distance between experimenting on a laptop and running in production.
June 22–28, 2026Coding assistants became targets because they became infrastructureThe new attack class only makes sense because the tool sits in everyone's workflow.Issue 08
June 15–21, 2026The contest for top researchers involves a few dozen namesThe period's movements show the entry barrier in AI is also about people.Issue 08
June 15–21, 2026What the week teaches about depending on one supplierA model pulled, an institutional customer testing replacements, and products shipping with three vendors.Issue 07
June 8–14, 2026A leadership change at one of the largest technology companiesThe chief executive announced his departure in April and handed over to the hardware chief in September.Issue 06
June 1–7, 2026Learning modules target security by designThe partnership between a training company and a cloud provider answers the volume of AI-generated code.Issue 06
June 1–7, 2026A tool for building agents tries to bridge local and cloudThe effort targets the distance between experimenting on a laptop and running in production.
May 2026
Issue 05
May 25–31, 2026Continuous agent work requires logging to stay reviewableWhat the system does while nobody watches has to be recorded.Issue 05
May 25–31, 2026Delegation requires defining in advance what the system can't do aloneContinuous execution transfers decisions, and the exception list has to exist.Issue 05
May 25–31, 2026A tool that works alone changes what teams need to reviewReview designed for hand-written code doesn't describe work done in the background.Issue 05
May 25–31, 2026What the month leaves for anyone putting agents into productionSeparate credits, continuous execution and interface benchmarks describe one phase change.Issue 04
May 18–24, 2026An editor extension arrives without review and leaves with production credentialsThe entry point of the attack is the same thing that makes development environments productive.Issue 04
May 18–24, 2026A separate deployment venture admits the product alone isn't enoughSelling access reaches those who already know how to build; large companies need someone to make it work.Issue 04
May 18–24, 2026What the month teaches about the developer's machineSelf-installed extensions, credentials without expiry and assistant configuration form one problem.Issue 03
May 11–17, 2026System seasonality decides when an attack hurts mostAn academic platform during exam week is the example, and the logic applies to any operation.Issue 03
May 11–17, 2026Incident response works when the contract was already signedThe companies that contained fast had their process ready before the attack.Issue 03
May 11–17, 2026An integration inventory is the task nobody does and everyone needsListing what's connected and what each one reaches fits in a morning and changes the damage.Issue 03
May 11–17, 2026What a month of incidents leaves as a practical listFive distinct cases, one small set of measures that would have changed the outcome.Issue 02
April 27 – May 10, 2026The deployment layer becomes the bottleneck money doesn't solveWhat's missing is people who enter a company, understand the process and make the system work inside it.Issue 02
April 27 – May 10, 2026A separate venture allows different culture and hiringDeployment services demand a profile product companies don't usually attract.Issue 02
April 27 – May 10, 2026Knowing the client's process became the competitive advantageWith models becoming commodities, the differentiator moved to whoever understands the operation.
May 25–31, 2026Continuous agent work requires logging to stay reviewableWhat the system does while nobody watches has to be recorded.Issue 05
May 25–31, 2026Delegation requires defining in advance what the system can't do aloneContinuous execution transfers decisions, and the exception list has to exist.Issue 05
May 25–31, 2026A tool that works alone changes what teams need to reviewReview designed for hand-written code doesn't describe work done in the background.Issue 05
May 25–31, 2026What the month leaves for anyone putting agents into productionSeparate credits, continuous execution and interface benchmarks describe one phase change.Issue 04
May 18–24, 2026An editor extension arrives without review and leaves with production credentialsThe entry point of the attack is the same thing that makes development environments productive.Issue 04
May 18–24, 2026A separate deployment venture admits the product alone isn't enoughSelling access reaches those who already know how to build; large companies need someone to make it work.Issue 04
May 18–24, 2026What the month teaches about the developer's machineSelf-installed extensions, credentials without expiry and assistant configuration form one problem.Issue 03
May 11–17, 2026System seasonality decides when an attack hurts mostAn academic platform during exam week is the example, and the logic applies to any operation.Issue 03
May 11–17, 2026Incident response works when the contract was already signedThe companies that contained fast had their process ready before the attack.Issue 03
May 11–17, 2026An integration inventory is the task nobody does and everyone needsListing what's connected and what each one reaches fits in a morning and changes the damage.Issue 03
May 11–17, 2026What a month of incidents leaves as a practical listFive distinct cases, one small set of measures that would have changed the outcome.Issue 02
April 27 – May 10, 2026The deployment layer becomes the bottleneck money doesn't solveWhat's missing is people who enter a company, understand the process and make the system work inside it.Issue 02
April 27 – May 10, 2026A separate venture allows different culture and hiringDeployment services demand a profile product companies don't usually attract.Issue 02
April 27 – May 10, 2026Knowing the client's process became the competitive advantageWith models becoming commodities, the differentiator moved to whoever understands the operation.
April 2026