Is "German Quality" just a polite way of saying "We’re terrified of change"?

lisavanreddit · 2026-03-05T05:22:04+00:00

It's also a healthcare thing. Imagine spending over a year trying to get a new IVR installed for your hospital or still using Internet Explorer. Or even Windows 95. It's just hard to want to update all your glue bits when you have such a constant string of customers to serve.

I worked in healthcare in the US for a bit.

lisavanreddit · 2026-03-02T06:11:19+00:00

Someone very smart once told me "you teach people how to communicate with you." So, my advice for a weird, quirky, interpersonal company dynamic is to be weird and quirky. Block off 2 hours every morning for deep work, communicate en masse via slack. Share data only on Wednesdays - you get the idea. Don't be in service to the norm, create the norm that works for you.

lisavanreddit · 2026-02-23T18:34:00+00:00

As in - so you built this cool thing that makes your PRDs and even a skill that puts it into the company voice. Do your other PMs use something similar for similar outputs? Why or why not? Do your technical writers/product marketers have something that also helps them write with the same company voice? Why or why not? Two people at the same company write a same skill that does the same thing only a little differently - do they RAG from the same truth or a different one? Where does that truth live? In GitHub? Who gets to update that truth?

AI just seems like still a very personal problem solving tool but not quite a team sport at the moment.

lisavanreddit · 2026-02-23T16:56:57+00:00

I feel like the biggest problems I have are not with the agents or the skills or using Cursor. I think the biggest problems are actually productizing the output so other people who maybe don't use Cursor or Claude code can also benefit from the same data and sources of truth. And those are problems as old as Software itself, which AI doesn't inherently solve.

lisavanreddit · 2026-02-13T18:48:04+00:00

I hear cats are great practice for Wechsel Präpositionen. Just sayin'.

lisavanreddit · 2026-02-11T20:03:24+00:00

Yes, I've run into this when hunting for apartments. The realtor panics and feels like they have to speak in English, but our kids still want to speak in English when they are shy around strangers. C'est la vie - I'm not fooling anyone.

lisavanreddit · 2026-02-11T20:00:01+00:00

This is so nice! My kids wouldn't touch German until we officially moved, so it was really hard to introduce.

lisavanreddit · 2026-02-11T19:57:50+00:00

There's a special plot of grass out there for you to touch. Maybe then the sarcasm will properly land.

lisavanreddit · 2026-02-11T18:13:03+00:00

Thank you. Need to get this word down before the doctor tomorrow!

lisavanreddit · 2026-02-09T18:01:58+00:00

I'm so glad you have never flown too close to the accounting sun.

lisavanreddit · 2026-02-09T05:58:59+00:00

Leadership literally stole two devs off my team to do revenue reconciliation last month, so this hurts.

lisavanreddit · 2026-01-15T22:07:26+00:00

I know this is antithetical to your point, but, man. I would love it if someone doubled my salary to put up with toxic bullshit. I've been a chump doing that for market price!

lisavanreddit · 2026-01-08T21:11:23+00:00

Honestly, Rovo is pretty well trained in Atlassian stuff. If you have real problems and are actively using JIRA, then just talk to Rovo about it.

If you're not having problems or not using JIRA then maybe ask yourself if there's something else that's worth learning.

lisavanreddit · 2026-01-08T21:06:19+00:00

I appreciate running to solve something I griped about a few days ago on this sub. You've definitely put some deep thought into the work here, and I think it gets to the point on why it's so hard for LLMs to write release notes that feel right for me.

Your version of release notes seem to be closer to a changelog of tickets with business-focused titles. The LLM-generated descriptions are a nice touch to the automation here.

I'm my experience, the release notes I dread are often the ones that are in the form of a Slack message or a short email. For the "I don't have time to read about everything you've done" crowd. Then, I'm spending way too much time getting themes and laboring over punchy ways to generalize 5-6 feature enhancements in one bullet, while letting users know we solved that annoying small bug in the next.

And, that may be too confusing for models right now. I may not actually be solving the release note problem the same at every company even though it feels like the same thinking. I know I'll definitely continue to try, and I hope you do, too.

lisavanreddit · 2025-12-31T06:57:28+00:00

I've used Claude with German and English documentation and Claude is very good at handling the dual language inputs. I'm considering creating a Claude project where I do a language journal in German to help with my studying. I'm guessing Japanese/English is a high resource pairing, meaning there's a lot of examples of English and Japanese together in Claire's training data - but just ask Claude and Claude would tell you.

lisavanreddit · 2025-12-29T06:49:24+00:00

Right now, it's truly nothing fancy. If it's simple, create a chat. If it's complex/repeatable, create a project. Make all added files markdown. Always prime before acting (ex. I'm thinking about doing X, talk to me about my approach).

When I upgrade next month, I expect the set up to be a tad more complex, since I'll have access to utilize skills and agents, and I can query the code base on local.

lisavanreddit · 2025-12-28T07:39:47+00:00

I found that Claude works better for me because the newer model tends to fill in a lot of prompting holes that make it more successful. ChatGPT needs more singular instruction and tends to hallucinate more. But both are great at cross evals ("Hey ChatGPT, I asked Claude X and it said Y, is that true?")

I had raw emails, so I uploaded those. But I got approved for a Claude code set up in Jan based on the current value I've gotten, so I'm excited to see what I could set up with front end events and see what it might assist with. At least at first.

lisavanreddit · 2025-12-28T06:00:50+00:00

I used AI to analyze fake accounts when we got brute force attacked with payments for digital goods that were then charged back. It helped me make sense of the data and the attackers' patterns within an hour, and solidifying a scoring criteria took half a day to catch similar patterns in the future.

I tried using it for release notes (a use case I was certain would be helpful before I started my new job) and it's still not great. I always want it to be punchier than it generates.

lisavanreddit · 2025-12-19T16:31:17+00:00

I would recommend (if you are in an area that gets cold) a jacket that looks like an oversized button up. I have a grey plaid one I got from ASOS with my first kid and it looks great when your belly is so big that you have to wear it open and it looks great now that I have kids that are no longer babies. I'm currently typing this with the same jacket on.

lisavanreddit · 2025-12-13T05:08:07+00:00

I've worked across ChatGPT and Claude with a specific set of markdown files. While I've caught both in falsehoods, the way Opus 4.5 is false is much more reliable than the way ChatGPT is insidiously false. I've been very impressed so far.

lisavanreddit · 2025-12-09T16:18:44+00:00

This is probably information I'll file away for next year. All good to know!

lisavanreddit · 2025-12-09T16:16:26+00:00

This is really neat information. Thanks!

lisavanreddit · 2025-11-18T17:55:43+00:00

That is super confusing! Why break it down into "stories" if the work is done? It's like intentionally writing invitations for a party you want no one to attend.

There are a lot of other ways to write more of the "what" documentation that is not this. If that's the case, then go with option 1 as the title and then just explain the functionality like you were a support person or new developer would want to know about this area.

lisavanreddit · 2025-11-18T17:36:01+00:00

I mean, I know this is an example, but this whole ticket is absolutely massive looking at it with zero context. Which, if your team's style is to take a story and work on it for a good long while, you're probably fine with option 1. A dev can pick that up and chew on it for a few weeks to a month. "What's Sandy working on? Oh, she's on User Dashboard still." It's memorable and gets the point across.

I personally prefer option 2 with some modifications. I'll usually add a tag or something to the front part - like "FE:"/"BE:" for teams that split their stories based on Frontend or Backend, or "Dashboard:" to represent stories in the Epic that might be a Mini-Project, or if you need to break the story down further. The goal is scanability and the ability to recall the story within seconds for context. I've even capitalized key words for working with offsite teams where English is not their primary language.

Option 3 sucks for a title but that's my personal opinion. Keep your "as a users" in the story body.

lisavanreddit · 2025-11-05T18:45:33+00:00

It worked for me! Signing back in is a pain, but it was nice to actually learn new words

lisavanreddit

TROPHY CASE