notme77

source ~/.bash_history

That’s because you’re already above where money would constrain you. The vast majority of people are not. I suspect you know this.

ok, but why?

Well then,

I can write a tiny C compiler in bash...

Found the PM

Boston has "Allston Christmas" on Sept 1st each year. Tons of people move. There's lots of nifty stuff on the sidewalks waiting to be discovered.

Perhaps people shouldn't have started paying nerds a good amount of money to do super nerdy things.

I've got discount pitchforks. Get your pitchforks. 3 for $5.

FreeNAS (open source, ZFS, requires ECC ram) Unraid (paid license for connivence that wraps open source mergerfs and snapraid) OpenMediaVault (open source unionfs + snapraid) Drobo (appliance) Synology (appliance)

There's a lot of near brain dead point and click options.

You've never been given a free meal?

Did you buy your copy of the book?

Ever been given a complimentary slide deck?

Ever had a publisher give you suggested questions for tests?

Ever seen a student have to use "online resources" that does the teaching and grading for the professor?

The publishers are doing professors jobs for them, and the students are paying for it. The bribe is you don't have to do your job.

I'd like to see more professional, terminal (doctorate) degrees that aren't PhDs. Run them in parallel. For instance, I feel there should be an M.Eng. equivalent for comp sci that requires mastery of existing theory instead of development of new theory.

The CEO is the CEO because he makes profitable decisions. You have to replace her with someone / something that makes at least equally good decisions.

Those same users are probably benefitting from the other thing I did that delivered value to my company. It has value for the company because it has value, directly or indirectly, for the customer. Eventually, it'll sort itself out with competition.

Ultimately, my work is dictated by what the customers whine about. If they make more noise over missing feature X than slow feature Y, X gets my time.

Hackathons happen on the weekend? Every company I've worked in has done them on weekdays. People tend to work longer on hackathon days than regular ones, but that doesn't seem so bad.

Most programmers probably enjoy what they do. To my mind, my employers aren't so much paying me be build stuff, I'd more or less do that anyway, they're paying me to choose what I build and to have control over the result.

If I work longer than a 7-8 hour day, 9 times out of 10, it's because I got wrapped up and lost in what I was doing.

Inflation moves money from the rich (who have assets) to the poor (who have debt). Can't have that...

It's targeting what is easiest to automate. This happens to be mostly low skilled workers.

Software engineers constantly cannibalize their own jobs, but there are so many positions for software engineers available (or potentially available) that we (software engineers) don't feel the affects.

Often people, especially computer engineers, focus on the machines. They think, "By doing this, the machine will run faster. By doing this, the machine will run more effectively. By doing this, the machine will something something something." They are focusing on machines. But in fact we need to focus on humans, on how humans care about doing programming or operating the application of the machines. We are the masters. They are the slaves. --Yukihiro Matsumoto

I'm very mean to my slaves. I have absolutely no issue leaving a rack of machines to slave away all weekend while I enjoy myself as opposed to spending that same weekend myself making it more efficient. (e.g. training models)

I don't care if a CPU is running at 80% consuming more electricity when I could work for a week and make it do the same job at idle. It's an inefficient use of my time. That same week's worth of effort could be spent delivering more value than the $10k server + $500/year operating cost. (I'm paid less than that, but I deliver more value to my company than my paycheck.) Also, risk. If it works now, it may not after I spend a week mucking with it.

That's a lot of parens you've got there. You should try emacs. :)

Want a dozen + 1?

As a friend, I setup a precision workstation for a small business owner. Part of this setup was a hardware raid 1 array. (He wanted a fast machine that was very reliable. His money, ¯\_(ツ)_/¯).

He took it to the Geek Squad to have a printer setup on it. These idiots destroyed the raid array while doing idk what complimentary scan or wtf ever. The friend had also stopped using the dropbox drive and used the regular user's folders to save stuff.

This did not end well. It was judged to be my fault for using poor quality hardware and software. He bought a gaming desktop from Best Buy. I learned a lesson.

Please google "Ashton Manual"

The process you're describing is well understood. What your folks are experiencing is extremely common. The Ashton Manual not only describes the process, but also details procedures for mitigating withdrawal-crash-relapse cycling.

I'm not a Doctor. The author has solid medical and research credentials along with decades of experience specifically treating and studying benzo addiction. The manual is published by a public research university and has withstood many years of scrutiny.