Great advice, I usually forget to do this. Another presenter suggested I build it into my talks right after the title slide to help remember.

Software is much more complicated so the default assumption is someone worked hard on it. And in the case of OSS, usually given away for free.

Hehe, yeah I guess there is some grey area there based on how much effort people are putting into the thing. Like I doubt a fast food employee gives one iota of a shit if you criticize their intentionally paint-by-numbers meals.

Same thing with meals. If someone cooks me a meal I don't like, I don't say it's shit, I just politely say I didn't like it. Or I make suggestions about what would make me like it more.

That said, feel free to apply the same standard everywhere. Instead of saying a movie sucked, just don't recommend it. If asked you can merely say you didn't like it, or give specific details instead of a lazy dismissal. Both are better than going out of your way to publicly shame the work.

More so than the rest of those examples, software is expected to have revisions and improvements. And with open source software it almost certainly has an issue tracker for constructive feedback to facilitate those improvements. Simply saying it sucks or calling it shit is both lazy and cruel.

I enjoyed the first one, haven't seen this one yet but looking forward to it.

Would you say it's good for a sequel, good outright, or even achieved the rare feat of being better than the first?

Maybe you're OK with people trashing things you create because you vibecoded them, but that's not the case for most people. You can be a better person by having just the smallest amount of empathy here. Or don't, I won't keep trying to convince you, muting and moving on. I hope your day gets better.

I don't think I'd ever use an AI-generated result blindly, but it seems like a big time saver to get something that is most of the way there and just needs verification and tweaking. At the very least this would be me on the right track and help me understand what documentation to dig into.

This matches directories with the exact name ansible, but not directories containing ansible in the name. But it was easy to adjust the pattern to `*ansible*/*.{yml,yaml}` which worked as desired.

prompt:

write me a vim config line to set the filetype to yaml.ansible for files with the yml or yaml extension in directories that contain the word ansible

result:

autocmd BufRead,BufNewFile */ansible/*.{yml,yaml} set filetype=yaml.ansible

Not perfect, but really close.

prompt:

what are the graphicsmagick flags to resize an image

result:

gm convert input.jpg -resize 800x600 output.jpg

Perfect.

prompt:

give me a git log command formatted with one commit per line, only including the date in yyyy-mm-dd format, the short commit hash, author name, and author email (in that order)

result:

git log --pretty=format:"%ad %h %an %ae" --date=short

Perfect.

The lab is still functional. I periodically make improvements, usually after delivering it in person and people give me feedback. At some point in the future it will be migrating to a new lab platform, but I'll make sure the new one works and change the short URL as needed.

workshop:
bit.ly/hellorpm

slides:
carlwgeorge.fedorapeople.org/presentation...