JATtho

JATtho, 1 month ago

name your function as malloc() and see to world burn and generate bugs at factorial rate.

JATtho, 1 month ago

Lettme introduce you to ackermann’s function:

<span style="color:#323232;">int ack(int m, int n) {
</span><span style="color:#323232;">    if (m == 0) {
</span><span style="color:#323232;">        return n+1;
</span><span style="color:#323232;">    } else if((m > 0) && (n == 0)){
</span><span style="color:#323232;">        return ack(m-1, 1);
</span><span style="color:#323232;">    } else if((m > 0) && (n > 0)) {
</span><span style="color:#323232;">        return ack(m-1, ack(m, n-1));
</span><span style="color:#323232;">    }
</span><span style="color:#323232;">}
</span>

You won’t run out of stackoverflows any time soon.

JATtho, 1 month ago

A lot. That’s the answer.

JATtho, 1 month ago

After 362879 wrong answers you will pass. Or after 2,0922789888×10¹³ tries if it’s a fancy 4x4 grid.

JATtho, 1 month ago

std::chrono::neutronstar_clock

JATtho, 2 months ago (edited 1 month ago)

To produce 1 commit, I end up rebasing the damm thing at least 3 times. If there is an problem, it’s at least 2³ times.

JATtho, 2 months ago

Please, no, I get flashbacks from my 6-month journey (still ongoing…) of the code review process I caused/did. Keeping PR scope contained and small is hard.

From this experience, I wish GitLab had a “Draft of Draft” to tell the reviewer what the quality of the pushed code is at: “NAK”, “It maybe compiles”, “The logic is broken” and “Missing 50% of the code”, “This should be split into N PRs”. This would allow openly co-develop, discuss, and steer the design, before moving to nitpicking on the naming, formatting, and/or documentation details of the code, which is likely to drastically change. Drafts do work for this, but the discussions can get uncomfortably long and convolute the actual finishing of the review process.

Once both reviewer(s) and the author agree on the code design, the “DraftDraft” could be collapsed into a link in an normal Draft to be mocked next. The scope of such draft would be limited by the earlier “DraftDraft”.

JATtho, 2 months ago

<span style="color:#323232;">volatile int blackhole;
</span><span style="color:#323232;">blackhole = 1;
</span><span style="color:#323232;">const int X = blackhole;
</span><span style="color:#323232;">const int Y = blackhole;
</span>

Compiler is forbidden to assume that X == 1 would be true. It’s also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> “read only volatile value at read only address hwreg”. Compiler can assume the hwreg address won’t magically change, but can’t assume the value read from that address won’t.

JATtho, 2 months ago

Holy cow.

JATtho, 2 months ago

And you have bootstrapped an B compiler on that?

JATtho, 3 months ago

I think the difference with Dolphin is that it now emulates an extinct system(s), so it cannot possibly compete with the actual thing. They did have a close call last year, if I remember, and they pretty quickly went into “jettison all illegal shit out of the code base NOW.” -mode.

JATtho, 3 months ago

The day I configured git to use Geany for commit messages with a separate config specifically tuned for this, it improved my life by 300%

<span style="color:#323232;">~$ cat ~/bin/gitedit
</span><span style="color:#323232;">#!/bin/sh
</span><span style="color:#323232;">exec /usr/bin/geany -i -s -t -c ~/.config/gitgeany $@
</span>

Then in git config: git config --global core.editor “gitedit”

JATtho, 3 months ago

<span style="color:#323232;">gdb> break before it crashes
</span><span style="color:#323232;">gdb> record full
</span><span style="color:#323232;">gdb> continue
</span><span style="color:#323232;">(segfault)
</span>

gdb> set exec-direction reverse

JATtho, 3 months ago

It’s a FOSS project, so wish me luck, as you can now get it in the mail eventually.

I had to run a makepkg today, which now includes my self-written pieces of code in master. So I’m eating my own dog food now, and it’s good. Also, the itch from before has somehow relieved.

JATtho, 3 months ago

Bugs that have existed for +3 years in a component and are nearly immediately visible to the end user. Oldest source line I touched was from before 2010.

JATtho, 3 months ago

Reaper of the VMAs.

JATtho, 3 months ago

This cannot be an coincidence. I may actually finished something this time.

JATtho, 3 months ago

I clicked the link with SUS knob set to 900% and the other hand on the main breaker. It did not disappoint.

JATtho, 3 months ago

It happened to me when I was configuring IP geoblocking: Only whitelist IP ranges are allowed. That was fetched from a trusted URL. If the DNS provider just happened to not be on that list, the whitelist would become empty, blocking all IPs. Literally 100% proof firewall; not even a ping gets a pass.

JATtho, 4 months ago

Tätä odottaessa, kosmos24.

JATtho, 4 months ago

That’s because people are now aware of all of this shit happening, and some discreet day, just flip off the power from the house, doing indescribable things, and listens to the voices in their heads. And nobody will know.

JATtho, 4 months ago

Technical debt means how much work it takes to update legacy solution to a modern solution. E.g. each time a new C++ standard is used, all code written with the old standard should be checked. The work time needed to do this is paying up the technical dept.

Now, if you are lazy, and didn’t clean up the code, used the easy and sloppy solution, next time you have twice the work to be done. So the dept gets worse, if you do nothing.