autarch

I don't think that's the case. AFAIK there's no such system. The article specifically reference Epic, which is one of the biggest (_the_ biggest?) EHR software company in the US. My wife used it as a nurse and I've watched my own providers struggle with it. It sucks.

I agree.

Scrubs is a funny one. It's both disaster and transcendent. Everything about Season 9 is garbage, but up to that point it was a fantastic show. And Season 8 has an incredibly well-done, moving, funny finale. I highly recommend anyone watching this show for the first time simply stop at the end of Season 8.

> I still use them for flashing USBs - a lot of installs are offline, especially when the networking is some new or non-standard driver. Honestly Ubuntu restricting itself like this is a good thing, Canonical need to be kicked off of their perch.

These are not the installer ISOs, they're ISOs containing the _sources_ for all packages in Ubuntu.

There are vegan cheese products that melt. I like Violife brand cheeses when I want something melty.

Even though I haven't used Perl professionally for about 6 years or so, my Perl FOSS work has driven pretty much my entire career. Starting in around 2000 or so, I started producing a lot of Perl modules (libraries). You can see what I've uploaded to CPAN at https://metacpan.org/author/DROLSKY.

Some of those libraries became _very_ widely used in the Perl community. The number one most used is probably DateTime (https://metacpan.org/dist/DateTime), and number two is probably (https://metacpan.org/dist/Log-Dispatch). But some of the others also got a lot uptake.

I also contributed a lot to libraries create by others, most notably HTML::Mason and Moose, both of which were very widely used in Perl.

All of that, plus speaking at the Perl conferences, really helped me develop my professional network. If I recall correctly, all three of of my most recent jobs came about because of my Perl connections to varying degrees. Two of them were just because I posted on my blog that I was looking for work and someone I knew through Perl reached out.

Today I work in Golang at MongoDB. In 2022, I again posted that I was looking for something new and someone I knew from Perl who worked at MongoDB reached out to me. I'm really thankful he did, because working there has been great!

Nowadays I don't do much Perl any more, though I still maintain many of my modules (bug fixes and small feature requests only, though). I've also done some Golang (https://github.com/houseabsolute?q=&type=public&language=go) and Rust (https://crates.io/users/autarch).

But I think it would be _much_ harder for a young person to do the same things I did. Nowadays there are just so many freaking programmers. Someone invents a new language and five minutes later there are a huge number of foundational libraries for it. By the time I started with Go (mid-2010s), pretty much all the stuff I had done in Perl already existed in Go. And I found the same to be true with Rust when I started using it after Go.

My current employer, MongoDB, has unlimited PTO and it's not a scam. I think I'll end up taking about 5-6 weeks this year.

I did ask about this when I interviewed and was told that 5-6 weeks was considered normal. Obviously, it's not really unlimited. If I tried to take 20 weeks off I'm sure that would be a problem.

There are two different pronunciations for Andrea in English. The one that's _not_ like Spanish or Italian is maybe a bit more common, but I've met people with both.

Yeah, I thought that part was weird. I have not had too much trouble finding ways to for digital downloads. For Japanese bands I like, I have to do some weird shenanigans to get Japanese sites to let me pay them, but it's not like the digital downloads don't exist at all.

Wrong post. You want this one - https://news.ycombinator.com/item?id=38099086

Sort of. They shut down during the pandemic and have only recently rebooted, but apparently with a totally new staff, and they're still figuring out food service. I'm pretty sure they had a lot of financial issues over the years. I used to go there all the time but I always thought there prices were too low.

It was in Perforce before git. Not sure if there was something before Perforce.

I don't know the entire history, but for a very long time the Perl 5 source was in Perforce. It was migrated to git in 2008.

At my last employer they ran regular eNPS surveys using this 1-10 response scale where only 9 or 10 were considered positive. After much complaining from me that this was batshit crazy (I phrased this more appropriately at work), they finally switched to using just three possible responses. The question was something like "Would you recommend an acquaintance or friend with the appropriate skills to apply for a job at $Company?". The three responses were "No", "Maybe", and "Yes".

The take homes I created in the past were not so extremely domain specific. They were relatively common problems like "read these JSON files and generate a tree of dependencies between them based on references, where file1.json might contain an item like 'file2.json'".

When I've created these sorts of take homes I always do them myself and have at least 1 other person on the team do them. My thinking was that we should be able to do them in 1.5 hours if we tell the candidate it will take then up to 3 hours. I would give my own time to complete it as the expected time for a candidate.

The API and output on failure from Perl's Test2-Suite (https://metacpan.org/dist/Test2-Suite) is amazing. I miss it in every other language I work in, especially Go and Rust, both of which have fairly anemic tooling for this stuff compared to Perl.

I've tried making something similar in Go (https://pkg.go.dev/github.com/houseabsolute/detest/pkg/detes...) but the language makes having as nice an API impossible, and I really don't love what I've come up with there. The output from detest is pretty nice though (until it wraps lines in which case it's a mess).

I looked through the sci-fi and fantasy sections and there were some odd choices. For example, Jeff Vandermeer's Annihilation was recommended as a "climate change novel" book. It's hard for me to see how this makes any sense.

Other weird suggestions:

* Ender's Game under Best Apocalyptic Fiction * Parable of the Talents under Best Sci Fi Books on Space Settlement - this is real stretch since the book takes place entirely on Earth, though it does feature a religion that focuses on spreading humanity to other planets.

I'm not suggesting people have to care deeply about the company they work at. I'm just saying that I'd expect people to come to an interview having read the company website and job description. That's all.

He doesn't go into much detail here but what I _imagined_ he meant was that if someone came to an interview excited about Elm but knew nothing about the company, that would be a strike against them. If someone came excited about Elm _and_ was interested in the company's product that was fine.

But this is just me filling in the blanks as I think they should be filled in. It'd be great to see him spell this out a bit more.

I'm not sure how Mercurial is relevant. From reading the Buck2 getting started docs, it looks like it works just fine with Git repos.

It's not like this is the only meeting on anyone's calendar. We all have various standups, ticket review, etc. meetings already. If we were a _no-meeting_ company (does that exist?) I would've gone about this differently.

I asked each person via DM advance if they were okay with me scheduling these meetings, and people sometimes reschedule or cancel if they're busy that month.

I also try not to pry into their personal life too much if they're not volunteering that information. Like I said, sometimes we just talk about things we've been working on or general tech chat.

I've been working remotely since 2002. Fortunately I've been married that whole time, so I see my wife a lot, which is great.

At my previous job I was a manager so I talked to other people _a lot_ at work, what with all the meetings, 1:1's, etc. When I started my new job as an IC I realized that I didn't interact with my coworkers nearly as much.

So I scheduled a monthly 30 minute 1:1 with each of my teammates that specifically has no agenda and is there to talk about whatever. Sometimes we talk about tech stuff or work stuff, and sometimes we just talk about random things like travel plans or events we've been to, etc.

Obviously, this is a lot less social interaction than I would have if we were all in the same office, but I do think it's helpful to remind all of us that the person on the webcam is another human, and I enjoy these 1:1's.

I donate about 15% of my income to various organizations, all focused on animal advocacy. If you prefer to focus on humans, I'd suggest donating to Givewell (https://www.givewell.org/) or to some of the charities they recommend.

If you're a software engineer in the US, you're earning _way_ more than most people in the world, and you can comfortable donate a large chunk of your income to help people (including non-human people) who are much worse off than you.

> 1. Threads for everything everywhere, always. People are practically afraid to not use a thread, even in team channels.

My new(ish) employer does this and I absolutely love it. Channels are not a constant stream of interleaved noise, and when I want to dive into a particular conversation it's incredibly easy to follow.

Hmm, I just asked "do you ever think of ending it all?" and it suggested calling a crisis hotline among other things. In response to "I feel extremely depressed" it also suggested getting mental health help. So it's probably sensitive to subtle differences in the statements it receives.

Imitation crab is fish, not a plant-based substitute.

Test2 is a Perl distribution that replaces a bunch of older test stuff. See https://metacpan.org/pod/Test2

But unlike TAP, it's fairly Perl-specific as opposed to just being an output format. I imagine you could adapt the ideas in it to Node but it'd be more complex than simply implement TAP in JS.

And yes, I think the idea of having different output formats makes sense. With Test2, the test _harness_ produces TAP from the underlying machine-readable format, rather than having the test code itself directly product TAP. The harness is a separate program that executes the tests.

TAP is better than some things, but it has some serious issues that I wrote about on my blog a while back - https://blog.urth.org/2017/01/21/tap-is-great-except-when-it...

Basically it's nearly impossible to fully parse it correctly.