But only some distros should be used !

It’s like an uncanny valley , so close to reality but different enough to elicit feelings

I don’t have numbers in front of me, but I think only a slim minority of contributors make money off their work. And those that do make money often can only do so because of the earlier, unpaid, work by others which caused the projects to be valued and widely used

What’s stopping a sustained, constructive public inquiry into these parallels between past cover-ups and current information control?

There is no mechanism to promote the investigation. At best there will be queries like you made for the general, and social media reactions to specific events as they unfold.

A large chunk of government, politics, and press in the USA no longer exists. There are no authorities to turn too, now or later, regardless who gains power in Washington.

Most of the Anglosphere outside the USA is in a free fall too, a few years behind, maybe 20 years.

It gives one month of bad luck for each time used. If the power is activated to help others without benefit for yourself, then it’s sloppy good luck instead. You are fortunate in a tragic way.

The timer and type is reset each time power manifested

The open source developers should unionize against the large corporations not paying them. A virtual picket line, and collective bargaining

Super strength

New computer scent

I make little typing motions with my fingers

Sometimes I only walk around, other times I do more like run

I’m still trying to reach my potential two hours of workout daily, only doing one hour of things that makes me sweat.

I have alarms on my phone set every three hours to remind me to stop and do something

I find a variety of activities help distribute the loads

I often push my older body when it’s not used to work. This means I pull a muscle once every few weeks, often in my upper body; or demand too much in my knees.

Fortunately I can heal in a week or two, but I definitely am slow to heal compared to before.

I always say a little prayer before I do that command

Basically this. Most people are decent enough, that is they are not trying to burn down the world. Many, including me, have unclear ideas about what is happening. Often, people use opposing words and history to really mean the same goals.

But it’s exhausting figuring it out for more than friends and people in my echo groups. So I don’t usually try. They have to be worth it to me.

That said, this is for the mental stuff. When it comes to political actions that need to be done now, and cannot wait, things are different. There is a time crunch then. And it’s not about tolerance , but results.

TIL Nintendo will perhaps give money, to the American administration, for unknown reasons

If it is stupid and it works it’s not stupid.

I’m going to use it

When I graduated with my bs in programming I thought I had at least a little knowledge of most programming

Years later, I can safely say I know very little, maybe aware of 1% or 2% of just the names of the major parts of tech in programming . Details even less.

And I read a lot

Dev mode is when developing by the programmers. Production means used by others.

When I am working with a service, I want to know immediately when there is a problem.

When I push my code to be used, the dev flag is off and the code does stuff as normal.

For example: if I am making a payment service using a third party, I use sandbox and fake cc numbers. I want things to fail loudly on my computer so I can make things fail silently. And safely, when it’s used with real money. But I can only do that if I know there are issues. And only logging lets some bugs be unnoticed , particularly if a cluttered log. So being loud in development saves tears in production

All good points!

Also, I’ve learned from others that how you crash depends on the environment, if running in dev, be different than if the thing is used by the public or in production.

• In a script, dump too much data if dev, in production keep it terse but have relevant info and a link to the docs.
• In a gui, webpage or app make the crash screen in dev be a thing of beauty that has the full stack trace, database info , and more. But in production only generate a polite message that is vague, with an error code. Push that error to a logging service with the code. And if this is not used by the public but by a company that paid for it, have a feedback button or live chat button, in the error message, to talk with tech support.
• Backend services and libraries: if in dev mode crashes should be loud and definitely break things, while in production log silently and keep working.
• And for any type of program: always back up data, and always use transactions to not have the database or files be in an incomplete state if an exception happens.

formatting edit

I use the catastrophe theory of error handling: if something fails sanity checks or throws an exception, then kill it with fire: crash the whole program and make the users cry.

True, it’s a pain but… no more hidden errors that get reported two years later