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.
That is because your provider is nice and gives you a static pre-fix. Around here, all the providers give dynamic IPv6 pre-fixes to prevent people from running servers. This is partially why some see Ipv6 as a advantage, and others see it as nothing but trouble. We still have the whole Ipv4 CGNAT disadvantage, with the added complexity of Ipv6 on top.
Thumbs up on Concourse CI: I like seeing all my builds at once on any easy-to-read dashboard. That’s why we switched from GitHub actions: the dashboard.
Measuring oneself as an engineer by the title of the salary band you're in is a disservice.
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 had the pleasure of working with a handful of Pivots for about 2 years, and I have to say that felt like the closest I ever got to a healthy engineering culture. Delightful people, superb engineers, always focused on working and learning together. I feel really privileged to have worked in that environment.
For the first 10 years or so of my career, I didn’t even know my job title. I knew my pay, which is what I cared (and still care) about. They could call me the janitor as long as they paid me a good salary and the work didn’t change.
It wasn’t until one of my startups was bought by a big corp that I came to learn my job title, because suddenly it was tied to compensation. That mattered.
> Measuring oneself as an engineer by the title of the salary band you're in is a disservice.
It's really not that deep - people do this because both a title and salary are effectively money you can bank and that's the only thing that matters - we don't work grueling, stressful, tedious, jobs just the sake of "a hard day's work".
> 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.
I wish people would introspect more deeply instead of perpetuating toxic relationships with corporations; you're basically saying your most gratifying experience at work (where you are given a small slice of the net on your labor) was when you did something completely abstract and not when you got more money, more status, more whatever? Ok that's like saying my most gratifying experience at school was not when I graduated but when I had to sit in detention. Note I could've said "when I discovered XYZ mathematical principle" but I didn't because they're both equally as arbitrary in the overall scheme (learn skills and move into the workforce).
> are effectively money you can bank and that's the only thing that matters
We may have to agree to disagree here.
Not even just talking about the case where someone's worked in the tech industry long enough with a low enough expense lifestyle that money literally does not matter to them anymore...
A lot of people will work specific jobs not because they're trying to optimize for the most possible money.
> Not even just talking about the case where someone's worked in the tech industry long enough with a low enough expense lifestyle that money literally does not matter to them anymore...
This is the most out of touch (and also irrelevant) take you can have. I work in FAANG in the bay. The people around me are solid upper middle class but mortgages, day care, regular cars, medical bills, aging parents, college tuitions, etc etc etc mean very few of them can retire today and continue to live in the same place.
> A lot of people will work specific jobs not because they're trying to optimize for the most possible money.
Then you just work in a completely universe than I do because at every single job I've ever had, from lowly bus boy to FAANG ML engineer, not a single person has ever said to me "I'm doing this for the love of it". Quite the opposite in fact - many people I know would quit at the drop a hat if not for "golden handcuffs".
I'm doing this for the love of it. I never meant to make it a career, originally; I just spent so much time at it when I was young that it became a career, whether I liked it or not. I've never sought to maximize my compensation; I just need to get paid enough that I can comfortably keep doing the work, because the work is what I want to do.
Yes, I have a family and a mortgage and bills, blah blah blah. All this is adaptable.
Lest you simply dismiss me, I will say that I have worked at two FAANG companies and another tech giant which was larger than any of them; but my ambition is measured in terms of technical impact, not money.
> not a single person has ever said to me "I'm doing this for the love of it".
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!
congrats you're an extremely privileged and exceptional person. basketball players also generally love their jobs but they happen to be on average 6'7" so i'm not sure how either your experience theirs apply to me and the people i work with.
You’re getting awfully close to being rude. There’s no reason to try to go around imposing your perspective when it’s just you venting about feeling stuck. We all feel stuck from time to time, the solution is generally to wait it out until something that genuinely excites you comes along and you ask to hop on that opportunity. That’s possible in all work cultures, including egalitarian flat organizations.
> This is the most out of touch (and also irrelevant) take you can have. I work in FAANG in the bay. The people around me are solid upper middle class but mortgages, day care, regular cars, medical bills, aging parents, college tuitions, etc etc etc mean very few of them can retire today and continue to live in the same place.
I don't know the particulars of your budget, but up here in Seattle an FAANG E5/L5/etc makes over 3x median Seattle household income. And has medical insurance with like a <$10k OOP max. And can rent a house, and drive a $10k used car (like me) that gets replaced once every 10 years. Add public Uni tuition and $150k for 5 years of daycare (or have one working parent, see above r.e. 3x median income from one person), and say $30k/yr of elder parent support, and you can still run a 50%+ savings rate. That won't let you retire in 5 years, but it very likely will in 20 years.
I've met quite a few FAANG who've been at it long enough with a modest enough lifestyle that they don't need to work after 20 years. Some quit, some quit and moved to cheaper local, but some are still at it 'cus they like the problem solving.
I've also met several FAANG who bought a house worth 5x their income, are saving for $100k/yr of private Uni for 2-3 kids, drive $100k cars, etc, and save <10% of their income.
It's all tradeoffs.
And yea probably earning 3x median income makes someone out of touch to begin with. But what you do after that income is kinda up to you, and different choices yield different possibilities.
> Then you just work in a completely universe than I do because at every single job I've ever had, from lowly bus boy to FAANG ML engineer, not a single person has ever said to me "I'm doing this for the love of it". Quite the opposite in fact - many people I know would quit at the drop a hat if not for "golden handcuffs".
Well you can count me as one. I've met several others, and was on a team where most were like that for awhile.
I hope you’re not feeling superior to others because you’re able to have a “low expense lifestyle.” That tends to go right out the window if you have a spouse who doesn’t work in tech, and especially with children. Though I could just be a little biased because for a special needs child, basically take your expected ‘child expenses’ and square that number.
Note: all of the above was my own choice, so I can’t complain. I only just want to point out that you can really only keep a true low-expense lifestyle as a single person, or as a childless couple if both of you share that frugality passion.
You're coming at the employer relationship from a fundamentally different place than the parent comment you're responding to.
I'm assuming their age because of when Pivotal Labs was a thing, but there was a period from about the late 90s to the early 2010s where many people in the valley believed in an ideal of ascetic tech monks where we did this for the love of the work and not purely for status or money. It's not like those elements were ever wholly absent, but nominally egalitarian hierarchies weren't the weirdest things in hindsight.
> ascetic tech monks where we did this for the love of the work and not purely for status or money
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.
> Note I could've said "when I discovered XYZ mathematical principle" but I didn't because they're both equally as arbitrary
Wow. I cannot relate to someone who only (mostly) view's their own accomplishments as bargaining chips for money/prestige. Even accomplishments that could have widespread benefit to others.
But I accept productive people can operate in different ways.
> Even accomplishments that could have widespread benefit to others.
Which ones would those be? The ones where you optimized some process so your company could make 10MM more annually? I'm not a doctor/teacher/public defender. I write code that my company sells. I'm not benefitting anyone except myself and my company.
> I'm not benefitting anyone except myself and my company.
I don't know what you do, and all good work should be rewarded, but in most work third parties, such as customers or others benefit from work well done.
But I strongly share your opinion that good work should be matched with proportional compensation.
I had a similar problem. I was compensated well for what I could achieve, as a partner to a company, but after many good years, asymptotically prevented from achieving anything. The irony of being bought out of a contract for a price that reflected how much I could no longer achieve in those circumstances wasn't lost on me.
Sometimes I log into the root account to see the billing information.
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.
It was "fun" discovering this the hard way a number of years ago when active US Android user count for a game we were supporting dropped 15% essentially overnight. The TCP stack in the client only did IPv4.
The challenge, ironically, was convincing management that adding IPv6 was the thing worth trying. After almost a week of getting nowhere (and almost 2 weeks of outage), I forced the issue by saying "Look, I'm doing this. I need one engineer for 2 days. If it doesn't work, then it doesn't work."
He got the change implemented in 2 hours. QA OKed it the next day. The topic never came up again.
I have AT&T Fiber and it's been /64 since forever. I even called tech support who confirmed that they only provide /64 prefix length to home customers. How come did you manage to get a /56?
Sorry I confused prefix delegation with with having an allocation. I have multiple /64’s. It looks like with PD you can have up to 16 subnets, so equal to a /60.
A year ago I changed my CONTRIBUTING document to say that I don't accept pull-requests on my very modest open source project (a special purpose DNS server)
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 typically get a takedown notice a couple times a week, usually from my registrar (Namecheap) or from Netcraft, about 100 so far.
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.
Agreed. It takes more than a few developers to support older operating systems.
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.
> you can make a one-time donation of $5 to a charity of your choice ...
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.
Every SaaS platform with a reasonably cheap offering deals with these. I work for a recognizable SaaS and there are checks that flag both the accounts and reports the credit cards that are used after a fairly low threshold of "add payment method attempts". High levels of fraud usage hurt your reputation with payment processors and that's bad for business.
It doesn't stop the truly determined ones I'm sure, but it does mean that it adds complexity. You don't need to be impossible to test cards on, you just need to be harder to use than someone else (like a lower resource charity). We've even debated "fake accepting" some payment methods after we're confident it's someone trying to find working credit card numbers to add some false positives into the mix.
Definitely an issue. I don't really like the idea of long-term Patreon-eseque relationship between the individual user and the attestor/issuer site, but it could be done. The charitable giving is more of a means-to-and-end than a goal, functioning as a kind of "observed spending" which is harder to fake than, say, buying something from yourself on ebay.
If tokens had to mature for X days before being used that could deter laundering pretty handily, but stopping "tests" of cards would require hiding payment errors from the user for a certain period... which would not be a great experience.
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.