Hops isn't only for beer. You can dry them and make it into a tea to help you go to sleep.
CubitOom
joined 2 years ago
Honestly. It's about more than money.
If your boss says you must return to the office, after 3 years of WFH. At best, it shows that they do not value or respect you, and are just making an arbitrary decision in a bid to sell more stocks.
At worst, there might be some insidious reason to make employees physically available. Maybe they are getting a kickback somehow, or selling data that they can only get when you are there, or maybe they are just horny and want to seduce you sexually.
A remote worker is often happier, more productive, and cost less to employ even if they are paid the same as an on-site worker. Offices do not have to provide parking, seating, HVAC, power, wifi, and will even have less physical security vectors.
If some people prefer to go into an office, then it should be optional. Not a hybrid model where they force you to come a certain number of days a week.
At the end of the day unless you are on some kind of probation or evaluation period WFH should be the default when ever possible.
Seagulls...stop it now.
I second this.
About 6 years ago I had to make 20 upper mid teir pcs for a client's art department. I normally build my own but 20 seemed like a lot to do at once so I outsourced it to a company called Xidax.
I could pick the parts that met my spec and perhaps because it was a larger order I was able to get some parts they didn't have on their website after calling and asking. But most importantly it wasn't too much more expensive than a big box store pre-built but with quality parts, not just economy parts you might normally find in a lot of prebiilts. (PSUs and drives are important not to skimp on, especially in enterprise environments.)
I would say, building your own is better. Both from a cost and learning perspective. It's a lot easier then it seems, I know it's intimidating. But if your uncomfortable building your own. Go with a company you can pick name brand quality parts from that will last.
Also, I would avoid water cooling unless your workload demands it. Water cooling is honestly not worth it.
PS if you plan to upgrade it yourself. A case can either be very important or something you replace easily. The better your case is to build in, the longer you might keep it. Case in point. My fractal design silent case is the oldest PC part I have (at least 10 years old) and it's probably never going to need a upgrade.
Why are we even using nsfw tags? There should just be separate porn, gore, etcs tags. I think the lack of tags is the issue here.
Obviously the list of tags needs to be finite so that app settings are sane but there should be more than one explicit content tag and it honestly shouldn't need to reference work.
Grave of the Fireflies...but make sure to watch My Neighbor Totoro right after as intended
Tutanota has been great.
Cherry hills sushi Co is great but might be a bit over of your price point.
Kikis japanese casual dining is also great, it's cheaper and has other things besides just sushi but admittedly I don't know if the have rolls. It is a pretty authentic place however.
There is a learning curve, but emacs org-mode sounds exactly like what you want.
With org-mode you can have your docs and your code in the same place or use your docs to create and link to different files.
You can even run your code inside your docs and have it execute on a networked computer without ever leaving your doc.
https://www.youtube.com/watch?v=34zODp_lhqg
And with org-roam, you can keep the same functionality you are used to with obsidian.
Emacs is a bit of a rabbit hole however. So if you want to keep things simple you could just use git.
Git has its own learning curve but it's pretty much a requirement everywhere code is developed and released professionally so it's a good idea to have some experience with it.
I'd suggest having different repos for your different projects, and either one single readme.md file in each repo for all your docs or using the wiki feature that is built into most free git web UIs like GitHub and gitlab.
Once on git, it's trivial to link to specific files or even individual lines in your repo.
I'm really happy with tutanota
One of the best qualities of Arch and other Arch based distros, the ability to use the archwiki.
It can be helpful when using other distros too but on Arch it's exactly the docs your supposed to use.
https://wiki.archlinux.org/title/Anbox
From that wiki it says: Note: As of February 2023, Anbox is no longer actively developed. The developer recommended Waydroid as an alternative.