home.social

#codecomments — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #codecomments, aggregated by home.social.

  1. Comment Studio for Visual Studio - Enhance XML documentation comments with rich rendering, automatic reflow, collapsing, color-coded tags, and clickable issue links

    marketplace.visualstudio.com/i

    #visualstudio #xmldoc #documentation #codecomments #productivity

  2. Comment Studio for Visual Studio - Enhance XML documentation comments with rich rendering, automatic reflow, collapsing, color-coded tags, and clickable issue links

    marketplace.visualstudio.com/i

    #visualstudio #xmldoc #documentation #codecomments #productivity

  3. Comment Studio for Visual Studio - Enhance XML documentation comments with rich rendering, automatic reflow, collapsing, color-coded tags, and clickable issue links

    marketplace.visualstudio.com/i

  4. 👨‍💻🎨 Behold, D2's groundbreaking leap from stick figures to #ASCII art! At long last, developers can marvel at their code comments adorned with 1970s-inspired "graphics" – because who doesn't love squinting at cryptic text mosaics? Next up: PowerPoint presentations in Morse code! 🚀✨
    d2lang.com/blog/ascii/ #D2 #art #developer #fun #codecomments #retrographics #techhumor #HackerNews #ngated

  5. 👨‍💻🎨 Behold, D2's groundbreaking leap from stick figures to #ASCII art! At long last, developers can marvel at their code comments adorned with 1970s-inspired "graphics" – because who doesn't love squinting at cryptic text mosaics? Next up: PowerPoint presentations in Morse code! 🚀✨
    d2lang.com/blog/ascii/ #D2 #art #developer #fun #codecomments #retrographics #techhumor #HackerNews #ngated

  6. "// Return the competitions enriched with slugs"

    ..is, for now, my favorite code comment I've written.

    #coding #codeComments

  7. "// Return the competitions enriched with slugs"

    ..is, for now, my favorite code comment I've written.

    #coding #codeComments

  8. "// Return the competitions enriched with slugs"

    ..is, for now, my favorite code comment I've written.

    #coding #codeComments

  9. Not all comments in source code are useful but it's often not clear how to improve them.

    This post offers some practical advice on when and how to rewrite, remove, or turn comments into code. The discussion of "should comments" is particularly interesting.

    noncombatant.org/2023/08/27/co

  10. Not all comments in source code are useful but it's often not clear how to improve them.

    This post offers some practical advice on when and how to rewrite, remove, or turn comments into code. The discussion of "should comments" is particularly interesting.

    noncombatant.org/2023/08/27/co

    #CodeComments #programming

  11. Not all comments in source code are useful but it's often not clear how to improve them.

    This post offers some practical advice on when and how to rewrite, remove, or turn comments into code. The discussion of "should comments" is particularly interesting.

    noncombatant.org/2023/08/27/co

    #CodeComments #programming

  12. Thanks #TestMuConf for a great session. Rock on! 🤘

    For anyone interested in reading more about #CodeComments , here's my blog post on it: responsibleautomation.wordpres

  13. Thanks #TestMuConf for a great session. Rock on! 🤘

    For anyone interested in reading more about #CodeComments , here's my blog post on it: responsibleautomation.wordpres

  14. Thanks #TestMuConf for a great session. Rock on! 🤘

    For anyone interested in reading more about #CodeComments , here's my blog post on it: responsibleautomation.wordpres

  15. share your best #pythoncomments or #codecomments of any language, you lol, when you read it :awesome: :python:

  16. share your best #pythoncomments or #codecomments of any language, you lol, when you read it :awesome: :python:

  17. I'm #bored. Let's have a #flamewar about #codecomments.

    There are those "YOU SHOULD NEVER WRITE COMMENTS, IF YOU NEED COMMENTS YOUR CODE SUCKS AND NEED REWRITING"

    and then we have "You should comment *ALL* code *ALL* the time"

    And then we have "You should write comments, if it makes sense and the code is non trivial"

    Which camp are you in, and why?

    #devlife #dev #code #codingstyle #comments

  18. I'm #bored. Let's have a #flamewar about #codecomments.

    There are those "YOU SHOULD NEVER WRITE COMMENTS, IF YOU NEED COMMENTS YOUR CODE SUCKS AND NEED REWRITING"

    and then we have "You should comment *ALL* code *ALL* the time"

    And then we have "You should write comments, if it makes sense and the code is non trivial"

    Which camp are you in, and why?

    #devlife #dev #code #codingstyle #comments

  19. If you're writing #docs or #codecomments, or especially if you're *not* because you're afraid they'll go stale, remember:

    Statements about the past are true for longer than statements about the present.

    E.g: "This function does X" will go stale next time any change is made. "On 2023-01-19 we needed a function that does X" will be true forever.

    Bonus points if you can encode "does X" as a test, and then your comment can be about *why* you want X. #tdd #xp

  20. If you're writing #docs or #codecomments, or especially if you're *not* because you're afraid they'll go stale, remember:

    Statements about the past are true for longer than statements about the present.

    E.g: "This function does X" will go stale next time any change is made. "On 2023-01-19 we needed a function that does X" will be true forever.

    Bonus points if you can encode "does X" as a test, and then your comment can be about *why* you want X. #tdd #xp

  21. If you're writing #docs or #codecomments, or especially if you're *not* because you're afraid they'll go stale, remember:

    Statements about the past are true for longer than statements about the present.

    E.g: "This function does X" will go stale next time any change is made. "On 2023-01-19 we needed a function that does X" will be true forever.

    Bonus points if you can encode "does X" as a test, and then your comment can be about *why* you want X. #tdd #xp

  22. Today in #CodeComments:

    /* Theoretically this should be fine, in practice it may not */

    #Coding

  23. Today in #CodeComments:

    /* Theoretically this should be fine, in practice it may not */

    #Coding

  24. Today in #CodeComments:

    /* Theoretically this should be fine, in practice it may not */

    #Coding

  25. So I've been working on a macro crate in #Rust for a little while... and I wanted to ask, what do you think of my style of #CodeComments, #Developers of Mastodon? 😁

    (I'm rather pleased with this one...)
    #FOSS #Opensource #Git #GitHub #Programming #Development

  26. So I've been working on a macro crate in #Rust for a little while... and I wanted to ask, what do you think of my style of #CodeComments, #Developers of Mastodon? 😁

    (I'm rather pleased with this one...)
    #FOSS #Opensource #Git #GitHub #Programming #Development