How We're Using AI in Our Work These Days (Practical Notes)

We've been integrating AI tools at the team level since last year, and I've gathered only the ones that actually worked. About half of what we adopted just because it was trendy has been scrapped.

1. Code review assistance

Run it yourself before opening a PR and preemptively fix the issues that would get flagged. You can really feel how much reviewer time it saves.

2. Document drafts

Design docs or meeting summaries. But you can't just use them as-is; terminology consistency has to be done by hand.

3. Log analysis

Paste in error logs and get a "list of likely causes in order of probability." I make the final call.

4. Generating test cases

For getting ideas for edge cases.

5. Internal search chatbot (RAG)

The more documentation a team has, the bigger the effect. But if you don't set a cadence for ingesting the latest docs, it can actually lose people's trust.

Overall: It's not a silver bullet; it's strong for repetitive, draft-type work. If you use it as-is where judgment is required, it causes problems.

by 프롬프트장인259

6 answers

Agreed. Especially #1, the code review assistant really makes a noticeable difference. The number of times I get nitpicked by reviewers has dropped significantly.

by 문과출신개발자953 · ▲0

Well, I'm a bit skeptical about log analysis. It's nice that it lists candidate causes, but when plausible-sounding wrong ones get mixed in, I've wasted time digging in the wrong place early on more times than I can count. Ultimately, it's not much different from the skill of the person reading the logs.

by 알고리즘고수815 · ▲0