home.social

#softwaretools — Public Fediverse posts

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

  1. I. CORRECTIONS:

    (1) The notation has square brackets for the old version:
    [-old-]{+new+}
    —I made several typos in the original post.

    (2) The incantation is `git diff --word-diff=plain'.

    II. NOTES:

    (a) There is also --word-diff-regex="." marking differences at single character granularity.

    (b) Sometimes I run `git diff' directly from the command line and sometimes from another environment, such as Emacs.
    The defaults may vary.

    @dougmerritt

    #Diff
    #Git
    #GitDiff
    #SoftwareTools

  2. I. CORRECTIONS:

    (1) The notation has square brackets for the old version:
    [-old-]{+new+}
    —I made several typos in the original post.

    (2) The incantation is `git diff --word-diff=plain'.

    II. NOTES:

    (a) There is also --word-diff-regex="." marking differences at single character granularity.

    (b) Sometimes I run `git diff' directly from the command line and sometimes from another environment, such as Emacs.
    The defaults may vary.

    @dougmerritt

    #Diff
    #Git
    #GitDiff
    #SoftwareTools

  3. I. CORRECTIONS:

    (1) The notation has square brackets for the old version:
    [-old-]{+new+}
    —I made several typos in the original post.

    (2) The incantation is `git diff --word-diff=plain'.

    II. NOTES:

    (a) There is also --word-diff-regex="." marking differences at single character granularity.

    (b) Sometimes I run `git diff' directly from the command line and sometimes from another environment, such as Emacs.
    The defaults may vary.

    @dougmerritt

    #Diff
    #Git
    #GitDiff
    #SoftwareTools

  4. I. CORRECTIONS:

    (1) The notation has square brackets for the old version:
    [-old-]{+new+}
    —I made several typos in the original post.

    (2) The incantation is `git diff --word-diff=plain'.

    II. NOTES:

    (a) There is also --word-diff-regex="." marking differences at single character granularity.

    (b) Sometimes I run `git diff' directly from the command line and sometimes from another environment, such as Emacs.
    The defaults may vary.

    @dougmerritt

    #Diff
    #Git
    #GitDiff
    #SoftwareTools

  5. Funny thing, algorithms.
    I replaced

    performanceID

    with

    performerID

    and if I were marking the change manually,
    it would be:

    -perform[-ance-]ID
    +perform{+er+}ID

    but in fact it is:

    -perform[-anc-]eID
    +performe{+r+}ID

    (obviously...).

    [Typos corrected.]

    #Diff
    #Morphology
    #SoftwareTools

  6. Funny thing, algorithms.
    I replaced

    performanceID

    with

    performerID

    and if I were marking the change manually,
    it would be:

    -perform{-ance-}ID
    +perform{+er+}ID

    but in fact it is:

    -perform{-anc-}eID
    +performe{+r+}ID

    (obviously...).

    #Diff
    #Morphology
    #SoftwareTools

  7. Funny thing, algorithms.
    I replaced

    performanceID

    with

    performerID

    and if I were marking the change manually,
    it would be:

    -perform[-ance-]ID
    +perform{+er+}ID

    but in fact it is:

    -perform[-anc-]eID
    +performe{+r+}ID

    (obviously...).

    [Typos corrected.]

    #Diff
    #Morphology
    #SoftwareTools

  8. Funny thing, algorithms.
    I replaced

    performanceID

    with

    performerID

    and if I were marking the change manually,
    it would be:

    -perform[-ance-]ID
    +perform{+er+}ID

    but in fact it is:

    -perform[-anc-]eID
    +performe{+r+}ID

    (obviously...).

    [Typos corrected.]

    #Diff
    #Morphology
    #SoftwareTools

  9. Funny thing, algorithms.
    I replaced

    performanceID

    with

    performerID

    and if I were marking the change manually,
    it would be:

    -perform[-ance-]ID
    +perform{+er+}ID

    but in fact it is:

    -perform[-anc-]eID
    +performe{+r+}ID

    (obviously...).

    [Typos corrected.]

    #Diff
    #Morphology
    #SoftwareTools

  10. My best friend Jim @jammcq and I work in very different ways. We have the same **goals**: finding or building the right answer for the customer (solves the right problems, costs the right amount).

    Both of us are very good with our tools. Both of us, for any given problem, probably already have all the tools we need to do the job. But even though we have the same end goal, we have different challenges, values, and techniques. For me, friction is a huge problem. Anything that gets in my way can become a progress-robbing obstacle. Lincoln said "Give me six hours to chop down a tree and I will spend the first four sharpening the axe." (though I’ve heard different numbers of hours).

    When I encounter friction: I evaluate, and if the math works out, I sharpen the axe.

    Jim and I both get the job done, but when we look at each other, the **natural** thing to see is through the lens of our **own** strengths (emphasizing: this is what we **see**, not the actual truth). He sees a man wasting time sharpening the goddamn axe. I see a man who’s going to spend hours longer than he needs, cutting down a tree with a dull tool.

    He feels his tools are proven and (his word) "nimble". We were comparing `find` (him) against `fd` (me). I feel like my tools do everything his do, but modern defaults, easier and faster to use. He’s been using `find` forever. He knows it so well, but uses it rarely enough that the effort vs payback for learning something new just doesn’t work out. The way I think and learn is just different. To me, the single dash "operators" you use with `find` **are** friction. It doesn’t work like other tools and I’m more about consistent systems than memorization. We both **are** using the right tools.

    We’re both wrong, of course. We’re both solving the right problems the right (for ourselves) way.

    #SoftwareDevelopment #Programming #SoftwareTools

  11. My best friend Jim @jammcq and I work in very different ways. We have the same **goals**: finding or building the right answer for the customer (solves the right problems, costs the right amount).

    Both of us are very good with our tools. Both of us, for any given problem, probably already have all the tools we need to do the job. But even though we have the same end goal, we have different challenges, values, and techniques. For me, friction is a huge problem. Anything that gets in my way can become a progress-robbing obstacle. Lincoln said "Give me six hours to chop down a tree and I will spend the first four sharpening the axe." (though I’ve heard different numbers of hours).

    When I encounter friction: I evaluate, and if the math works out, I sharpen the axe.

    Jim and I both get the job done, but when we look at each other, the **natural** thing to see is through the lens of our **own** strengths (emphasizing: this is what we **see**, not the actual truth). He sees a man wasting time sharpening the goddamn axe. I see a man who’s going to spend hours longer than he needs, cutting down a tree with a dull tool.

    He feels his tools are proven and (his word) "nimble". We were comparing `find` (him) against `fd` (me). I feel like my tools do everything his do, but modern defaults, easier and faster to use. He’s been using `find` forever. He knows it so well, but uses it rarely enough that the effort vs payback for learning something new just doesn’t work out. The way I think and learn is just different. To me, the single dash "operators" you use with `find` **are** friction. It doesn’t work like other tools and I’m more about consistent systems than memorization. We both **are** using the right tools.

    We’re both wrong, of course. We’re both solving the right problems the right (for ourselves) way.

    #SoftwareDevelopment #Programming #SoftwareTools

  12. My best friend Jim @jammcq and I work in very different ways. We have the same **goals**: finding or building the right answer for the customer (solves the right problems, costs the right amount).

    Both of us are very good with our tools. Both of us, for any given problem, probably already have all the tools we need to do the job. But even though we have the same end goal, we have different challenges, values, and techniques. For me, friction is a huge problem. Anything that gets in my way can become a progress-robbing obstacle. Lincoln said "Give me six hours to chop down a tree and I will spend the first four sharpening the axe." (though I’ve heard different numbers of hours).

    When I encounter friction: I evaluate, and if the math works out, I sharpen the axe.

    Jim and I both get the job done, but when we look at each other, the **natural** thing to see is through the lens of our **own** strengths (emphasizing: this is what we **see**, not the actual truth). He sees a man wasting time sharpening the goddamn axe. I see a man who’s going to spend hours longer than he needs, cutting down a tree with a dull tool.

    He feels his tools are proven and (his word) "nimble". We were comparing `find` (him) against `fd` (me). I feel like my tools do everything his do, but modern defaults, easier and faster to use. He’s been using `find` forever. He knows it so well, but uses it rarely enough that the effort vs payback for learning something new just doesn’t work out. The way I think and learn is just different. To me, the single dash "operators" you use with `find` **are** friction. It doesn’t work like other tools and I’m more about consistent systems than memorization. We both **are** using the right tools.

    We’re both wrong, of course. We’re both solving the right problems the right (for ourselves) way.

  13. My best friend Jim @jammcq and I work in very different ways. We have the same **goals**: finding or building the right answer for the customer (solves the right problems, costs the right amount).

    Both of us are very good with our tools. Both of us, for any given problem, probably already have all the tools we need to do the job. But even though we have the same end goal, we have different challenges, values, and techniques. For me, friction is a huge problem. Anything that gets in my way can become a progress-robbing obstacle. Lincoln said "Give me six hours to chop down a tree and I will spend the first four sharpening the axe." (though I’ve heard different numbers of hours).

    When I encounter friction: I evaluate, and if the math works out, I sharpen the axe.

    Jim and I both get the job done, but when we look at each other, the **natural** thing to see is through the lens of our **own** strengths (emphasizing: this is what we **see**, not the actual truth). He sees a man wasting time sharpening the goddamn axe. I see a man who’s going to spend hours longer than he needs, cutting down a tree with a dull tool.

    He feels his tools are proven and (his word) "nimble". We were comparing `find` (him) against `fd` (me). I feel like my tools do everything his do, but modern defaults, easier and faster to use. He’s been using `find` forever. He knows it so well, but uses it rarely enough that the effort vs payback for learning something new just doesn’t work out. The way I think and learn is just different. To me, the single dash "operators" you use with `find` **are** friction. It doesn’t work like other tools and I’m more about consistent systems than memorization. We both **are** using the right tools.

    We’re both wrong, of course. We’re both solving the right problems the right (for ourselves) way.

    #SoftwareDevelopment #Programming #SoftwareTools

  14. You have not read _Software Tools_ until you have read it in the original Ratfor.

    #Fortran #SoftwareTools

  15. You have not read _Software Tools_ until you have read it in the original Ratfor.

    #Fortran #SoftwareTools

  16. You have not read _Software Tools_ until you have read it in the original Ratfor.

    #Fortran #SoftwareTools

  17. You have not read _Software Tools_ until you have read it in the original Ratfor.

    #Fortran #SoftwareTools

  18. You have not read _Software Tools_ until you have read it in the original Ratfor.

    #Fortran #SoftwareTools

  19. QGIS DevTools — Déboguer et développer ses plugins plus efficacement
    Le développement de plugins QGIS peut parfois être fastidieux : recharger le plugin, déboguer, inspecter l’interface, exécuter des scripts, etc.
    C’est là que DevTools pour QGIS (NextGIS) entre en jeu — un ensemble d’outils conçus pour rendre le développement plus fluide, interactif, rapide et ergonomique.



  20. QGIS DevTools — Déboguer et développer ses plugins plus efficacement
    Le développement de plugins QGIS peut parfois être fastidieux : recharger le plugin, déboguer, inspecter l’interface, exécuter des scripts, etc.
    C’est là que DevTools pour QGIS (NextGIS) entre en jeu — un ensemble d’outils conçus pour rendre le développement plus fluide, interactif, rapide et ergonomique.
    #QGIS #PyQGIS #QGISPlugin #QGISDevelopment #Debugging
    #DevTools #PythonDevelopment
    #SoftwareTools
    #DeveloperExperience

  21. QGIS DevTools — Déboguer et développer ses plugins plus efficacement
    Le développement de plugins QGIS peut parfois être fastidieux : recharger le plugin, déboguer, inspecter l’interface, exécuter des scripts, etc.
    C’est là que DevTools pour QGIS (NextGIS) entre en jeu — un ensemble d’outils conçus pour rendre le développement plus fluide, interactif, rapide et ergonomique.
    #QGIS #PyQGIS #QGISPlugin #QGISDevelopment #Debugging
    #DevTools #PythonDevelopment
    #SoftwareTools
    #DeveloperExperience

  22. Building a website can feel like staring at an endless toolbox. So many tools, but which ones actually work?

    In this guide, I’ve rounded up my go-to open source picks for web development — tools that every dev should have in their kit.

    👉 Full article: bitskingdom.com/blog/best-open

    #OpenSource #WebDevelopment #DevTools #SoftwareEngineering #WebDev #Development #juniordevelopers #opensource #softwaretools

  23. Think your business is too small for powerful tools? Think again.
    Low-code apps can:
    ✅ Automate your emails
    ✅ Turn spreadsheets into dashboards
    ✅ Make your team look like a tech giant
    Check out 9 tools that every smart small business should know.

    Read chapter 2: bitskingdom.com/blog/low-code- 

    #Small Business #businesstips #features #lowcode #smallbiz #softwaretools #tools #lowcode #smallbusiness #productivity #automation #digitaltools

  24. Think your business is too small for powerful tools? Think again.
    Low-code apps can:
    ✅ Automate your emails
    ✅ Turn spreadsheets into dashboards
    ✅ Make your team look like a tech giant
    Check out 9 tools that every smart small business should know.

    Read chapter 2: bitskingdom.com/blog/low-code- 

    #Small Business #businesstips #features #lowcode #smallbiz #softwaretools #tools #lowcode #smallbusiness #productivity #automation #digitaltools

  25. Think your business is too small for powerful tools? Think again.
    Low-code apps can:
    ✅ Automate your emails
    ✅ Turn spreadsheets into dashboards
    ✅ Make your team look like a tech giant
    Check out 9 tools that every smart small business should know.

    Read chapter 2: bitskingdom.com/blog/low-code- 

    #Small Business #businesstips #features #lowcode #smallbiz #softwaretools #tools #lowcode #smallbusiness #productivity #automation #digitaltools

  26. Think your business is too small for powerful tools? Think again.
    Low-code apps can:
    ✅ Automate your emails
    ✅ Turn spreadsheets into dashboards
    ✅ Make your team look like a tech giant
    Check out 9 tools that every smart small business should know.

    Read chapter 2: bitskingdom.com/blog/low-code- 

    #Small Business #businesstips #features #lowcode #smallbiz #softwaretools #tools #lowcode #smallbusiness #productivity #automation #digitaltools

  27. Think your business is too small for powerful tools? Think again.
    Low-code apps can:
    ✅ Automate your emails
    ✅ Turn spreadsheets into dashboards
    ✅ Make your team look like a tech giant
    Check out 9 tools that every smart small business should know.

    Read chapter 2: bitskingdom.com/blog/low-code- 

    #Small Business #businesstips #features #lowcode #smallbiz #softwaretools #tools #lowcode #smallbusiness #productivity #automation #digitaltools

  28. Breaking news: #RubyMine is now free for those who aren't making money with it—because what better way to support developers than by ensuring they stay broke? 💸 Meanwhile, #JetBrains continues to remind us just how many tools it offers that we may never use. 🎉
    blog.jetbrains.com/ruby/2025/0 #Freebies #DeveloperSupport #SoftwareTools #StayBroke #HackerNews #ngated

  29. Breaking news: #RubyMine is now free for those who aren't making money with it—because what better way to support developers than by ensuring they stay broke? 💸 Meanwhile, #JetBrains continues to remind us just how many tools it offers that we may never use. 🎉
    blog.jetbrains.com/ruby/2025/0 #Freebies #DeveloperSupport #SoftwareTools #StayBroke #HackerNews #ngated

  30. Breaking news: #RubyMine is now free for those who aren't making money with it—because what better way to support developers than by ensuring they stay broke? 💸 Meanwhile, #JetBrains continues to remind us just how many tools it offers that we may never use. 🎉
    blog.jetbrains.com/ruby/2025/0 #Freebies #DeveloperSupport #SoftwareTools #StayBroke #HackerNews #ngated

  31. Breaking news: #RubyMine is now free for those who aren't making money with it—because what better way to support developers than by ensuring they stay broke? 💸 Meanwhile, #JetBrains continues to remind us just how many tools it offers that we may never use. 🎉
    blog.jetbrains.com/ruby/2025/0 #Freebies #DeveloperSupport #SoftwareTools #StayBroke #HackerNews #ngated

  32. ✨ Update 7.4.2.2
    Der QR-Code Creator erkennt jetzt automatisch Ihr System (Windows oder Unix) und optimiert den Zeilenumbruch.
    Das bedeutet: Noch bessere QR-Codes – für nahezu jede Anwendung.

    👉🏼 qr-cc.de

    #QRCodeCreator #Update7422 #QRCodeUpdate #NewFeatures #SoftwareTools #UpdateReady #BetterCodes #Innovation #SmartUpdate

  33. 🔍 / #software / #tools / #storage

    #TreeSize is a disk space analyzer for Windows with customizable file search and several exporting and reporting possibilities. Download for free today!

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools #SoftwareToolsStorage

  34. 🔍 / #software / #tools / #storage

    #TreeSize is a disk space analyzer for Windows with customizable file search and several exporting and reporting possibilities. Download for free today!

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools #SoftwareToolsStorage

  35. 🔍 / #software / #tools / #storage

    #TreeSize is a disk space analyzer for Windows with customizable file search and several exporting and reporting possibilities. Download for free today!

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools #SoftwareToolsStorage

  36. 🔍 / #software / #tools

    #Voiden.md — The Offline, Git-Native API Workspace

    Redefining how developers work with APIs. One Git-native, composable workspace. Offline-first. #Markdown-powered. Developer-loved.

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools

  37. 🔍 / #software / #tools

    #Voiden.md — The Offline, Git-Native API Workspace

    Redefining how developers work with APIs. One Git-native, composable workspace. Offline-first. #Markdown-powered. Developer-loved.

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools

  38. 🔍 / #software / #tools

    #Voiden.md — The Offline, Git-Native API Workspace

    Redefining how developers work with APIs. One Git-native, composable workspace. Offline-first. #Markdown-powered. Developer-loved.

    🐱🔗 laravista.altervista.org/CatLi

    #catlink #SoftwareTools

  39. 🚀 Oh, joy! A tool that ✨graciously✨ waits for your computer to catch its breath before doing anything remotely productive. Because who doesn't love a software-induced siesta while their RAM is on life support? 🤖💤
    github.com/surban/memstop #softwaretools #productivity #techhumor #RAMissues #codinglife #HackerNews #ngated

  40. 🚀 Oh, joy! A tool that ✨graciously✨ waits for your computer to catch its breath before doing anything remotely productive. Because who doesn't love a software-induced siesta while their RAM is on life support? 🤖💤
    github.com/surban/memstop #softwaretools #productivity #techhumor #RAMissues #codinglife #HackerNews #ngated