Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BE
best_username_ever @sh.itjust.works
Posts 2
Comments 406
How has Git changed the way you think about version control?
  • The staging area changed the way I work for the better. When I develop something, a file can be at the same time "not modified yet," in progress where I can carefully accept or reject the modifications, and partially done when the parts have been confirmed and added to the staging area.

    Once nothing is "in progress" anymore, I know that my future commit is almost perfect and I can quickly review my stuff before committing. It’s faster and more safe than other tools.

  • In your career, have you found a drama free workplace?
  • Maybe try to detect or feel if the person in front of you is really a nice person or if he’s faking it.

    The last HR guy I met was so nice to me and enthusiastic that it was really suspicious. I had met real psychopaths before and I was careful. But in the end, he really wanted to take care of the coworkers, and it took me one whole month to understand this.

  • Privacy-Preserving Attribution | Firefox Help
  • Very disappointed. I’m starting to see how I could contribute to Servo or Ladybird as an alternative because I haven’t seen Mozilla do that kind of shit so far.

    They wasted money with stupid CEOs and stuff unrelated to Firefox, but sucking the dick of advertisers is on a higher level.

  • In your career, have you found a drama free workplace?
  • I’ve been working for almost 10 companies in 20 years, and I have only found 2 drama free workplaces so far. It’s random and I don’t think there are signs that could show you whether a job is good or bad.

    Most HR people are happy when they hire you but it usually means nothing, sorry.

    Last but not least, drama free could also mean "we’re gonna fire everybody in a few months," which makes the choices more difficult to make.

  • Is there a "markup language" to describe a debugging session?

    cross-posted from: https://sh.itjust.works/post/19440902

    > 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!

    1

    Is there a "markup language" to describe a debugging session?

    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!

    10