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/)GC
Posts
3
Comments
425
Joined
2 yr. ago

  • La raison est aussi difficile à trouver. Est-ce le boulot merdique, les chefs tyranniques, la perte de repères ? Il y a des centaines d’explications possibles mais c’est un problème qui a l’air d’être global à nos sociétés modernes.

  • Bon courage à ceux qui veulent jardiner le soir puisque nos gentils patrons jugent que le télétravail est impossible à mettre en place.

    Pour ce qui est de lire ou cuisiner, c’est une idée révolutionnaire. Je pense que personne n’y avait pensé avant. Merci à cet article pour cette révélation.

  • I hate videos that try to talk about programming concepts. Also it would be better if we had a real comparison between Nim and Zig as it seems that they try to fill the same void in programming languages.

  • Si c'est un bot officiel, je suis pour. Par contre, est-ce qu'on pourrait avoir le code du bot genre "open-source" sur GitHub ou autre ? Ça serait bien, au moins pour lire, voire pour corriger les bugs ou ajouter des fonctions.

  • Yes, it's common. No, it shouldn't be tolerated. Your boss/tech lead/whatever should be involved. Here is what should be done ideally:

    • not following best practices: you MUST implement merge requests (GitLab, GitHub, etc.) and his code shouldn't be approved which means that his code won't ever be merged in a shitty state. Force 1 or 2 approvals for each MR, and it should not be possible to merge an MR if it has open comments. The boss should ask every day "why is your code not merged yet?" and he'll have to explain why people don't approve his shitty code.
    • shitty unit-tests: same thing, the boss should show him how to do this, and the MR shouldn't be approved.
    • breaking unit-tests: it's the job of the CI to literally block MRs that break unit-tests (whether it's code coverage or unit-tests).
    • leaves me to fix it during PR approval: NO, it's HIS merge request, not yours.

    To sum it up: devs must not approve his MRs, the CI must block MRs that break tests.

  • Doxygen may be required in regulated industries like healthcare, banking, or robotics, but programmers never use it internally. The headers themselves are useful though and show that programmers take care of what they write even if they don't read the generated HTML.

  • Yes, serious people write docs. I hate this bullshit about code that should be so good that it's "auto-documenting." It never happens in real life. Code is at best of average quality, but it needs documentation. At my previous job they had "guidelines" to make sure that code didn't needed doc. It was a bad joke and we had the worst code I've ever seen.

    I don't have solutions for you though. You need a combo of documentation generation, code formatter (in the CI maybe, or before a commit), and code linters to check for errors.

  • I don't understand how a "rude customer" is related to "most people buy big cars." Also, the customer is always right is an American thing, that may explain why I'm confused.

    Last but not least, I bought the smallest car available because I wanted this. Most people buy big cars because they are influenced by the things around them, it doesn't mean that they are rude to the cashiers.