overview for best_username

Data from deleted GitHub repos may not really be deleted in c/technology@lemmy.world

[-] best_username_ever@sh.itjust.works 4 points 3 months ago

How can such a wrong answer get so many points? Clones and forge forks are unrelated. First, GitHub or GitLab cannot and could not link clones together without analyzing the remotes of each clone.

FFS it's a tech community...

Data from deleted GitHub repos may not really be deleted in c/technology@lemmy.world

[-] best_username_ever@sh.itjust.works 7 points 3 months ago

Forks do not exist in git. It's a GitHub feature, and a massive blunder at the same time.

Is there anyone who can help me mod and style a community? Or do I need to do it on my own? in c/nostupidquestions@lemmy.world

[-] best_username_ever@sh.itjust.works 1 points 3 months ago

Try gimp.org.

Is there anyone who can help me mod and style a community? Or do I need to do it on my own? in c/nostupidquestions@lemmy.world

[-] best_username_ever@sh.itjust.works 1 points 3 months ago

Yeah. They only read textbooks to quiet kids, they do not have unpaid overtime at home for grading tests, and earn a million dollars every month. Lazy bastards.

Vinyl records outsell CDs for the second year running in c/music@lemmy.world

[-] best_username_ever@sh.itjust.works 3 points 3 months ago

It’s fake nostalgia of an era they never experienced. Vinyls always sounded like shit but we had no comparison except the better sound of movie theaters, but you couldn’t have that at home.

Then the audio CD appeared and it was like the second coming of Jesus. The sound was really a hundred times better than vinyls, even with the same set of amps and speakers.

One day they’ll tell us that VHS on a small black and white TV is better than a 4K movie on a giant screen.

Censure : plus de 500 artistes interpellent Vincent Bolloré après la disparition de Zaho de Sagazan des ondes de Lagardère in c/france@jlai.lu

Reddit blocking all major search engines, except Google in c/technology@lemmy.world

[-] best_username_ever@sh.itjust.works 32 points 3 months ago

Is there a downside? I’m confused.

We finally know what caused the global tech outage - and how much it cost in c/technology@lemmy.world

[-] best_username_ever@sh.itjust.works 4 points 3 months ago

I don’t understand the downvotes. You’re right on all points. If the task is too big, it can take years from testing another solution to using it for real.

YSK that if you don't like AC/DC, then you are un-american... in c/youshouldknow@lemmy.world

[-] best_username_ever@sh.itjust.works 36 points 3 months ago

I’m bored too, but not bored enough to post shitty shit like this.

[Fil quotidien] Discussion du jour 26-07-2024 in c/forumlibre@jlai.lu

[-] best_username_ever@sh.itjust.works 1 points 3 months ago

On veut des photos avant et après, même floutées.

What are your small and silly questions in life? in c/asklemmy@lemmy.world

[-] best_username_ever@sh.itjust.works 4 points 3 months ago

Do you do it yourself with a European recipe? You would get the same result I guess.

Why do so many people use NGINX? in c/selfhosted@lemmy.world

[-] best_username_ever@sh.itjust.works 24 points 3 months ago

Back when Nginx started, Apache was the only alternative and a big pain in the ass. That’s how it became popular.

12

Is there a "markup language" to describe a debugging session? (sh.itjust.works)

submitted 5 months ago by best_username_ever@sh.itjust.works to c/experienced_devs@programming.dev

10 comments fedilink

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.

// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)

I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!