yoyar

Windows itself is malware.

Planke plastics

I struggled with weight for decades but this last year I've lost 60+ pounds, and I will lose more. All the weird tips in the world won't help IMO. I used an app that worked for me finally. It worked because I was able to get the education, and mindset / motivation I needed. Little tips and tricks won't work, you need a comprehensive solution that works for you. I'm not shilling for some company, this was the only thing that has worked consistently for me after decades of trying. Anyway, at the risk of sounding like an advert which this is not, it was noom. It takes a lot of work and persistence but having the reasons and knowledge to make it all come together and be consistent is what is key.

That’s too bad. That helps me understand why it isn’t favoured as much as I would think/like.

Anytime I learn a new language (I regularly write code in several) I start asking how is testing done, where are the libraries, where is this, and how do I do that? I already have all of that and more at my fingertips. Also, Groovy is vastly underrated. It’s the most economical and easiest to understand language I know meaning I can do more with less code and faster in general.

Every complaint I’ve ever seen about OOP (and other tools) amounts to “we misused and abused the tool/language/whatever so therefore the tool itself is bad “

Inflation of the money supply leads to prices that end up higher than they otherwise would have been.

This does not necessarily mean nominally higher prices.

This is a distinction that leads people to say things like: Obama did it and prices didn't go up. With the implication that it might be ok to inflate to infinity.

Agreed. No one knows.

I think the causal nature of this relationship is way overestimated.

Not building garbage software in the first place is an option

The point here for me is team dynamics, maturity, and skill level.

If you have a team that can't competently write and maintain a monolith that is modular and built/tested via automation, then that team has no business trying to build and maintain microservices.

No single person understands everything about how a pencil is made.

I use the rule that if something is non-obvious I write comments in the code with references to how I solved the problem.

It was alluded to in the list but I like this great quote:

"the best way to deal with complexity is to remove it"