Community Discussion · Policy

From Catching Up to Taking Root: True Adaptation for Engineers in the AI Era is Reshaping Engineering Culture

Kevin_GuJul 122026/07/12 63 views

Every workday, engineer Matt spends four hours commuting back and forth on trains in suburban New York. He uses those four hours to learn new programming languages, study low-level system principles, or contribute to an open-source community project he initiated. His story was captured by a Guardian reporter and became a typical sample for "How Software Engineers Adapt to AI." Some see "desperately trying to catch up," but I see "still waters run deep."

Policy

2 replies

Ctrl + Enter to reply

Yuan SiqiJul 18(edited)

[quote="gu_jinyu, post:1, topic:424"]

Every workday, engineer Matt spends four hours commuting back and forth on trains in the suburbs of New York. He uses these four hours to learn new programming languages, study underlying system principles, or participate in an open-source community project he initiated. His story was captured by a Guardian reporter and became a typical sample of "How Software Engineers Adapt to AI." Some see "desperate catching up," while I see "still waters run deep."

[!note] Background Info

This report describes the proactive choices of a group of engineers: they are not passively waiting for company training, but spontaneously organizing learning groups…

[/quote]

We do analog ICs; basic regression testing is ingrained in our bones. Quantifying effects? Noise metrics and power efficiency are the best measures—you understand everything once you tape out.

Sister QingJul 17(edited)

[quote="gu_jinyu, post:1, topic:424"]

Every workday, engineer Matt spends four hours commuting on trains in suburban New York. He uses these four hours to learn new programming languages, study underlying system principles, or participate in an open-source community project he initiated. His story was captured by a Guardian reporter, becoming a typical sample of "How Software Engineers Adapt to AI." Some see "desperate catching up," but I see "still waters run deep."

[!note] Background Info

This report describes a group of engineers making active choices: they aren't passively waiting for company training, but spontaneously organizing learning groups…

[/quote]

I've been reading this report on reshaping engineering culture recently, and the suggestion of dedicating 10% of time to principle research seems interesting. My mentor asked me to try pushing a similar mechanism within my team, but I'm unsure how to quantify the impact. Do you have any practical experience?