I think it was the EPA’s National Compute Center. I’m guessing based on location though.

When I was in highschool we toured the local EPA office. They had the most data I’ve ever seen accessible in person. Im going to guess how much.

It was a dome with a robot arm that spun around and grabbed tapes. It was 2000 so I’m guessing 100gb per tape. But my memory on the shape of the tapes isn’t good.

Looks like tapes were four inches tall. Let’s found up to six inches for housing and easier math. The dome was taller than me. Let’s go with 14 shelves.

Let’s guess a six foot shelf diameter. So, like 20 feet circumference. Tapes were maybe .8 inches a pop. With space between for robot fingers and stuff, let’s guess 240 tapes per shelf.

That comes out to about 300 terabytes. Oh. That isn’t that much these days. I mean, it’s a lot. But these days you could easily get that in spinning disks. No robot arm seek time. But with modern hardware it’d be 60 petabytes.

I’m not sure how you’d transfer it these days. A truck, presumably. But you’d probably want to transfer a copy rather than disassemble it. That sounds slow too.

Not looking at the man page, but I expect you can limit it if you want and the parser for the parameter knows about these names. If it were me it’d be one parser for byte size values and it’d work for chunk size and limit and sync interval and whatever else dd does.

Also probably limited by the size of the number tracking. I think dd reports the number of bytes copied at the end even in unlimited mode.

Mine looks a little like that. It’s my job though. Everything’s on GitHub.

I downloaded google lense a while back to identify a mushroom. It was pretty and I was curious. After installing and taking the picture it replied… “Mushroom.”

The second image said false widow’s death wish or something metal as hell.

I used gerrit and zuul a while back at a place that really didn’t want to use GitHub. It worked pretty well but it took a lot of care and maintenance to keep it all ticking along for a bunch of us.

It has a few features I loved that GitHub took years to catch up to. Not sure there’s a moral to this story.

Amazon is certainly interesting for open source. They’ve caused me and my friends a fair bit of trouble but they have made some real contributions. I feel like they only do it when they have to though. They are quite happy to take others work and give nothing back.

They just feel very disingenuous. Opportunistic. A bit sleezy. But some of my favorite open source hackers work there and do good work. It’s hard.

Thanks. I remember one of these had people being excited about it and I felt bad that I couldn’t try it. But Linux is hard and we are all so grumpy. I get it.

Is that the Mac only one?

I’m a pretty good engineer. Not the best I’ve ever met by a long shot, but I’m good. But I’m very outgoing for an engineer.

Ironically, that’d describe both my parents too.

I had this one weekend when I was in tenth grade where I did nothing but write code on a fun project. Then I decided I didn’t like writing code. I don’t know why. Kids are weird.

I decided then I couldn’t make it my job. I managed not to program for three years. It turns out I’m bad at everything else. Miserable.

That was 22 years ago. That’s still all I’m good at.

Five minutes of googling says some folks thing stone mason. Some copy and paste response says unskilled tradesman. Other response says translation is just “learned” so maybe they could read.

I’d never heard of this before so seeing that there is disagreement is a fun new thing for me. Especially interesting to see this “learned” response.

I spent a few minutes looking to see if a name I trust said any of this. Ultimately I don’t have the background to evaluate it and lots of folks spend their lives about historical Jesus. I didn’t see anything from anyone I recognized but, like I said, I don’t know much about this area.

Do folks still use logstash here? Filebeat and ES gets you pretty far. I’ve never been deep in ops land though.

In case you haven’t heard of it, check out Altered Carbon. It’s a series and the first book is cyberpunk noir detective stuff. Rest aren’t. Good, but not in the noir style.

The point of the license combination they use is to allow the enterprise version to be open and live in the same repo as everything else. Dunno if that’s what they do, but that’s why the elastic license exists.

The only surefire way is to read it all. And understand it all. That ain’t happening though. So you decide how much to do.

You should figure out how many people are landing patches and get a rough sense of why. Same for folks filing issues or talking about the project in general. Maybe you trust one of the contributors for some reason. Either way, you want to know how alive the project is.

You could land a patch.

You could spot check parts of the code.

You could run vulnerability scanners on it.

I dunno. It’s hard.

I’m not sure I’d attach any meaning to real names online. There’s a whole group of us whose online names are just things they thought were neat when they were 12. And they’ve just stuck forever. There’s lot of reasons.

But otherwise, yeah. I’ll spend ten minutes looking up someone’s online profile. Mostly for GitHub if I can find it. If someone’s commenting on public prs and seems nice that’s a big signal.

I agree. Light touch until you have a bunch of changes landed.

I was a professional open source contributor for a while. Still have the same job, but the license changed. Culture still quite similar though.

Amazing

We squash. I’m not really interesting in your local journey to land the change. It’s sometimes useful during review, but after that it’s mostly the state of the main branch I care about. It’s what I need to bisect anyway.

I don’t like commits that are just references to issues. Copy the issue into the commit message so git blame tells you something useful. Unless it’s just closing a simple big. Then the title and issue reference are plenty.

Depends on the project I imagine.