dukk @ dukk @programming.dev

Posts

6

Comments

260

Joined

2 yr. ago

Yeah, I’d imagine you’d want to adapt for different locales. Here in the US, MMDDYY is pretty ubiquitous, but I’m sure it’s different in other countries.

I’m guessing the UI designer accidentally put in DD/MM/YY, when the code handles the date as MM/DD/YY.

Remember kids, always use protected branches.

Maybe I’m the minority, but I’ve never really broken my Linux. Sure, it’s NixOS, so it’s a little more stable than many other distros, but still, I have a much better time with it than I do with Windows

IMO for AI to reach a useful point it needs to be able to learn. Now I’m no expert on neural networks, but if it can’t learn anything new once it’s been trained, it’s never really going to reach its true potential. It can imitate a human, but that’s about it. Once AI can really learn, it’ll become an order of magnitude more useful. Don’t get me wrong: all this AI work is a step in the right direction, but we’ll only be able to go so far with pre-trained models.

Public transport.

I swear, I saw a video on this…

The whole thing would just be relative to the portal, though. Relative to the portal, they come in fast and out fast.

However, the portal is moving. So if we look at this relative to the portal, they would moving into the portal. I imagine they would get shot out along with the rails. Of course, they’ll eventually plop back down, so it really could be A if the trolley was moving quite slow.

So they agree that water is wet?

As OP stated, it’s still there, just barely visible. ¯(ツ)_/¯

This post isn’t on Lemmy.world.

Yeah, that is true. Proprietary software can be difficult with Nix sometimes.

You can get merge conflicts in cherry picks too, it’s the same process.

This is the way! Small commits with descriptive commit names, then just fixup into a few feature commits. Makes rebase a breeze.

Yeah, I am. However GitHub, being the biggest Git hosting provider and all that, makes you use merge commits. FF-merges must be done manually from the command line. While this definitely isn’t a problem for me, many people out there just don’t care and merge without a second thought (which, as I said in my comment, results in having to create a new branch and cherry picking the commits onto there).

Alpine Linux: what’s up, guys?

Merge commits suck.

My biggest issue with GitHub is that it always squashes and merges. It’s really annoying as it not only takes away from commit history, but it also puts the fork out of sync with the main branch, and I’ll often realize this after having implemented another features, forcing me end up cherry picking just to fix it. Luckily LazyGit makes this process pretty painless, but still.

Seriously people, use FF-merge where you can.

Then again, if my feature branch has simply gone behind upstream, I usually pull and rebase. If you’ve got good commits, it’s a really simple process and saves me a lot of future headaches.

There’s obviously places not to use rebase(like when multiple people are working on a branch), but I consider it good practice to always rebase before merge. This way, we can always just FF-merge and avoid screwing with the Git history. We do this at my company and honestly, as long as you follow good practices, it should never really get too out of hand.

Yeah, snaps are truly bloat. I always stayed away from Ubuntu, mainly because of Canonical. Debian is amazing stability wise. Definitely a good choice. I like to live a little more on the edge though, so I use NixOS (it’s great, I can update without ever worrying about breaking my system).

What if your dev experience was entirely in the cloud?

No. Just no.

Fuck no.