74 lines
5.1 KiB
Markdown
74 lines
5.1 KiB
Markdown
---
|
||
author: "Lumo (AI) & Human Editor"
|
||
date: 2026-01-15
|
||
title: "Using AI as My Daily Driver at Work"
|
||
draft: false
|
||
tags: ["AI", "Productivity", "Software Engineering", "Glean", "Claude", "Lumo"]
|
||
summary: "A fresh Software Engineer II shares how internal AI tools and Lumo are reshaping his everyday workflow."
|
||
---
|
||
|
||
<!-- All blog posts generated by AI will be marked as such at the top. -->
|
||
|
||
# Using AI as My Daily Driver at Work
|
||
|
||
## Why I’m Jumping on the AI Bandwagon
|
||
|
||
In my new position, at my new company, as a Software Engineer II, I finally got the chance to treat AI like a coworker instead of a distant sci‑fi concept. Up until now, my interaction with AI was limited to the occasional prompt, just to see what comes back, or minor experiments with editing code. So, you can imagine my excitement (and a dash of trepidation) when I started experimenting with a handful of tools that promised to make my day‑to‑day less about copy‑pasting and more about actually *thinking* about code.
|
||
|
||
> **TL;DR:** I’m learning, I’m stumbling, and I’ll be documenting the whole messy journey right here.
|
||
|
||
## Meet Glean: My New Internal Swiss‑Army Knife
|
||
|
||
Glean is the internal AI assistant we’ve been handed to tame the corporate jungle. Here’s how it’s already become indispensable:
|
||
|
||
| Task | How Glean Helps |
|
||
|------|-----------------|
|
||
| **Learning about the company** | Quickly pulls together onboarding docs, team structures, and product roadmaps into bite‑size summaries. |
|
||
| **Writing reports** | Generates first drafts from raw data, then I sprinkle in the human touch. |
|
||
| **Keeping up with todos** | Turns vague meeting notes, slack messages, and jira tickets into actionable checklist items. |
|
||
| **Creating tickets & ticket summaries** | Drafts clear, reproducible bug reports and feature tickets in seconds. |
|
||
| **Writing PRs and PR comments** | Suggests concise change descriptions and even offers polite reviewer feedback. |
|
||
|
||
The best part? Glean learns from our internal vocab, so the output feels *almost* like it was written by someone who’s been here for years—minus the coffee stains on the keyboard.
|
||
|
||
## Claude: The Code Whisperer
|
||
|
||
While Glean handles the “process” side of things, Claude is my go‑to for the gritty code work:
|
||
|
||
- **Understanding codebases** – Feed it a file or a function, and it spits out a plain‑English walkthrough that even my non‑technical friends could follow.
|
||
- **Summarizing code paths** – Need a quick overview of a complex execution flow? Claude condenses it into a tidy diagram description.
|
||
- **Finding bugs** – By describing symptoms, Claude suggests likely culprits and even points out suspicious lines.
|
||
- **Making edits** – Want to refactor a method? Claude proposes a clean version and explains why it’s better.
|
||
|
||
## Lumo: The Secret Sauce Behind This Post
|
||
|
||
Full disclosure: this very post was *originally* drafted by Lumo, Proton's AI. I then gave it a once‑over, correcting misconceptions and adding details, and hit publish. Going forward, every AI‑generated article on this site will carry the same banner so you know exactly where the magic happened.
|
||
|
||
Using Lumo for blogging feels oddly satisfying—its ability to respect Hugo’s markdown conventions while keeping the tone light makes it a perfect partner for a technical audience.
|
||
|
||
## What’s Next?
|
||
|
||
I plan to keep a running log of wins, fails, and the occasional “aha!” moment as I integrate AI deeper into my workflow. Expect future posts on:
|
||
|
||
- Automating code reviews with Claude
|
||
- Turning Glean‑generated tickets into sprint stories
|
||
- Measuring productivity gains (or losses) from AI assistance
|
||
|
||
Stay tuned, and feel free to drop a comment if you have tips, tricks, or cautionary tales of your own!
|
||
|
||
## Prompts Used
|
||
|
||
### Project Instructions
|
||
|
||
- Make the blog posts a minimum of 100 words, but no more than 1000
|
||
- Casual tone
|
||
- Markdown format to be used with Hugo
|
||
- Make sure to include a headers menu section as well
|
||
- Keep things light and humorous
|
||
- These are for a technical audience
|
||
- This will be on https://flow.halvo.me, use blog posts there as example formatting
|
||
|
||
### Prompt
|
||
|
||
Write an intro blog post about using AI as a daily driver at work. Use the language of "in my new position as a software engineer II" instead of mentioning any specific companies. Note that I haven't used AI much in the past so this is a new experience that I'll be documenting as I go. Mention using internal AI tool glean, for learning about the company, writing reports, keeping up with todos, creating tickets and ticket summaries, writing PRs and PR comments, and more. Mention using claude for learning how the code works, summarizing code paths, finding bugs, and making edits. Mention the use of Lumo for this blog post and future ones, make sure to note that all blog posts generated by AI will be marked as so at the top. Make a note at the top that this blog post was originally written by Lumo and edited by a person. Include this prompt at the end, under a heading `## Prompts Used`. Under that heading put the Instructions that were given as well.
|