Site icon Accidentally in Code

How I’ve Been Using AI

Cécile Evans' performance 'Sprung a Leak', seen in Haus der Kunst in Munich, Germany.

By Ralf Steinberger from Milan, Berlin + Munich, Italy + Germany – 21st century robots. Seen from the future, they will just look cute., CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=110354735

I feel like the whole AI conversation is dominated by two extremes. Those who believe in AGI, and AI skeptics. I’m trying to approach it as a tool that may or may not be useful. Here are some things I’ve found so far.

Useful as an editing partner. For things where I have a clear point of view, I produce a first draft and then use AI to refine and clarify. It will just go on endlessly though, so I have been telling it “I have limited time to spend on this, please stop once the feedback is chasing diminishing returns”. I think this works for me because I am quick to write and slow to edit.

➡️ For similar reasons, I’m enthused about AI feedback on PRs.

Helpful for generating feedback. If I’m reviewing something, I can use a similar process to refine my feedback. So I will put in the doc, my initial thoughts, and ask it what else – again being judicious about what I include. Or the doc, the additional clarification I wrote, and then use the combination of those to generate a feedback. It means that I can read something once and query it, rather than reading multiple times to check my thoughts – the longer what it is I’m reviewing, the more useful that is.

➡️ Like all women in tech, I’m continually walking the tightrope between being a b*tch and being a pushover, so I’m trying to offload any overthinking of “tone” to AI. My current workflow here is to tell it: “You are a busy engineering leader, who wants {team|person|whatever} to get their shit together”, and then “Now soften it a bit so people don’t think you’re mean”.

Mixed for structuring things. I’ve also been trying to use AI to create structures or plans, typically for things I don’t know much about (if I know about it, the structure is normally very clear to me). Here, I’ve had mixed results.

Both of these examples were places where I have some amount of expertise, but a relatively narrow point of view, deeply anchored in my own experience. As a result, I was struggling to move something forward or know how to prioritize, I wanted AI to help me get from half formed idea -> plan, but perhaps I need to add an interim step of half formed idea -> deeper understanding -> plan.

All in all, this I think supports a theme of what I’ve been hearing about AI, for example on the impact on senior devs (good for productivity) versus juniors (destroying their learning).

For my own takeaways:

go deeper

Navigating the AI Shift

From anxious and reactive to genuinely capable. Build real fluency with AI — without the hype.

go deeper

The EM Survival Guide

The EM job has changed. Four modules to become the force multiplier your team actually needs.

go deeper

DRI Your Career

Your career is yours to shape — or capitalism will shape it for you.

Exit mobile version