TunaLobster

Lol I looked up in Google maps my public transit options to get to work. I gave me Lyft. I live in a major metropolitan area. The problem is that the suburbs all think they can go it alone on transit and then wonder why people don't use it and then cut service. It's been 30+ years of trying to coordinate a system for the entire area. It ain't happening soon.

Yep. Lots of kip feet numbers in engineering. Moments are everywhere and they usually dominate.

I keep a set of notes for each day. I have 2 journals. One for work and one for the rest of life. I use the same system in both. I took the Bullet Journal system of notation and added a few more to handle some edge cases that I encounter occasionally. The system works with any size of journal or pad of paper. I often drop sketches and diagrams in the middle of meeting notes. Actions get carried from day to day. Walk up requests get written down. I know when something was handed off to someone else. I like it! Totally not for everyone though. I skip the monthly and future planning parts. I would probably use that part if I was doing schedule management. Rapid logging is the part that I use all the freaking time.

https://www.tinyrayofsunshine.com/blog/bullet-journal-guide

Notes for small code projects/my network set up get tossed into .txt files. Eh. It gets the job done and there is only one place that file can be and it is the most up to date. Assuming I updated after the last changes. Which is a coin toss when things are busy. Comments in the code are a far more common way for me to keep track of what is happening.

I think the other aspect is the easy to follow discussion threads. IMO it's the cleanest way to show and follow branching discussions.

HAHAHAHA 😂😂 None of those are Ukraine.

Proxmox can be a bit of a bear to setup. The documentation is not very approachable for new users. It uses a lot of terms without definition which is a deadly sin of technical writing IMO. Guides for getting an Ubuntu Server VM setup vary wildly and often recommend outdated settings.

I'm totally on board with using it though. It eliminates the need to start from scratch when migrating to newer hardware.

Set up your favorite Linux server distro and then go ham on setting up docker (dockge is a great tool to introduce compose).

Just having something that shows the field options and formats it correctly would be fantastic. Tooltips and all that could be added later to lower the bar of entry for new users.

You're completely overthinking it. I keep white separate. Colors get their own basket. Denim goes in a separate piles after it really smells (it honestly shouldn't be washed very much). Towels get their own load due to shedding. Sheets sometimes go in with the colors.

I do everything on cold. I use the plainest of plain detergent. If there's a smell in polyester or nylon clothes I'll put in some Clorox 2.

Dryer on low or medium until mostly dry. I've got a fancy one with a moisture sensor that actually works so I let that determine how long. Usually 25-30 minutes.

Citation: https://www.nytimes.com/wirecutter/reviews/wirecutter-show-podcast-20240821-better-laundry-secret/

Assuming your mean in the US. Depends on the state.

Also writing down a process that has many parties working in tandem so that everyone is aware of who they receive something from and who they give that something to. Not micromanaging. Just keeping things flowing!

That's not the correct link.

https://www.androidauthority.com/google-pixel-7a-problems-fixes-3333284/

It's not even that great of an article. Those problems are generic for many different phones. Adding a few of the phones specs to some sentences doesn't make the content specific to a 7a. Needlessly limiting the audience. Is AA is going to start blasting these kinds of form fill articles for every phone out there for targeted advertising? That's what this reads as.

That's what the people living in Dallas said. Then a tornado hit the middle of a dense neighborhood.