• 0 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Free: closed source, Dev can make it non-free any time they want, add monetization, ads, collect and sell data, change licensing, etc at any time and you just have to deal with it or switch software

    Foss/open source: if the Dev tries to monetize, add ads, go private, collect/sell data, people will just fork a non shitty version and maintain that



  • The religious marriage to rule them all: doom Emacs (or other packages that do similar things). All the excellent text editing of vi/vi/vi/vim, the ecosystem and all the features of emacs.

    For anyone who hasn’t heard of doom Emacs, it’s emacs with a lot of customizations baked into it, one of the biggest selling points is that everything uses vim keybinds now (where it makes sense). You get the amazing ecosystem of emacs with the ease of movement and editing of vim, plus a lot of other QOL features. It’s also just vanilla emacs with pre-made (and easy to edit) config files and helper functions so you can move over existing stuff if you want, and you don’t have to worry since all the emacs packages will still work, since it’s still emacs









  • I have a few hundred hours in terraria, but I’ve never really cared how my bases looked… Until I started playing again a few weeks ago. My normal world has each NPCs in living wood styled rooms with a painting each, but that was more because I was tired of digging. I’ll be making a permanent expert (or master) world and plan to make themed and nice rooms for each NPC since digging and materials won’t be an issue. My initial thoughts are a legit wizard tower for the wizard, a doomsday bunker for arms dealer and demo, living wood grove with active waterfall for dryad, fishing hut with pier for angler (going to actually do angler quests for the first time too), workshop for tinkerer steampunker cyborg and mechanic, and a cage surrounded by lava just above the underworld with the bare minimum metal furniture for the guide




  • It is - the bacteria and fungus grow extremely rapidly when it’s between refrigerator and cooking temperature, hence why you usually cook meat from refrigerator temp and don’t wait for it to get to room temp unless you need an excuse to get out of work for a very painful few days.

    Defrosting meat in room temp or hot water gets the outer layers to room temp or warmer much faster than cold water, and the outer sections immediately begin to grow bacteria/fungus extremely fast because of it. Cold water will slow that growth down long enough for the middle to defrost, but you need to keep changing the water or the bacteria will just keep growing faster and faster.

    Also, defrosting meat too fast or cooking it while frozen messes with the texture and flavor of it because the ice crystals haven’t had time to reintegrate into whatever is being cooked which is why you don’t cook stuff that is still frozen (not to mention it will cook extremely unevenly)


  • Cooking kills most bacteria - but not all, that’s how food poisoning still happens in cooked food (cross contamination too, but that’s a separate issue). You should never defrost meat at room temp, best way is in the fridge since it still keeps it at a temp that’s safe for a few days after being fully defrosted but it takes a day or two to fully defrost. To do it faster you can submerge it in cold water if you replace the water every couple of hours (or more often, depending on your room temp) until you cook it but that’s a last resort if you just need it defrosted in the same day




  • I don’t use readonly with dbeaver, but I do have the prod servers set to automatically make transactions and have to hit a button to commit. Almost certain it asks confirmation that I want to make the changes to prod which is nice too (I rarely have to touch our sql server prod)


  • finestnothing@lemmy.worldtoProgrammer Humor@lemmy.mlWhoops
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    8 months ago

    I’m a data engineer that occasionally has to work in sql server, I use dbeaver and have our prod servers default to auto-wrap in transactions and I have to push a button and confirm I know it’s prod before it commits changes there, it’s great and has saved me when I accidentally had a script switch servers. For the sandbox server I don’t have that on because the changes there don’t matter except for testing, and we can always remake the thing from scratch in a few hours. I haven’t had an oppsie yet and I hope to keep that streak