BetterDev

joined 2 years ago
[–] BetterDev@programming.dev 10 points 2 weeks ago (1 children)

C'mon. Live a little.

Just imagine needing to give a company-wide demo of a newly completed platform initiative, so you wanted to make sure your camera and mic were working, but you care about privacy so you want to do it locally.

You dont have an app for that, as this is a purpose-built, minimal, Arch Linux workstation, so you use pacman to install a local webcam GUI. While you're using pacman, you think, might as well update too.

Update, reboot, uh oh.

WHERE'S THE ARCHISO USB?!?!

You can't find it anywhere! And you even check that weird place you found it last time! Think! ... Your phone has a USB-C port and a terminal right? And right there is a USB-C Flash Drive... Surely you can just flash - Ah shit, not without rooting the phone!

Thinking quickly, you unscrew the back panel and replace the M.2 SSD with the one from your personal Librem 14 laptop [you care about privacy, remember?] that's currently out for repairs for the (now infamous) power issues. It's Arch too, but it hasn't been updated yet -- thank the good Dennis Ritchie, so you're able to boot with it and check the ArchWiki homepage...

Those dreaded words... MANUAL INTERVENTION NEEDED... Ugh! Why does this only happen when I need it not to!

You frantically download and flash the archiso to your available usb stick, swap ssds, boot up, decrypt the drive, mount it manually (remembering fondly the carefully chosen partition layout), chroot in, perform the "intervention", and reboot.

Perfection. Smooth as freshly polished glass. Smoother even -- probably -- with these sweet new updates! You log in, slide directly into the meeting, you were only 30 seconds late. You give the presentation expertly, they're all impressed by your fancy words like "kubernetes" and "admission controller". "What a genius" you know they're thinking. They have no idea.

You sign off, and wipe the cold sweat from your brow. These are the moments when you remember why you run Arch at work. Not because it's easy -- because it's hard. Because every time you're faced with a situation like this, you get a little bit better.

Sure, you could be an Ubuntu Urchin, a Debian Dweeb, a Mint Mistake, but you're not. You're better than them. You're an Arch Assassin, because you know the moment you lose your edge -- is the moment you lose your job.

You sit back and start your favorite database UI tool, DBeaver. It full screens instantly thanks to your tiling window manager. You love how it's always been reliable on Arch Linux. Why anyone would bother doing anything else is beyond you.

[–] BetterDev@programming.dev 27 points 1 month ago (3 children)

Um, actually it's pronounced png

[–] BetterDev@programming.dev 47 points 3 months ago (1 children)

Ummm...

I use Arch btw 🙃

[–] BetterDev@programming.dev 2 points 3 months ago

Punch the keys for god's sake!

[–] BetterDev@programming.dev 2 points 3 months ago

To me it reads like an AI generated article written to grab attention, and I spend a lot of time reading AI generated articles. Either the author has absolutely nailed the "sound like an AI" vibe, or very little effort was spent by an actual human to deliver this information.

[–] BetterDev@programming.dev 5 points 5 months ago

I've cracked this code (at least for me)

Use Hyper-V to create a workspace VM, using your favorite OS.

Keep all business related things on the host:

  • email
  • instant mesenger
  • meeting software
  • MDM
  • etc

Put all dev related thing in VM

  • docker
  • ide/text editor
  • dev tools

Set up "enhanced sessions" with

  • shared drives
  • clipboard integration
  • automatic monitor resizing

It isn't easy, and a lot of the sotware used for deep integration is archived but it still works. But since Hyper-V is integrated with the windows kernel, you can achieve near-metal performance with minimal tweaking.

Best part? New laptop? Just export the VM onto it, you lose nothing.

This even works in Windows 11.

I have played the cat and mouse game of Docker for windows and WSL and been dissapointed time and time again. No more.

Free yourself. Escape Windows development pain. Carve out a palace of your own design from within the jail provided you, and make it the best dev environment for you.

[–] BetterDev@programming.dev 13 points 9 months ago* (last edited 9 months ago) (3 children)

You understand Sway is a passion project, distributed with source for free, and Windows is a comercial product licensed to you by a multinational corperation, right?

[–] BetterDev@programming.dev 7 points 10 months ago

Dang bro, how much did you pay for it? I'd try to get my money back if I were you.

[–] BetterDev@programming.dev 1 points 1 year ago

And what I'm saying is it doesn't take more time to opt out in my experience. Its just as quick to get manually verified as to be biometrically scanned.

212
Lydia (programming.dev)
 
 

Get a wok. You can craft restaurant quality dishes in minutes. This little number was made from mostly leftovers, fed 3 people, and was downright delicious.

8
submitted 1 year ago* (last edited 1 year ago) by BetterDev@programming.dev to c/lemmybread@lemmy.world
 

I know, I know, I'm late to the sourdough game, but I've been thoroughly enjoying easy bread with commercial yeast, so I wanted to give sourdough a shot.

Followed the recipe from Joshua Wiessman's "Unapologetic Cookbook" (side note: great cookbook), twice, but I couldn't get the dough to turn out right. It always seemed overly hydrated and liquid.

I've been reading through this community, watching videos, and cooking easy bread long enough though that I finally threw up my hands and decided to have a go at it myself.

I started with about 10g of starter, added about 450g of bread flour, 1/4 cup of sugar (to increase rise), and a spoonful of salt. Then let that mix in the stand mixer till pretty homogeneous. Next I added 1.5 cups of 100°F water, and mixed in.

At this point it was still very liquidy, so I mixed in quite a bit more bread flour until it "looked right" with an appropriate amount of shaggyness.

I then let that rest for a while, and came back with the dough hook about every 30 minutes. At one point it still looked a bit too wet, so I added even more bread flour. I just worked this in with the hook.

After all my working I was worried about overdoing it, so I switched to stretch and folds, of which I did about 3 over the next several hours.

Finally I left it alone for about an hour, and when I returned, it was nice and risen.

I turned it out into my working space, added flour, cut and shaped, and placed into the floured bannetons. I let them rest in the bannetons for about an hour before I refrigerated them overnight.

I let them rest while the oven was heating this morning, and followed my normal baking routine, but I adjusted the temp up by about 50°, based on the Weissman recipe, which I feel was a mistake, so next time I'll just stick to 450°F.

The result was good. Though I can still taste sugar, so I'm going to cut it way down in the next batch. I'm also thinking I may not split into two loafs, and to bake at a lower temp next time.

All in all, I'd say this is my first successful attempt, and I'm excited for the next iteration. Any tips or sage wisdom from fellow bread people would be greatly appreciated!

view more: next ›