IIRC they’re paralyzed from the shoulders down, so probably not.
AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.
Damn, that’d make a cool movie.
“feat: stuff”
Guilty of this one myself.
Commit more often. Maybe work in a different feature branch, and don’t be afraid to commit your half-working crappy code. If it’s a personal project/fork, it’s totally acceptable to commit often with bad commit names and small unfinished changes: you can always amend/squash the commits later. That’s how I tend to work: create a new branch, work on the feature, rebase and merge (fast forward, no merge commit). Also, maybe don’t jump around working on random features :P
rust-analyzer is a pretty good LSP, and works in most modern text editors.
My advice? Just pick an editor and stick to it.
VSCode? Sure.
Jetbrains? Good choice.
Hell, Emacs? Why not?
I personally use Neovim, and it just works. No matter what I’m programming in, I’m still at home.
Just pick an editor that works for you. I’d suggest VSCode. Use VSCodium for a true FOSS experience, or Helix for a beginner friendly terminal editor.
If you really just want something Rust-focused, there’s RustRover from Jetbrains, but that’s about it.
A monad is just a monoid in the category of endofunctors.
If it passes.
I hope it passes.
Honestly for me electron apps can also get pretty janky.
Plus Electron takes WAY more than 2mb of RAM.
No Reddit account, you aren’t using their shitty app; IDK, seems like a win to me.
Reddit “traffic” doesn’t really mean or do anything for them(mainly at this scale).
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.
dukk
0 post score0 comment score
The Earth is a sphere, which means there’s no easy way to project it onto a flat surface. One of the methods used to project the Earth’s surface on the map results in certain places (such as Greenland) to be stretched to huge sizes, sometimes appearing as big as Africa (look up “Mercator map”). The joke here is that while we expect him to make a comment about the map’s projection, he instead comments on how Greenland on the physical map is only a few inches, as opposed to its actual size.
So yeah, subverted expectations, peak Dad joke