The real world case I remember also included a TODO to return and fix the code later. In a published scientific software. I wonder how many paper were messed up by this buggy software. As I looked at the code due to the amount of bugs I encountered.

It’s been many years from publication, and to the surprise of no one, they did not return to fix it.

// This line does nothing, however removing it causes production to crash. DO NOT REMOVE

Killed by the department of efficiency

Will all the needed binary blobs survive a kernel update? Cus that’s a blocker for both long term and distro wide support.

Forgejo is very much fun

I managed to donate a few patches over the years. But the whole ceremony with a PR around a fix is just too much. It takes more time than I have free.

I have a minor error fix sitting on my computer for over month now. No time to get it merged.

Most of it revolves around how bad the housing situation is.

Partial documentation combined with complex code will be great for your bank account.

Code fast, and badly, always under promise and over deliver. Before the shit hits the fan, move to another place.

Next person after you will take the blame. You may be hired again at premium as you can deliver. Blame the replacement Dev for breaking the code and causing a lot of damage.

Fix the little that is possible, at premium rate and move on.

After the shit they pulled with the Nokia 9 PureView, how can someone bet money on their crap?

The newly freed 40+GB are a nice bonus.

You are confusing Nix with Debian.

I don’t see a reduced number of CS students that enjoy poking around. I see an increase in the number of students that are there only for the good salary. Making the poking type into a smaller percentage.

Following the flow chart I came to the conclusion that plastic dinosaurs are real dinosaurs.

Simple text editor. To create failing test by hand, closing in on a bug in the code.

Now run a VM from Google Cloud on a system booted from Google Cloud.

Bioinformatics isn’t used only for medical research or within big companies. Sub-topics like metagenomics, that are helpful in many areas of research, require high level of technical knowledge, that the life science people don’t have.

You can work in bioinformatics, the pay is lower than FAANG, but your code will benefit society.

They are not limiting their foot print to 1/4 acre. They are using bikes, using glass and forge the forest.

It’s like offloading your aluminum production to another country and claiming you are living 100% on renewable.

Importance of order changes by field. In my field, at least for in lab work: first is the main lab person that worked on the project. Last is the PI, everyone that helped goes in the sandwich. I’m unsure about collaborations between labs and at that point too afraid to ask.

This is brilliant

A folding solar panel to charge electronics using USB.

A small radio+torch+USB port that can be charged with a spinner and a solar panel.