[-] tr00st@lemmy.tr00st.co.uk 42 points 1 month ago

Accidentally hitting reply-to-all on a company wide email and more or less stating that I wanted to be transferred to another team.

There was a new team forming elsewhere, and in fairness, it was a great opportunity in a lot of ways. But... I didn't get the transfer until another batch of jobs opened a few months later.

That... was a long few months.

12
submitted 1 year ago* (last edited 1 year ago) by tr00st@lemmy.tr00st.co.uk to c/programming@programming.dev

Anyone have suggestions for getting some tools in place to monitor for when changes happen that match certain criteria (obvious one being when certain files change)? Hosting-wise, we use BitBucket Cloud, though I can't find anything built-in that'd be useful (seems like most cloud-based solutions don't offer pre-receive hook customisation?)

We've had some "issues" with people not considering the impact of changes to certain code, and just want a little more handholding before the next time that sort of issue happens. I'm sure I could rig something either with a webhookey endpoint, or a CI build that does it, but it just seems like the sort of thing there'd be a pre-built tool for.

Any ideas?

[-] tr00st@lemmy.tr00st.co.uk 8 points 1 year ago

Had something along these lines - a mail server that ended up used almost exclusively for sending automated internal emails. We'd migrated to a third party for email sending because managing DNS etc for clients got pretty painful. Mail server got removed by the tech lead and repointed to our third party mail provider without telling anyone, and 3 days into the months we'd hit our billing limit, on the lead's day off. Turns out that one service had been sending an order of magnitude more email than all of our other services put together, as someone had been using email as a logging method.

That was a... fun day.

[-] tr00st@lemmy.tr00st.co.uk 100 points 1 year ago

Is this a surprise? User retention is hard, and I'd expect this to hit even harder as time goes by. It'll keep going up until the point where user growth matches attrition and I'd guess in the early days of a social platform, it's going to take a while for background growth to increase that much and attrition will be pretty high given the lack of attachment.

[-] tr00st@lemmy.tr00st.co.uk 28 points 1 year ago

That's 102 stars more than my best... Nicely done :)

[-] tr00st@lemmy.tr00st.co.uk 16 points 1 year ago

I'm too lazy to find a picture of a spider for this joke - this exercise is left for the reader.

[-] tr00st@lemmy.tr00st.co.uk 5 points 1 year ago

In the 13 years I've had a Reddit account, I made 40 comments, and 4 posts.

In the 15 days I've had a Lemmy account, I've made 28 comments and 1 post.

Now I wouldn't want to be one for extrapolating from data of different timescales, but...

[-] tr00st@lemmy.tr00st.co.uk 7 points 1 year ago

I, a real normal human person, would consume the turtle with my regular bone teeth, in the usual fashion.

[-] tr00st@lemmy.tr00st.co.uk 7 points 1 year ago

I really want the Vim/VS Code one - as someone who professionally devs in an MS stack, but would choose Vim as a primary text editor otherwise... it speaks to me deeply.

5

Summary first - I'm looking for software to use for web-controlled music playback. Main requirement is playback via a DAC on the hosting device and a half-decent UI for it (though streaming would be nice...).

Hardware-wise, I've currently got a Pi Zero W paired with a HiFiBerry DAC+ Zero, which has been fine for me quality-wise, routed as an aux input to an old HiFi. That, plus plenty of space elsewhere to host split apps - currently running Emby as a main streaming host for other media, and the media is just on a NAS pulling over NFS.

I've been using Volumio for a while, but have been frustrated with a few things (UI, playlist management, etc) so I'm looking for a change. Streaming from Emby/Jellyfin via DLNA looks like it might be a decent fallback, but I'm wondering if there are any nicer ways to handle it.

Any ideas? Open to switching a few bits of infrastructure around, of course :)

[-] tr00st@lemmy.tr00st.co.uk 7 points 1 year ago

Thanks for highlighting probably the most important part of the article.

[-] tr00st@lemmy.tr00st.co.uk 17 points 1 year ago

The language in the article does seem to forget that plenty of early smartphones had replaceable batteries... Yeah, it might add some bulk, but it's not exactly going to be a major hardship.

... but it seems like a good reverse step to me. Any consumer replaceable part is a good thing as far as I'm concerned.

[-] tr00st@lemmy.tr00st.co.uk 9 points 1 year ago

Two main points personally:

  • with self-moderation, you can't really say "I don't want to see this sort of content", you can only say "I don't want to see this content again". A well stated set of rules for a community let's you know what to expect, so you get to make that choice if advance. This is a massive difference in preventing distress and general unpleasant feelings. It's not absolutely necessary, but it's a lot nicer.
  • it avoids massive duplication of effort. If you have a moderator-to-reader ratio of 1000:1, you'll be saving the vast majority of self moderation with those people would be doing. Yes, reporting exists, but it's a tiny fraction of the time one would spend "moderating" for yourself
[-] tr00st@lemmy.tr00st.co.uk 9 points 1 year ago

Fun fact: your known bug count is super low if you don't test properly.

view more: next ›

tr00st

joined 1 year ago