It was great to reclaim that barely used 1tb nvme.
It was great to reclaim that barely used 1tb nvme.
No, it potentially impacts cpu power profile (if it’s toggling between AC and DC because of a loose connection)
This would adjust throttling of the cpu, which could impact playback in certain cases, so it’s possible. Likely other apps would be affected but OP was probably most often watching videos while plugged so noticed mostly there 🤷
404 Ethics not found. Go be evil elsewhere.
Has a nice ring to it. Though google deserves their own special fuck-you http status. Maybe we can crack the 600s
Not just wanted to make, the original article implied existence of a prototype. That’s “putting into effect a plan” which, for fans of causality, implies a pre-existing plan.
Bun is used by us in production, in dev, everywhere. It’s great. We don’t even use (p)npm to build js packages on our docker images for apps anymore.
Fair point but no one wants to deal with my incessant whining, and you couldn’t pay me enough to deal with it. Sometimes a scratching post is what the cat needs.
This is about that Twitter website people used to use right? Sorry, out of the loop here.
I utterly detest the use of “wholeheartedly agree” when people have caveats. It truly goes against the concept of wholeheartedness. It is sufficient to indicate that you agree completely and then be silent. That you don’t suggests your caveat has more value and meaning to you than the point you are ‘wholeheartedly’ agreeing with.
You are either being willfully obtuse or are actively a troll. Either way, we’ve all already used up more metabolism on you than is worthwhile. If you cannot bother to be informed about something as easy to know as this, and yet spout off multiple replies to defend your position, then you’re not here in good faith.
asking questions
Yeah thanks there Tucker Carlson.
Ketamine is a hell of a drug yo.
Yes, that is another benefit, once you start getting muscle memory with the library. You start to parcel things by context a bit more. It’s upped my habit of discrete commit-by-hunks, which also serves as a nice self-review of the work.
👏 Super duper this is the way. No notes!
Quasi parallel reply to your other post, this would kind of echo the want for a capital letter at the start of the commit message. Icon indicates overall topic nature of commits.
Lets say I am adding a database migration and my commit is the migration file and the schema. My commit message might be:
🗃️ Add notes to Users table
So anyone looking at the eventual pr will see the icon and know that this bunch of work will affect db without all that tedious “reading the code” part of the review, or for team members who didn’t participate in reviews.
I was initially hesitant to adopt it but I have very reasonable, younger team mates for whom emojis are part of the standard vocabulary. I gradually came to appreciate and value the ability to convey more context in my commits this way. I’m still guilty of the occasionally overusing:
♻️ Fix the thing
type messages when I’m lazy; doesn’t fix that bad habit, but I’m generally much happier reading mine or someone else’s PR commit summary with this extra bit of context added.
Could have been worse. I mean, like, imagine of you were using like CVS and you put a watch on the root! Haha and then like every trivial commit in the repo caused everyone to in the entire org to get an email and it crashed the email servers.
Like who’d even DO that?! Though, I bet if you met that guy he’d be ok. Like not a jerk, and pretty sorry for all those emails. A cool guy.
You nailed it with the critique of commit messages. We use gitmoji to convey at-a-glance topic for commits and otherwise adhere to Tim Pope’s school of getting to the point
100% they do. Rebase is an everyday thing, merge is for PRs (for me anyway). Or merges are for regular branches if you roll that way. The only wrong answer is the one that causes you to lose commits and have to use reflog
, cos…well, then you done messed up now son… (but even then hope lives on!)
Here’s an example
Say I work on authentication under feature/auth
Monday and get some done. Tuesday an urgent feature request for some logging work comes in and I complete it on feature/logging
and merge clean to main. To make sure all my code from Monday will work, I will then switch to feature/auth
and then git pull --rebase origin main
. Now my auth commits start after the merge commit from the logging pr.
Merge keeps the original timeline. Your commits go in along with anything else that happened relative to the branch you based your work off (probably main
). This generates a merge commit.
Rebase will replay all the commits that happened while you were doing your work before your commits happen, and then put yours at the HEAD, so that they are the most recent commits. You have to mitigate any conflicts that impact the same files as these commits are replayed, if any conflicts arise. These are resolved the same way any merge conflict is. There is no frivolous merge commit in this scenario.
TlDR; End result, everything that happened to the branch minus your work, happens. Then your stuff happens after. Much tidy and clean.
Lol write your own fanfiction.