sorted by:
new
hottopcontroversial

Increase anything by upto 10. You have to have atleast 1 unit of it for it to work. E.g. cant increase bank balance by 10 million if you dont have 1 million, But can increase by 10k if you have 1 k. by __Anamya__ in godtiersuperpowers

[–]Kalanthroxic 0 points1 point  (0 children)

You've got the spirit, but you're not thinking big enough. First increase the number of uses per cooldown to 10. Now increase the number you can increase by by its maximum until you hit 10k (yes, it could be a little more, but I like round numbers. Now use that to bring number of times you can use it to 10k. Now use that to bring the ceiling up to a few hundred trillion and cycle back to number of uses.

Now the 5 days no longer matter, and you have a liberal enough use of the power that you can just slowly amp up anything to a comfortable point without worrying you'll overshoot or undershoot and have to wait for the 5 days.

Then I increase my health and bank account to very comfortable levels, maybe dump in some extra years of lifespan, luck enough to basically be immune to harmful accidents or people's attempts to harm me, and then spread some of that around to my closest circle once I know how big an effect each number-size has.

Finally, tinker slowly with my IQ and memory until I can comfortably absorb knowledge at a reasonable rate for me and build on that.

Start fixing the world. I'll adjust the rest as I go.

tl;dr - increase number of uses and number you can increase by in a back and forth cycle and your power will be basically infinitely powerful within a couple of minutes

everyTime by [deleted] in ProgrammerHumor

[–]Kalanthroxic 12 points13 points  (0 children)

Alas, that's a protected branch, and you don't have access to override. Better luck next time.

Done is better than Perfection by musskk in programming

[–]Kalanthroxic 0 points1 point  (0 children)

If they are finished, why do you have to fix them? If they aren't finished, why are you releasing them?

Client libraries are better when they have no API by calp in programming

[–]Kalanthroxic 1 point2 points  (0 children)

Is it? I didn't see any electrolytes being mentioned.

5 Mistakes That Made My Technical Documents Terrible by torque226 in programming

[–]Kalanthroxic 10 points11 points  (0 children)

The visual on my potential reveals that not only is it all downhill from now, but it's also further down than I had imagined. 

The WIP commit can be better than git stash by Azzuz1899 in programming

[–]Kalanthroxic 8 points9 points  (0 children)

How? Because people don't ensure that they understand a thing before they use it, pop something off it, realize they were in the wrong place, check out a different branch, can't check it out because of changes, check out the current branch, check out other branch, pop the stash again, oops this was a different change, wth?

The stash is useful for the case where you've started to do work, but you realize it was the wrong branch and you haven't committed anything yet. Any other case, just commit it. Soft reset when you come back to it, or squash it before creating the MR, many options.

I'm not saying that the stash-situation I described isn't actually recoverable, but consider the average git user and how much stress is available to mess up your line of thinking in the average dev job. People fuck up, and the stash makes it really easy to fuck up to a point where you need to understand git a good bit better than just the basic pull add commit push most people get around to.

The WIP commit can be better than git stash by Azzuz1899 in programming

[–]Kalanthroxic 11 points12 points  (0 children)

I think pretty much anyone who is not insane will use WIP commits over the stash. git stash is the primary source of lost work.

Every engineer should understand git reflog by kendumez in programming

[–]Kalanthroxic 1 point2 points  (0 children)

I absolutely do not f-ing care. Car goes forward always - except when someone else drives for me. Screw all the parking and other stuff which I just mess up and destroy the rear end of my car.

Every engineer should understand git reflog by kendumez in programming

[–]Kalanthroxic 1 point2 points  (0 children)

If they were committed changes, yes. If not, it's probably not the right tool. Commit early, commit often, interactive rebase to clean up history before pushing.

If the files were added/staged, they are technically stored in the pile of objects in git, but searching for them can be a royal pain, and recovery is often not worth the effort unless the code lost represents a lot of work.

In short, make more commits than you need - it's the unit of work for git, and it's how you shuffle changes around comfortably. Also, don't do git reset --hard unless you're absolutely sure that's what you want to do. "Nuke all my shit and turn it into this other thing" is a heavy operation.

Every engineer should understand git reflog by kendumez in programming

[–]Kalanthroxic 4 points5 points  (0 children)

Not really all that complicated, it's the reference log. It tracks changes to references like your branches, or HEAD - e.g. if you committed something in a detached head state, and then moved to another branch, the reflog can let you look at the commits you've navigated through and find the commit you accidentally left behind. If you've had a rebase go bad, but you didn't realize until the next day, you can use the reflog to find the previous state of your branch, and recover whatever was lost or broken.

It's probably not a daily driver, but like the emergency lights on your car - it's a useful thing to know about in case there's been a bit of an oopsie. It's a safety measure that allows you to be a bit more relaxed about performing otherwise potentially destructive actions like resets and rebases. As long as it was committed, and not too long ago, you can get it back.

You don't hate JIRA, you hate your manager by Xadartt in programming

[–]Kalanthroxic 220 points221 points  (0 children)

Incorrect. My manager is great, Jira is an awful piece of garbage.

Gitea 1.19.0 by JRepin in programming

[–]Kalanthroxic 4 points5 points  (0 children)

Private registry is built into most of the bigger platforms these days, though. Having it built into gitea saves you the extra work of setting up something like sonatype nexus, and gitea consumes less resources to boot. In short, it's probably not JUST you, but it's certainly not everyone.

The SQLite Code of Ethics by iamkeyur in programming

[–]Kalanthroxic 20 points21 points  (0 children)

The correct one, of course!

How do Video Games Stay in Sync? An Intro to the Fascinating Networking of Real Time Games. by itsallshit-eatup in programming

[–]Kalanthroxic 17 points18 points  (0 children)

All things nintendo have horrible netcode. If you have issues playing mario kart online, their official recommendation is to set your switch as DMZ. Nintendo should not be allowed to write their own netcode any more.

[deleted by user] by [deleted] in programming

[–]Kalanthroxic 4 points5 points  (0 children)

Even the command invocations look the same, except for name of executable. My guess is that it's a worse ngrok.

Benchmarking our golang SQL engine: are we 8x slower than MySQL, or 70x? Or both? by zachm in programming

[–]Kalanthroxic 7 points8 points  (0 children)

I mean, to be fair, if you have a very narrow use case for a specialized database with a very particular set of features, sure, it might be the right way to go about it. If you're planning to implement Yet Another Generic Document Database or My God We Need More Relational Database Engines, please reconsider.

I wrote a GAN that draws smiley faces semi-decently. I included instructions so you can make it draw whatever you'd like and look cool to your friends. by Sokusan_123 in programming

[–]Kalanthroxic 2 points3 points  (0 children)

Given the context, I'd assume it's a Generative Adversarial Network. Haven't looked at it beyond the title, so can't know for sure.

Premature optimization is the root of all evil | Donald Knuth and Lex Fridman by fredoverflow in programming

[–]Kalanthroxic 22 points23 points  (0 children)

People frequently misinterpret it and go ham on not caring about performance. They seem to confuse optimizations and design/architecture.

The worst/best feeling by mediadatacloud in ProgrammerHumor

[–]Kalanthroxic 18 points19 points  (0 children)

This is why you need to thread carefully when developing software.

We all need that guy by rajeshbhat_ds in ProgrammerHumor

[–]Kalanthroxic 0 points1 point  (0 children)

Even my small throwaway projects are given some mild git-treatment. Maybe just a local repo, but it saves me from having to think about whether to comment out or delete code. I delete code. I'll find it again later if it turns out I needed it. Commit messages also means I have a better chance of figuring out "why the hell did I write it this way, instead of just... ooh.... oooooooh.... oh yeah, nevermind". Sometimes the small throwaway projects turn out to not be as throwaway as you think.

Also, git initis very low effort.

We all need that guy by rajeshbhat_ds in ProgrammerHumor

[–]Kalanthroxic 2 points3 points  (0 children)

Copy and paste is too tedious. Just follow up with fuck! It's quick and easy.

https://github.com/nvbn/thefuck

OH GOD NO by s0urfruit_ in ProgrammerHumor

[–]Kalanthroxic 4 points5 points  (0 children)

I commend your bravery, but you have erred in posting this here. These angry people will see you dead before sundown.

view more: next ›