paul/flow-hugo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Starting my ai journey

Browse Source
This commit is contained in:
paul
2026-01-15 13:30:10 -05:00
parent b461a26bee
commit e24edc5b88
1 changed files with 7 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
content/posts/intro-to-ai-at-work.md
View File

@@ -11,17 +11,9 @@ summary: "A fresh Software Engineer II shares how internal AI tools and Lumo a
# Using AI as My Daily Driver at Work
## Table of Contents
- [Why I’m Jumping on the AI Bandwagon](#why-im-jumping-on-the-ai-bandwagon)
- [Meet Glean: My New Internal Swiss‑Army Knife](#meet-glean-my-new-internal-swiss-army-knife)
- [Claude: The Code Whisperer](#claude-the-code-whisperer)
- [Lumo: The Secret Sauce Behind This Post](#lumo-the-secret-sauce-behind-this-post)
- [What’s Next?](#whats-next)
- [Prompts Used](#prompts-used)
## Why I’m Jumping on the AI Bandwagon
In my new position 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 “Hey Siri, set a reminder.” 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.
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.
@@ -33,7 +25,7 @@ Glean is the internal AI assistant we’ve been handed to tame the corporate jun
|------|-----------------|
| **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 into actionable checklist items. |
| **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. |
@@ -48,13 +40,11 @@ While Glean handles the “process” side of things, Claude is my go‑to for t
- **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.
It’s like having a senior engineer on standby, except Claude never takes a lunch break (or asks for a raise).
## Lumo: The Secret Sauce Behind This Post
Full disclosure: this very post was *originally* drafted by Lumo, the AI you’re reading about. I then gave it a once‑over, added a few personal anecdotes, 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.
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 that still appreciates a good joke.
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?
@@ -68,7 +58,7 @@ Stay tuned, and feel free to drop a comment if you have tips, tricks, or caution
## Prompts Used
**Project instructions:**
### Project Instructions
- Make the blog posts a minimum of 100 words, but no more than 1000
- Casual tone
@@ -78,4 +68,6 @@ Stay tuned, and feel free to drop a comment if you have tips, tricks, or caution
- 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.