555 karma · joined June 28, 2019
Sounds more like a knock on the person making the comment than it is on me.
That way, I don't care if your branch contains 100 commits or 1 commit. I don't need to worry about commit messages like:
- fix 1
- fix 2
- dfljfdlkfdj
- does it work now?
Do whatever you want with your commits on your feature branch. Just make sure the title of your PR is clean and follows our formatting. Git history is always well formatted and linear.
It's the ideal solution.
Use k9s for example. Let's say you want to determine where the value of an environment variable is coming from.
1. 'kubectl get deploy -n example' (find the name of the deployment in question)
2. 'kubectl describe deploy example-app -n example' (determine where the value for the env var is coming from)
3. 'kubectl get cm example-app-config -n example -o yaml' (check the value of the referenced key in the config map)
This is a very basic example but you can see where it lead to slow debugging that is made even slower by its propensity to typos and the need to look up command syntax. Once you get comfy in a well designed TUI, you can fly through this process in 10 seconds.
"If one thing I need is going to be down, everything might as well be down."
If I have a product with 5 dependencies and one of them is down, there's things I can do to partially mitigate. A circuit breaker would allow my thing to at least stay up and responsive. Maybe I could get a status message up and turn off a feature flag to disable what calls that dependency.
On the other hand, if all my dependencies are down AND the management layer is down AND the AWS portal is not functioning correctly, I'm pretty much SOL.
Massive centralization is never, ever a good thing for anyone other than the ones who are doing the centralizing.
There's no doubt a VM in AWS is exponentially more redundant than my VM running on a couple of Intel NUCs in my closet.
The difference is, when I have a major outage, my blog goes down.
When EC2 has a major outage, all of the blogs go down. Along with Wikipedia, Starbucks, and half the internet.
That single point of failure is the issue.
Working with ADO pipelines is painful.
- Make change locally
- Push change
- Run pipeline
- Wait forever because ADO is slow
- Debug the error caused by some syntax issue in their bastardized version of yaml
- Repeat
Here's some fun examples to see why HCL sucks:
- Create an if/elseif/else statement
- Do anything remotely complex with a for loop (tip: you're probably going to have to use `flatten` a lot)
Look at the first sentence of the first paragraph and the first sentence in the second paragraph. Two grammar errors which are a dead giveaway it's fraudulent.
> Thank you for your assistance and understanding during your recent support call, regarding a ficticious request aimed at accessing your Google account.
Comma doesn't belong there and "fictitious" is misspelled.
> To follow all guidelines of the internal review properly. Please keep a secure note with the temporary password which your support representative has provided to you.
Out of place period. Should be a comma.
Legit, canned emails like this (especially from legal@google.com) would be proofread much better than this. It's fake.
I think there's more than one way to achieve that. It doesn't have to be bans or subsidies. A lot of it has to do with education and competition. Unfortunately, they are kind of a circular dependency.
- There's so much cheap, highly processed food out there. The companies pay for prime real estate on the shelves and expensive marketing. It is chemically engineered to exploit your pleasure senses when you eat it. That is a hard beast to fight without proper education. And not just the food pyramid, but in depth explanations on why you should avoid it and what to eat instead. There are large groups of the population that have no idea that pop tart or cereal are not a healthy breakfast option.
- If there were more companies creating and promoting healthy, less-processed food options, the price would naturally comedown due to competition. But without the education, these products just do not sell as well. If I gave you some natural peanut butter or almond butter (just almonds or peanuts - 1 ingredient) and I gave you a jar of a more common peanut butter like JIF (sugar + hydrogenated oil for better consistency) and you had no other information at all, you're choosing JIF 10 out of 10 times. It's cheaper, it taste better, and you don't have to stir it. These megacorps prey on that lack of knowledge.
More education -> make better choices when buying -> more companies selling those choices -> cheaper prices on those choices.
The obesity trend has happened almost in lockstep with the proliferation of highly processed foods. Butter and animal fats being replaced with low quality, hydrogenated vegetable oils. Cane sugar being replaced with high fructose corn syrup and other highly processed sweeteners. Sodas and sugary juices replacing water. Food like substances with little to no nutritional value designed solely for taste and texture.
These things are calorically dense while containing nothing the body needs to thrive (though the calories will allow it to survive). They are easy to eat in large amounts and leave you feeling hungry. And unfortunately, these are the most affordable and readily available foods in the United States.
I don't think this is a conspiracy. It's just capitalism. These low quality ingredients are cheap and extremely shelf stable. In addition, the government subsidizes the production of this garbage.
So to say obesity has persisted through everything we've tried is a bit backwards. It would be more accurate to say "a percentage of the population has managed to avoid obesity despite all of the things we've tried."
- Make healthier food options more affordable and readily available - Better nutrition education - And if you really want to get the government involved, ban the use of some additives, oils, sweeteners, and dyes that allow the creation of many of these highly processed foods
For example, some podcasts I don't want to miss an episode and I want them all downloaded. Other podcasts I only check in on occasionally and would only want the latest episode to be kept on device.
I subscribe to a lot of podcast and downloading and keeping every episode is going to eat up a lot of storage.
Besides that, love the simplicity of it. Well done!
The shame is because I know others would love to be in my position and there is an almost endless list of jobs that are worse than this, but it's brutal sometimes. I workout daily and spend the vast majority of my time away from the keyboard, outside.
The worst part is, it's not just a matter of embrace the suck and push on. In a physical labor job, you can just command the body to move and push through it. In this line of work, you don't really have that option. You can't just command the brain to solve difficult problems and design complex systems.
If you go that route, you can use my referral code REFOUSPW7TK for 10% off. Totally optional.
Side note: why do these open source alternatives always have such terrible names?