You are reading too much into the title.
2,755 karma · joined October 9, 2012
You are reading too much into the title.
I really do hope they aren't "keeping a file on" me but I think I would definitely believe it was true, if they said it was so. I guess I'm easily conned. Generally trust authority.
That's a mistake!
The reason for CI to communicate with production is to handle deployments, right? So take away that responsibility, and now you can safely isolate GitHub Server and shunt it into a network that only has access to outside artifacts that are necessary, push access to an image registry, and that's it.
Deployment status notifications can go from Flux to CI, so you can read about your deployments via commit status messages, but the communication is one-way. Changes are always pulled into the cluster and never pushed. You can set up webhooks in both directions, of course, for faster round trips (it makes a big difference for devs when iterating to not have to do a context switch and manually trigger a deploy, or to wait seconds not minutes and get immediate feedback after git push) but many will also opt not to do this in order to further confine and constrain to limit attack surfaces, it works just as well so long as they can live with some 5-10 minute waits for polling to do the job.
Edit: heaven forbid we have a conversation, Hacker News won't allow fast replies :D thanks for giving examples
You use a policy CRD called ImagePolicy to declare what versions should be matched and deployed automatically. You can have them deployed directly to production, or if it makes you more comfortable with your contractors, to an "auto-PR" branch which simply queues them up for a release engineer with the required juice to approve and merge the changes to prod.
There is no deploy job in CI, since the deployment in prod is whatever happens to be on the main branch in the config repo. This is a protected branch which only releng can merge changes into, usually only when the release checks are satisfied. Flux (which scans any image repos) updates those manifests when there is a release, either directly or via pull request.
This strategy I think would be able to address your Security concerns regarding contractors, by reducing the responsibility of your CI system to only CI, and not to handle CD anymore.
This is the subject of my talk at KubeCon[1], although you might not be able to get that from the title, (I'm presenting this topic for a Jenkins audience, but the focus is on Flux and how Flux works) so I'm hoping it should be applicable to a broader audience, certainly inclusive of GitHub users :)
[1]: https://kccncna2021.sched.com/event/lV0V/gitopsjenkins-ci-wi...
I don't know enough about lightning to dispute it, but it would seem these reports about Opennode and McDonalds are in conflict with those reports. Do you have any local color or stories to add? I'm interested in what they actually are technically doing, I didn't know that Lightning could be "partitioned" but my Technical Spanish is rusty.
Are there any controls that would prevent folks from using Chivo to spend their $30 literally anywhere they wanted, in as much as there is a Bitcoin receiving address for them? (If I opened it up to "all lightning-capable nodes" would that change the story? I understand little in spite of knowing lots about Bitcoin and friends, something something, needs to be a route/path from one node to another?)
Nobody is required to use Chivo, but people are required to accept legal tender. There's no reason to expect that Chivo-Chivo transfers will go to the trouble of opening individual lightning channels for each user, which costs non trivial amounts of money for each opened and closed channel.
It would make sense that users of the app can settle with each other and it doesn't so much as escape the four walls of a database at Chivo-HQ. But McDonalds is a multi-national enterprise and won't be trusting Chivo (or any El-Salvador official banking infra, I'd assume) to manage their wallets.
It is really cool to see a (hopefully) successful application of Lightning on Bitcoin in the wild, from a person who has been nay-saying about Lightning. I will be really glad to see it succeed. But I'm dubious about the success of this app.
One should hope the two successes are not tied to each other – it's encouraging that there are other companies. I have no way to judge Chivo and I've never used their software, but I have little trust of governments to implement complex systems well, and if there ever was a case study of a burgeoningly complex system, I think Lightning and Bitcoin is the big one.
https://www.bloomberg.com/news/articles/2021-08-23/coinbase-...
I don't know how you feel about short term treasury bonds, but I think they are nearly as good as cash. Slightly less liquid but with some return.
And you will generally have no idea whether people around you are vaccinated or not, unless you are in a University or somewhere that enforces vaccination, generally this is only if they are actually large enough to register on the local scale as "potential identified source of many new infections" and would want to stay out of the news in that way – ahem, I mean somewhere that is invested in keeping people safe.
I am planning some cross-country travel for a conference in October (really big one, you might have heard of it) and I am really having a hard time with it. I've mostly been isolated for the past year and a half. I am vaccinated and I would really like to see some people. But I do feel like a plague rat even making these plans.
Given the number of people around me (especially as you drive outside of the city parts of Indiana and into farm country) who wear their un-vaccinated status on their sleeve or bumper sticker, as a point of pride or honor, I wouldn't say we're not a threat. But still generally agree with the sentiment.
I have no idea why it would be to the advantage of a business like T-mobile to get you on a postpaid plan when there is no possibility of running up your bill. It's still the option they push on hardest when you walk up to the storefront.
The credit model is the default model. That was my point. I don't know that I had a point.
You shouldn't need to maintain a credit account just to keep a phone number, but I guess it's real estate and that's valuable, they will put it back into the pool if you ever stop paying the bill. I haven't had to deal with these kind of problems myself for a long time, but the pain is still fresh.
That being said, you are right, there are prepaid options and postpaid with a deposit ($50) that can put you outside of this SSN requirement on T-Mobile. I guess you have to know to ask for them. It is for credit, that's the only reason they can ask for your SSN.
Everything is credit based now, and for some people their phone bill might even be their first positive (or negative) mark on a credit score rating.
Stable coins with centralized generation are not interesting.
Well, those are two possibilities, but a third is that you don't need it because of one of several possible reasons.
The debt metaphor still fails to hold up; the nice thing about accepting "technical debt" into your project is that you may never come upon a time where it needs to be paid off at all. Not all tech debt must be paid off.
Usually only the highest priority tech debt can actually be paid down, and it doesn't always come with an interest cost. But when it starts to "come due," if you're an engineer in the hot seat, you can often (usually) tell pretty quickly just how much the "interest payment" actually affects your ability to deliver future iterations.
Your "customers" or stakeholders can tell too, indirectly, when your estimates start outpacing their "very reasonable expectations."
No single job that earns enough, I think is what you found; this doesn't preclude that dual-income families can afford to have three kids, with average or above-average income jobs.
I can imagine it would be very difficult to make ends meet in this situation as a single parent with 3 or more kids. (I suppose you would either need an exceptionally high paying job, or another major source of income besides that job.)
That is a shame, and given the extent to which most businesses and groups are built on Open Source, the fact that your situation is not in any way unique (to your employer or at large) is what makes it IMHO much worse.
I ran into technical limitations with my testing framework at one point where I realized that it was going to make my work 10x more complicated if I couldn't simply take some of the common libraries that I had factored out of my apps, and make them public.
You know what I'm saying, the CI machine can't run without a machine account if "bundle install" requires a valid SSH account. Getting the SSH account inside of a Docker container was an exercise of Rube Goldberg proportions, I eventually did it, but doubt strongly I would have ever been able to get anyone else to understand how or why that solution worked.
So I did the rational thing and published a few libraries to simplify the stack. 6 months later, we received a message from the head of InfoSec who was "very disappointed" after looking at our GitHub account.
Nobody competes with us. There was no risk of helping the competition. We're not in the business of software development (though we had an entire department of folks whose job title was Application Developer, so figure that one out...)
Their concern wasn't that it was against an NDA or that we hadn't gotten it approved, it was that threat-actors will take any signal they can about our internal stuff and turn it into an attack vector. Given what specifically it was that we had published, this was beyond irrational. I told them "it's 2020 and this is a backwards position to be holding in 2020." Shine a light, get more eyes on it.
There is no danger and I'm glad that someone looked at my code, I said, even if only for a few minutes – which I know would not have happened at all if we kept the repo internal.
Yeah, I don't work there anymore (not specifically because of this incident, but it was a contributing factor to me leaving voluntarily, without a doubt.)
And be prepared to wait 24 - 72 hours for final confirmation!
Whoa, hold on. Is that really true? I found this list of states which have banned asking for salary data as part of a job application, but are there states where you're required to share it with a company just because they've asked on the application and are requesting it for verification?
https://www.hrdive.com/news/salary-history-ban-states-list/5...
Which states?
If you have a good manager, you don't want them to be promoted because then it's a crap shoot whether you get another good one or not :) of course the pay raise is a compelling argument
I was only arguing against the idea that you can successfully keep your manager in the dark, you don't want that. You want a good manager who understands the problem domain well enough to anticipate these negative outcomes and who won't fixate on quarterly (or short-term) outcomes at the expense of long-term viability.
(A good manager also optimizes for your long-term success as well as their own!)
And it's not to say that optimizing for short-term goals is necessarily wrong every time. There's YAGNI – which is a perfectly reasonable argument to make at any time, but sometimes You Are Gonna Need It and there's an objective case in favor of not taking the shortcut because it will cost you in easily predictable ways.
I have never given an estimate that was not later called into question and asked to be reduced. Usually much sooner in fact.
In many cases, asking for an estimate is fishing for a way to make the problem easier to solve. But they don't really want to make the problem easier to solve, they just want to get it done quicker (with no regard for whether or not it makes the next problem harder to get this problem done the quicker way.)
Really nobody is thinking this hard about it though, it's basically the "quarterly earnings report" problem. If we don't look good this quarter, then there's not much hope for next quarter, since we already told the boss this one would be done this quarter, and have started talking about what they'll want next quarter, though we're not ready to talk with you about that because they could change their mind at any time, so "93 days" sounds absolutely perfect, as you'll be ready for more soul crushing just in time for next quarter.
Happy hour here is just when you can get a $2 cheeseburger, or $0.50 wings on special. I had never even considered something like a happy hour being reflected on your insurance premium.
These are logically not the same structure of argument. I'm not making any character judgements about people involved in this discussion, or on the LKML either for that matter.
Thanks for the perspective. That makes sense, I wrote how they don't really like Ruby even though it is very stable like they said they wanted, and rarely makes breaking changes (and takes great care to ensure they are well documented and easy to follow when they happen) ...
Then I thought about Rails, and decided not to say anything about Rails, (because it might undermine my whole argument, as that's where arguing from this position breaks down a bit.) Rails isn't really that bad with breaking changes, but it is where most of the breaking changes probably come from, and therefore probably worst thing to use as an example... like you say with Kubernetes in Go!
People and organizations decide when they will move versions based on their own project lifecycles and requirements, usually (outside of the Go community?) not just because the language vendor says there is a new version and it's time. This is something that was hard for me to cope with as a Rubyist, who was always doing everything to be on the latest version.
I'm new to the Go community, but I can already see the effects of this in Kubernetes, and I don't necessarily think it's good the way things are. Kubernetes 1.16 was released in 9/19 and already EOL and out of support in 8/20, less than a year later. (It took some time for many cloud vendors like AWS to catch up, EKS only landed K8s 1.16 in April 2020. That's four months of usable life before it was officially out of date.)
Integrated things that worked in August of 2019, probably need work again in 2021. As a software developer I understand this and "yeah, we need to always be upgrading" is part of my mantra, and it has been clear to me since I was a teenager that I will spend time struggling with problems that I would not even know about, unless I run Debian "unstable" or an equivalent rolling release distro, where patches can be accepted from upstream at any time of year, whether or not they contain new features.
But I could never get my bosses to see it this way, working in a company that was not firmly embanked inside of the "Cloud-Native" sphere of the world. The "normies" I've always worked with didn't want to see new features popping in at any time, they wanted their own predictable environment that works the same as it did yesterday, to stay that way all year long.
(Edit: and for what it's worth, Ruby does a pretty good job of being stable all the time I've used it professionally for the last 8-10 years, and in spite of having chosen it themselves, they still hate it. Anyway, that's what they say they want...)
Then I remembered, we all work remotely, and got a good laugh out of it, since this can never happen. (Even if I do stink!)
It was $5 iirc. I got more than what I paid for out of it. No hard feelings to those that I'm sure worked hard and put a lot of effort in on Synergy 2 once long ago. It wasn't meant to be. It won't be released in 2022 or 2023 either LOL, not in any kind of shape that you want to use, (or I'll gladly eat my own shoe leather in atonement for my heavy but informed skepticism.)
(Seriously though, I hope it will get accepted and if so come to my talk on this at Kubecon?)