if your team is too busy doing their 'normal job' to…
- article
- Saved
Written by AI
- TLDR
- Geoffrey Huntley argues that software teams must make AI experimentation part of normal work or fall behind the changing employment market.
- Best for
- Software leaders making AI adoption part of team practice
- The tip
- Give engineers protected time to experiment with AI during normal work.
- What you need
- Access to approved AI tools
- Time for hands-on experimentation
- Start here
- Make AI use part of the job, not after-hours work.
- Create room for teams to experiment with real tasks.
- Filed note
- Geoffrey Huntley argues that teams need protected time to experiment with AI because treating adoption as extra work leaves people and companies behind.
articleThe source
- Highlights
Usage of AI in the profession of software engineeering is no longer optional.
AI use is now a baseline professional expectation in Huntley’s argument.
Our profession is at a crossroads, and this is the last time I'll say it.
The piece treats adoption as an immediate career decision.
- Excerpt
When Ralph was published last year, I sat on it. People who have been reading this blog for a while know this. I first came across the idea of loop engineering in early January last year, sat on it for four months, and then started writing a lot, begging people to pay attention.
From ghuntley.com