okl

23 ms·

271.
by okl 5y ago
I disagree. It's not difficult to stage single lines using the right tool.
272.
by okl 5y ago
> 4. use `git add -p` I strongly recommend tig
273.
by okl 5y ago
Not much trouble if you're used to it. git rebase --interactive master In Vim: ciw e ESC :x git reset HEAD~ // Make your commits git rebase --continue
274.
by okl 5y ago
> easy to revert later Depends on what you want to revert? git revert accepts more than one commit!
275.
by okl 5y ago
My aliases: alias.c commit alias.cf commit --fixup alias.cm commit --message alias.co checkout alias.f fetch -v -p alias.par pull --rebase --autostash alias.ri rebase --interactive --autosquash --autostash
276.
by okl 5y ago
Squashing commits is something lazy people do! :P
277.
by okl 5y ago
Right, I don't think rebasing is that daunting if you take a few hours to practice. It's time well spent. Sometimes you can even create empty commits (--allow-empty) up-front (if you already know about all the things that have to
278.
by okl 5y ago
I highly recommend tig because it lets you easily stage each line/change separately. Together with interactive rebase and fixup commits, it becomes super easy to group changes where they belong. For fixup commits with tig (in main view
279.
by okl 5y ago
Title is misleading at best.
280.
by okl 5y ago
I worked with both, 'architecture astronauts' (lol!) and shit-coders. I'd prefer there to be a balance. Code has quality can be measured in more than just one dimension. It's fine if code works, but it's even better
281.
by okl 5y ago
> If I were to refactor it at this point, it's really only to pander to my own ego, which probably isn't a sensible business goal. But it could be fun! You are aware of the risks, so if you'd really love to do it, knock yo
282.
by okl 5y ago
Upgrade to a refurbished T450s or T460 and you get a very nice FHD IPS display.
283.
by okl 5y ago
editions ? Why not make products repair-friendly by default?
284.
by okl 5y ago
> Code review → Valuable The activity in itself is not valuable, and code does not become better just because somebody looks at it. Identifying and subsequently fixing flaws -- that's what makes a code review worthwhile. Your concep
285.
by okl 5y ago
Thanks for putting in the effort and publishing the data. Are there indications that point to good/bad filtration quality? What do the good/bad products have in common?
286.
by okl 5y ago
> If a major FOSS Linux distro decided to add a virus to their latest release, would you say the same thing? https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-am...
287.
by okl 5y ago
I agree that it was a dick move from his side. Fork his project, or use an older version. I am not convinced that him breaking his code is something that ought to be punished. GitHub gets the right to close their hand while Marak doesn&#x27
288.
by okl 5y ago
Exactly.
289.
by okl 5y ago
How do you know that when you don't know what else he was using his GitHub account for?
290.
by okl 5y ago
Not different from Google shutting down someone's account, something that's constantly bemoaned on Hacker News.
291.
by okl 5y ago
Instead of the government, we let corporations repress deviants.
292.
by okl 5y ago
Using someone's code (for free) doesn't mean you can dictate terms to them.
293.
by okl 5y ago
Well fuck them. It's his code, he should be able to do with it whatever he wants.
294.
by okl 5y ago
You might find this resource interesting: https://www.linkedin.com/pulse/clean-hydrogen-ladder-v40-mic... (Yeah, linkedin sucks)
295.
by okl 5y ago
False dichotomy?
296.
by okl 5y ago
> Urea is a component of AdBlue The other component being water.
297.
by okl 5y ago
Same with CO2 -> https://www.theguardian.com/politics/2021/sep/22/why-is-the-... https://www.bbc.com/news/explainers-58626935
298.
by okl 5y ago
eat flaming death
299.
Identify a Flag(flagid.org)
6 points by okl 5y ago|0 comments
300.
by okl 5y ago
How boring.

More ›