This.

On my fun side project, I don't accept pull requests because writing the code is the fun part.

Only once did someone get mad at me for not accepting their pull request.

If I need to connect to my home Fedora machine from work, a simple "ssh fed.nono.io" works just fine — I don't need to activate my Wireguard VPN; I don't need to worry about address space collisions.

And this is not limited to 2010s! My father worked as a software engineer in Poland in the 1960s, and the communist party had a problem: every profession had at least one member of the communist party except the programming profession. But the Polish programmers weren't interested in joining, not even with the perks of a bigger apartment or cars. Finally they got one programmer to join the communist party, but he wasn't interested in programming, and only became a programmer so he could join the communist party & get the perks.

I'm doing this for the love of it.

Maybe "love" is too strong a word, but I certainly "like" what I'm doing, and I "like" computers, and I have a computer side project that I "like" doing and don't get paid for. Heck, when I was a summer student at IBM I couldn't believe they were paying me for something that was so fun!

I remember at Bell Labs they had one title: MTS (Member of Technical Staff). You were an engineer, and that was that. (disclaimer: there were a handful of DMTSes (Distinguished Member of Technical Staff)).

No one said, "I'm an E7" or "I'm a Staff Engineer II". Those statements strike me as distasteful. And begs the question if we're being suckered by Human Resource's gamification of work.

I worked at a company, Pivotal Labs, where everyone's title was "Pivot". It made for an egalitarian workplace. That changed after the acquisition, and we got titles. My proudest moment? Not when I was promoted from Senior Engineer to Staff Engineer, but rather the after-hours work I did with Dimtriy to expand our offering to include IPv6.

At my current startup, there are no titles, and I'm grateful for that.

I created an "administrator" account, but apparently it can't see the billing information, including the very-important amount of remaining cloud credits.

Maybe I could spend time fiddling with IAM to get the right privileges, but I have more pressing tasks. And besides, on my personal AWS account I only log in with the root account.

My experience is different: Comcast has been doling out IPv6 addresses for at least a decade, at least in San Francisco.

My T-Mobile phone gets IPv6 addresses.

My work and my swim club also have IPv6. It's pretty awesome.

I like coding, but am not fond of reviewing other people's code.

Also, the few PRs I received weren't up to snuff: for example, they included code changes but not tests. If they included tests, they weren't comprehensive. And they never included documentation changes.

I keep a public (transparent) list of takedowns, on a public repo on GitHub. The commit messages are the logs. [0]

I have a way to dispute: raise a GitHub issue. I've only had two people dispute: one was legit, and I unblocked him, and the other ran a WordPress site which he didn't know was compromised. I did not unblock him. [1]

Please don't judge me harshly for honoring the takedowns immediately, but I do so because the remedy is simple: register your own domain, and don't rely on my nip.io / sslip.io service (which maps IP addresses to hostnames as a convenience for developers, e.g. 127.0.0.1.nip.io → 127.0.0.1).

Dealing with takedown requests is the least pleasant aspect of running FOSS project. I want to spend my free time coding, not blocking phishers, scammers, and grifters.

[0] https://github.com/cunnie/sslip.io-blocklist [1] https://github.com/cunnie/sslip.io/issues/100

Me, too. The drive was unrecoverable. I had to reinstall from scratch.

At my old job we supported only two versions of our software product, Tanzu Operations Manager versions 2.10.x and 3.0.y), and we cut new patch releases every few weeks (similar to Apple's cadence). Bumping dependencies was a pain. Well, usually it went fine, but sometimes you'd hit a gnarly incompatibility and you'd either pin a Ruby package to a known version or try to modify the code just enough to make it work without making a major change.

If I had to put a number to it, I'd say it cost us 2 developers to keep our older product line consistently patched, and our product was a modest Ruby app, much less complicated than an entire OS.

The Alcoholics Anonymous San Francisco website had to implement CAPTCHAs on their website because scammers were making one-time donations to make sure their stolen credit cards were still valid. Every morning we had to invalidate a dozen obviously-fake donations.

Edit: typo

Similarly, I love swimming in the open cold water, but I never wrote down, "Swim from Alcatraz twice". It wasn't necessary. It happened organically.

I remember protesting at Penn in '85 ('86?) to persuade the trustees to divest from companies doing business in apartheid South Africa. And you know what? The trustees divested.

Now fifty-seven, he confided, "I think I made the wrong decision."