nik9000 @ nik9000 @programming.dev

Posts

1

Comments

133

Joined

2 yr. ago

Is that the Mac only one?

We knew spooks were all up in the phone network. They'd show up and ask installers to run them some cables and configure ports in a certain way. I was friends with folks who were friends with the installers.

I work on software for finding things and summarizing stuff. We were one of those Apache 2 -> other relicenses a while back.

I can't really talk about specifics. But we all have a working imagination though. I think about it a lot. But I still do the job. There are good folks doing good things with it.

I've been listening to the Andy Serkis reading it lately. First experience since I was a kid. It's surprisingly nuanced for something so old and so baked into the popular culture. It's kind of amazing how flattened my memory of it from childhood is.

Dune as well. And Snowcrash too

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.

Pre-merge code review should stop that kind of thing. I honestly haven't seen anything like this in years.

Chrono Trigger. The Magus Fight. The music.

FF6. Magitech Factory. Also music.

Metal Gear Solid. Psycho Mantis. Late at night. Tired.

Eternal Sonata. Last Fight. Intro line.

Hades. Final boss. Extreme measures 4.

NES Tetris. Crashing.

Windows -> RedHat -> Windows -> Gentoo -> Ubuntu -> RHEL -> Ubuntu -> Debian -> Arch

I hate the smell of some ground coffee. Others smell good.

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.

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.

I wonder what my last commit at each job was. I'll bet it was boring. About 10% of my commit messages are genuinely interesting.

I review a ton of code and have a bunch reviewed in turn. I don't remember that last time I've had this come up. Either direction really. I guess I'm lucky. We just split naturally in similar places.