offbyone

"jobs that are long-running might get rescued even if the producer is still alive" indicates otherwise. It suggests that jobs that are in progress may be double-scheduled. That's a feature that I think shouldn't be gated behind a monthly pro subscription; my unpaid OSS projects don't justify it.

Ooof. I don't mind the OSS/pro feature gate for the most part, but I really don't love that "Pro version uses smarter heartbeats to track producer liveness."

There's a difference between QoL features and reliability functions; to me, at least, that means that I can't justify trying to adopt it in my OSS projects. It's too bad, too, because this looks otherwise fantastic.

If you happen to nominate or vote on the Hugo Awards, you may have seen this turn up.

Self-hosting breezewiki -- even on the same machine that you browse from -- gets neatly around the way fandom wikis block the breezewiki public nodes. I've got it self-hosted and now I never see that damn fandom interface.

I've been doing this on my site for a couple of years: https://github.com/offbyone/ideas/blob/3f50f69494aca01f21aeb...

It's pretty easy to do. I recommend it, if you already use Fedi for anything.

Well, this is delightful; the links that this tool finds now 403, and looking at the network inspector, it seems that the URLs are now signed in some way.

I was your opposite number at AWS for many years. Like you say, it was one of the best jobs I've ever had, but over there it was a career dead end. I wasn't laid off, but I had to leave it to have any hope of growing myself.

I feel for ya, zem; if you ever turn up at a PyCon in person, lemme buy you a drink.

If you want my cynical take, here's the real reason that Amazon and other big companies are all-in on RTO: the commercial real estate collapse that may (will?) happen if downtown office districts don't repopulate: https://wapo.st/3QXHpFT

I think the reason that Amazon leadership isn't bringing data to support RTO is that not only are they aware of the "Urban Doom Loop” that this article is referring to, but I'd bet you a lot of money that the C-suite (S-team) has a significant investment in commercial real estate.

I had the distinct pleasure (?) of owning the C++, Python, and Java implementations of that config for a while and ... yeah, it had some positives, but the fact that it had two orthogonal hierarchies of configuration in addition to implementation-specific feature gaps and nuances made it something of a nightmare in practice.

The article is interesting in general, but this line really needs more than "works like a charm": `usb_modeswitch -W -v 12d1 -p 14fe -K -P 14ac -M "55534243000000000000000000000011060000000000000000000000000000"`

I mean, I believe you, but ... what on earth IS all of that?

I have been fortunate enough to land in a part of my employer's technical culture governed -- roughly -- by this sort of idea, albeit not one that's written down anywhere. The people in the Slack channels (IRC, back in the day, but time marches on...) that I frequent are the ones who provide some of the backchannel cross-team communication and technical analysis that make our company work.

I like this article a lot; if I were trying to replicate the community I've got now, I'd probably start with this.

Probably just delete.

Especially if it's the one I'm thinking of, too. It's a damn solid architecture.

I love build tools, and work with them professionally, and this tool seems to be getting one thing quite right: it is not injecting itself into the dependency resolution process. Where I see build tooling fall down is where they try to replace the idiomatic dependency modeling tools that exist in each language.

The build logic and CLI experience looks to be well thought out. I really like the native sandboxing support and the intentional exclusion of the calling environment. There's a lot of polish here.

That's going to be true to some extent of every library your company uses, but for every library someone writes and offers as FOSS, you don't have to spend the cycles designing, developing, and maintaining your own, nor training new hires on using it. You're fundamentally misunderstanding the value of having good quality tools developed by someone else.

And I'm not even going to _start_ on what I think of your attitude towards test tooling vs "central libraries" other than to note that if you don't consider test tools central to your development process, I think you have bigger problems.

Apropos of nothing related, I want to know: What, exactly, were you confident yet wrong about in regards to bay leaves?

Can you imagine how many [email protected] email addresses there'd be?

Huh. At this point I'm quite curious if I know you.

Almost as if he'd been the target of a nearly-non-stop decade of constant hostility and abuse or something.

I'm not sure I agree; Poettering isn't being harsh to his collaborators, here. He's protecting them against the implicit accusation of a hostile community member. I'd be _more_, not less likely to want to work on a project with someone who does that.

Probably for the best.. you're not really coming off very well here.

Yeah... BT is still pretty great. Good leaders for the most part, and the opportunity to have huge positive effects on many fronts.

I'll take "sentences I never thought I'd read" for $800, Alex!

Getting 3.x to work with mcpi is actually super easy; the library works nearly out of the box, and the code is basically the same as far as I can tell.

Well, I'm >5 years, two orgs, one of which re-shuffled a few times while I was there, trying to find the right fit between software engineering and domain expertise.

I've never personally seen any of the horrorshow stuff I hear about Amazon. I've worked with people who have, and mostly they just moved to other parts of the company. It's a big place.

I stay because I like it. I've turned down offers for more money in order to remain, because my job is satisfying, challenging, and balanced with my non-work life. I go home at 5 PM every day, get paged only occasionally, have a mandate to automate and stabilize my services that is at LEAST as high-priority as features or launches.

In short, the opposite of some of these complaints.

It's almost like there's nuance to be found here!

Ctrl-F "Match" No results found.

Still not usable, sadly.

That article misses the key point; a MITM proxy for mail is the actual problem, no matter how well implemented it is.

And we're hiring!

Because depending on the policies of your workplace, GPLv3 may be blacklisted; the nature of that license makes its use in certain classes of business very, very dangerous.

This. This, a thousand times.