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/)D

danrot

@ danrot @kbin.social

Posts
25
Comments
16
Joined
3 yr. ago

  • git bisect and the importance of a clean history

    Jump

  • I swear, I didn't come up with that myself, I read that somewhere else, but of course I don't have a source anymore 🙈 Maybe some git developer is a huge fan of wordplays?

  • Code comments are (mostly) a violation of DRY

    Jump

  • I think this is one of the most common misconceptions about DRY. Just because you have two times the same line in your code base it is not automatically a violation of DRY. If you compare if a number is bigger than 18 it is definitely not a good idea to extract that part if you are comparing the hour of the day once and the age the other time. In that case it would even be bad to create an abstration, and it would not be a violation of DRY. And I agree that something like this leads to code that is hard to maintain.

  • Code comments are (mostly) a violation of DRY

    Jump

  • I have also seen well commented code, but in this article I concentrate on the bad ones. Are you saying you have never seen a bad code comment?

  • Code comments are (mostly) a violation of DRY

    Jump

  • I think this is also in line with my article, since not being able to put yourself into somebody else's shoes (or even in yourself future's ones) is the reason for so much bad comments. But adding a comment to every single line cannot be the solution either, at least not in a higher programming language.

  • Code comments are (mostly) a violation of DRY

    Jump

  • I agree with almost all of what you say, but the thing IME is that in most cases people learn to comment a lot, which results in comments that feel like they've been done just for the sake of it, which is one of the main problems IMO. It's not like "just add a comment, it won't hurt", since comments can be immensely misleading and literally take a lot of time until figuring out that the comment was wrong if you trust the wrong ones.

    I also agree that this tends to be worse with bad code, which also is not surprising. Sometimes it feels to me like people think they can fix bad code with some comments, and I think that is far from being true.

    I also admit that especially the title of the article might be a bit provocative, but giving the general positive sentiment of comments I think this is called for. Sometimes you have to exaggerate a bit to get some attention. I don't like click-baiting either, but unfortunately it works ;-)

  • Code comments are (mostly) a violation of DRY

    Jump

  • I give you that, but I am not talking about assembly languages, therefore the examples from my blogpost aren't showing any :-)

  • Code comments are (mostly) a violation of DRY

    Jump

  • Totally agree, that's why I also mentioned this in the article.

    Very often good code that is self-explanatory does not need any comments at all and if it does, the comment should describe why it has been implemented this way instead of just repeating what the code already says.

  • Programming @kbin.social
    danrot @kbin.social

    Code comments are (mostly) a violation of DRY

    danielrotter.at /2021/01/16/code-comments-are-mostly-a-violation-of-dry.html

  • Automatic command execution on file changes with entr

    Jump

  • Ah, you are talking about systemd, wasn't aware of that... I imagine that to be much more complicated for many use cases. E.g. running a unit test (as I describe in the article) isn't something I would use systemd for. Setting up a path and a service seems more complicated than using entr, and it is probably also harder to get to the output as well.

  • Automatic command execution on file changes with entr

    Jump

  • I am not exactly sure what you mean by that... But the main advantage is that the command does not have to be executed manually everytime you change something. Instead entr recognizes when something changes and re-executes the command for you.

  • Linux @kbin.social
    danrot @kbin.social

    Automatic command execution on file changes with entr

    danielrotter.at /2020/10/07/automatic-command-execution-on-file-changes-with-entr.html
  • symfony @kbin.social
    danrot @kbin.social

    Applying design patterns: The builder and factory pattern in a DI context

    danielrotter.at /2020/08/24/applying-design-patterns-the-builder-and-factory-pattern.html

  • Execute commands for multiple files using fish

    Jump

  • Doesn't it also use case and esacand a few others? Such a weird language^^

  • WebDev @kbin.social
    danrot @kbin.social

    Web Push Book

    web-push-book.gauntface.com
  • WebDev @kbin.social
    danrot @kbin.social

    Understanding animated graphs in D3.js

    danielrotter.at /2020/06/12/understanding-animated-graphs-with-d3js.html

  • Execute commands for multiple files using fish

    Jump

  • That's true, but the syntax is different then. In this blog post I cover fish, and I didn't intent to say that this cannot be done in other shells (and I think I never said so).

  • Linux @kbin.social
    danrot @kbin.social

    Execute commands for multiple files using fish

    danielrotter.at /2020/05/13/execute-commands-for-multiple-files-in-fish.html

  • It's 2023, here is why your web design sucks.

    Jump

  • Sure, web applications have different requirements and might warrant the use of more JavaScript than a website does. But one of the biggest problems nowadays IMO is that many developers choose these fancy technologies also for websites, just because they like them, without thinking too much about how that affects the user, and it does so in a mostly negative way. If you are building a website for the local bakery HTML and CSS backed by any CMS probably suffice, and there is no need to add the complexity of client-side JavaScript and SSR (or whatever) to it.

  • It's 2023, here is why your web design sucks.

    Jump

  • I think the point of the article (and I agree to that) is that "modern" websites (i.e. use heavy javascript frameworks) are having real issues that websites being built without loads of client-side javascript do not have. I guess some websites built in 2005 are performing better and are more accessible than websites being built today.

  • WebDev @kbin.social
    danrot @kbin.social

    It's 2023, here is why your web design sucks.

    heather-buchel.com /blog/2023/10/why-your-web-design-sucks/
  • Programming @kbin.social
    danrot @kbin.social

    Keep All Commits Green

    kellysutton.com /2019/07/15/keep-all-commits-green.html
  • Programming @kbin.social
    danrot @kbin.social

    Demystifying Containers - Part I: Kernel Space

    medium.com /@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504
  • Linux @kbin.social
    danrot @kbin.social

    Finding used values of XML attributes using the command line

    danielrotter.at /2020/04/14/finding-used-values-of-xml-attributes-using-the-commandline.html
  • WebDev @kbin.social
    danrot @kbin.social

    Writing a TodoMVC App With Modern Vanilla JavaScript

    frontendmasters.com /blog/vanilla-javascript-todomvc/

  • Avoid z-indexes whenever possible

    Jump

  • I have even mentioned stacking contexts in the article, and the thing is that they are not only introduce with z-index, which makes them even more complex :-/ So yeah, it certainly helps if you understand them, but I think it does not make the problem less complex.

  • Tailwind, and the death of web craftsmanship

    Jump

  • I mean it is not really inline styles, with inline styles only it is e.g. not possible to implement a hover style AFAIK. I think the inventor has written a blog post explaining the steps, is that what you are referring to? I also read that, and it kinda makes sense, but basically giving up on development tools to work properly is kind of a high trade IMO.

    I would also be interested in seeing a performance benchmark. As the article says, gzip will probably make the difference in terms of network traffic negligible, but it would be interesting to see the impact it has on parsing HTML.