This guy should get his thyroid checked.
2,293 karma · joined September 26, 2021
This guy should get his thyroid checked.
For example, AWS us-east-1 outages have caused global outages on multiple occasions, such as https://www.networkworld.com/article/4168878/aws-hit-by-us-e...
How would it help society?
It achieved wage suppression and control over workers livelihood.
And it should be illegal, perhaps even criminal the way some companies go about it.
StackOverflow was always just an "answer machine".
They wanted it to be a community, but it never was.
I tried to describe it to my doctor and he seemed like he never heard of it before and sort of look at me like I was crazy, or at least that is what I sensed. But I ended up researching online and found it was a thing that happens.
"God, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference."
I don't know about other people, but for me, if I'm using my earbuds it is because someone around me is being distracting and/or annoying.
I usually prefer silence for work, but often that isn't an option.
I wonder if this could be related to these recent privacy related changes.
https://github.blog/news-insights/company-news/updates-to-gi...
(Edit: I meant to say PR, not issue...)
And even if I am just using Excel, my work still deserves to be respected by the operating system.
Why not solve the real problem instead of putting in a janky workaround?
At risk of being cliche, it seems like you guys could benefit from the 5 Whys approach here: "Why is loading a cross repo issue slow?" and iterate until you discover the root cause, and fix that.
I suspect fixing the root cause is going to be a lot less glorious career-wise than implementing a UX change that is easier to tout at review time (well maybe not so much after this debacle).
I do it all the time, whenever there are competing libraries to choose among.
It's a heuristic that saves me time.
If one library has 1,000 stars and the other has 15, I'm going to default to the 1,000 stars.
I also look at download count and release frequency. Basically I don't want to use some obscure dependency for something critical.
All joking aside, it really is a chronic problem in the corporate world. Most codebases I encounter just have "changed stuff" or "hope this works now".
It's a small minority of developers (myself included) who consider the git commit log to be important enough to spend time writing something meaningful.
AI generated commit messages helps this a lot, if developers would actually use it (I hope they will).
For most of us, taking calculated risks is better than simply taking more risks.
And the risk calculation changes based on your personal circumstances: physically falling has a greater impact on an old person than a young person, making a financial mistake has a greater impact on someone who has no savings than someone who is wealthy, etc.
So "let yourself fall down more" isn't really one size fits all advice.
Care to elaborate?
I also knew people who had MUD addictions.
These were very similar to how in later years people became addicted to Second Life or EverQuest and essentially dropped out of society.
I don't know if there is a modern-day equivalent, to be honest.
I also personally witnessed multiple friends who dropped out of college due to IRC addiction in the early 1990s.
I am curious if anyone else has a similar memory of IRC.
I just disable all notifications and it doesn't bother me to have LinkedIn because I only open it when I feel like it. Same with Facebook, etc.
Incredibly, the default is always for notifications to be enabled, and I don't know how people live like that.
Yes.
I have no involvement in this drama (it's the first I've heard of it actually), but signing your name to something matters.
Choose carefully what/who you support.
A repo owner is not obligated to accept contributions.
All of those people are free to create their own repo, post on social media, or write an article recanting their support if they choose to do so.
Is there someplace I can find information about how section 174 aligns with the frequency and size of layoffs?
"Security through obscurity" isn't really good enough.