AI Paradox
Published on AugĀ 18, 2024, filed under development, management (feed). (Share this on Mastodon orĀ Bluesky?)
Iām currently testing a lot of AI tooling, for everything related to the SDLC. While Iām concerned about AI in many areasāespecially around sustainability, AIās general impact on the world, and the specific impact on our fieldā, the experience has been eye-opening. AI is going to change how we do our work (I say āgoing to,ā because I believe weāre just at the start of that hockey stick).
Iām going to talk more about these tests and my observationsāone small experiment, ObsoHTML, you may have already seenā, so hereās something paradoxical that Iāve observed over the last few months:
Yes, AI helps me with my work ā¦but now I have even more of it.
(Is this the same for you? Iāve mostly stopped enabling comments, but Iām keen to learn more, perhaps on Mastodon!)
While you might think that AI reduces our workload (well, I did think so), it actually has boosted my own productivity so much that it has lead to a ton of unexpected extra work.
ObsoHTML is a great example: While it appears innocuous, once you finish the first version of a project like this, you clearly end up with more work! (Clearly, because in hindsight it makes sense. Mmh.) Now you can write the documentation, put it up on npm, announce the project, run more tests, and take care of the first maintenance tasks.
Clearly, if youāre productive, your outcomes arenāt just something that sits in the closet and needs no further attention.
While I keep saying āclearlyāāas clear as it wasnāt to meā, thatās still somewhat paradoxical, isnāt?
From the effects I observe around AI, the productivity gains donāt translate into more time, but into less.
I do worry that if weāre not aware of this and donāt manage this, AI may supercharge work stress, and the rate at which we burn out. We will just have more things to show for it once we do.
Thatās it. On the positive side, while I was worried AI might undermine my learning process, Iāve actually been learning a great deal using it. Howeverāthereās a catchā, these gains seem to be on the side of breadth (learning about more things), than on the side of depth (learning more about one thing). So thereās more here, too, and you can keep trusting me more on, say, what I write about HTML, than how my tests look like.
About Me
Iām Jens (long: Jens Oliver Meiert), and Iām a web developer, manager, and author. Iāve been working as a technical lead and engineering manager for companies youāve never heard of and companies you use every day, Iām an occasional contributor to web standards (like HTML, CSS, WCAG), and I write and review books for OāReilly and Frontend Dogma.
I love trying things, not only in web development and engineering management, but also in other areas like philosophy. Here on meiert.com I share some of my experiences and views. (I value you being critical, interpreting charitably, and giving feedback.)