home.social

#softwarecomplexity — Public Fediverse posts

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

fetched live
  1. Ah yes, Podman Quadlets with Podman Desktop—because the world was simply crying out for yet another buzzword-laden tool to clog up your desktop. 🎉 Now you can drown in a sea of Podman releases, because who needs simplicity when you can have a convoluted mess? 🤡🚀
    podman-desktop.io/blog/podman- #PodmanQuadlets #PodmanDesktop #TechBuzzwords #SoftwareComplexity #DeveloperTools #HackerNews #ngated

  2. Ah yes, Podman Quadlets with Podman Desktop—because the world was simply crying out for yet another buzzword-laden tool to clog up your desktop. 🎉 Now you can drown in a sea of Podman releases, because who needs simplicity when you can have a convoluted mess? 🤡🚀
    podman-desktop.io/blog/podman- #PodmanQuadlets #PodmanDesktop #TechBuzzwords #SoftwareComplexity #DeveloperTools #HackerNews #ngated

  3. Ah yes, Podman Quadlets with Podman Desktop—because the world was simply crying out for yet another buzzword-laden tool to clog up your desktop. 🎉 Now you can drown in a sea of Podman releases, because who needs simplicity when you can have a convoluted mess? 🤡🚀
    podman-desktop.io/blog/podman- #PodmanQuadlets #PodmanDesktop #TechBuzzwords #SoftwareComplexity #DeveloperTools #HackerNews #ngated

  4. Ah yes, Podman Quadlets with Podman Desktop—because the world was simply crying out for yet another buzzword-laden tool to clog up your desktop. 🎉 Now you can drown in a sea of Podman releases, because who needs simplicity when you can have a convoluted mess? 🤡🚀
    podman-desktop.io/blog/podman- #PodmanQuadlets #PodmanDesktop #TechBuzzwords #SoftwareComplexity #DeveloperTools #HackerNews #ngated

  5. #SoftwarePerformance & #SoftwareComplexity are related! It's common for refactoring to introduce unexpected regressions, and performance optimizations often face tough code reviews.

    In this #InfoQ video, Richard Startin explores the recent enhancements to the Java String class and the intricate relationship between Complexity & Performance.

    Have you faced this trade-off? Watch now: bit.ly/4hhpGmq

    📄 #transcript included

    #Java

  6. #SoftwarePerformance & #SoftwareComplexity are related! It's common for refactoring to introduce unexpected regressions, and performance optimizations often face tough code reviews.

    In this #InfoQ video, Richard Startin explores the recent enhancements to the Java String class and the intricate relationship between Complexity & Performance.

    Have you faced this trade-off? Watch now: bit.ly/4hhpGmq

    📄 #transcript included

    #Java

  7. #SoftwarePerformance & #SoftwareComplexity are related! It's common for refactoring to introduce unexpected regressions, and performance optimizations often face tough code reviews.

    In this #InfoQ video, Richard Startin explores the recent enhancements to the Java String class and the intricate relationship between Complexity & Performance.

    Have you faced this trade-off? Watch now: bit.ly/4hhpGmq

    📄 #transcript included

    #Java

  8. #SoftwarePerformance & #SoftwareComplexity are related! It's common for refactoring to introduce unexpected regressions, and performance optimizations often face tough code reviews.

    In this #InfoQ video, Richard Startin explores the recent enhancements to the Java String class and the intricate relationship between Complexity & Performance.

    Have you faced this trade-off? Watch now: bit.ly/4hhpGmq

    📄 #transcript included

    #Java

  9. & are related! It's common for refactoring to introduce unexpected regressions, and performance optimizations often face tough code reviews.

    In this video, Richard Startin explores the recent enhancements to the Java String class and the intricate relationship between Complexity & Performance.

    Have you faced this trade-off? Watch now: bit.ly/4hhpGmq

    📄 included

  10. Corollary: If I have to grep your source code for the error message to find out what it is and where it's coming from, you need to rewrite that error message and add more #documentation.

    #Debugging #SoftwareComplexity

  11. Corollary: If I have to grep your source code for the error message to find out what it is and where it's coming from, you need to rewrite that error message and add more #documentation.

    #Debugging #SoftwareComplexity

  12. Corollary: If I have to grep your source code for the error message to find out what it is and where it's coming from, you need to rewrite that error message and add more #documentation.

    #Debugging #SoftwareComplexity

  13. Corollary: If I have to grep your source code for the error message to find out what it is and where it's coming from, you need to rewrite that error message and add more #documentation.

    #Debugging #SoftwareComplexity

  14. Corollary: If I have to grep your source code for the error message to find out what it is and where it's coming from, you need to rewrite that error message and add more #documentation.

    #Debugging #SoftwareComplexity

  15. If there's no search results for an error message that can happen in your software, there's not enough #documentation (or you have too many dependencies)

    (Sidenote, yes I checked other search engines, yes search engines suck)

    #Debugging #SoftwareComplexity

  16. If there's no search results for an error message that can happen in your software, there's not enough #documentation (or you have too many dependencies)

    (Sidenote, yes I checked other search engines, yes search engines suck)

    #Debugging #SoftwareComplexity

  17. If there's no search results for an error message that can happen in your software, there's not enough #documentation (or you have too many dependencies)

    (Sidenote, yes I checked other search engines, yes search engines suck)

    #Debugging #SoftwareComplexity

  18. If there's no search results for an error message that can happen in your software, there's not enough #documentation (or you have too many dependencies)

    (Sidenote, yes I checked other search engines, yes search engines suck)

    #Debugging #SoftwareComplexity

  19. If there's no search results for an error message that can happen in your software, there's not enough #documentation (or you have too many dependencies)

    (Sidenote, yes I checked other search engines, yes search engines suck)

    #Debugging #SoftwareComplexity

  20. If I have to use #strace to debug your software in the first place, you needed more logging and tracing (and it needed to be discoverable).

    #Debugging #SoftwareComplexity

  21. If I have to use #strace to debug your software in the first place, you needed more logging and tracing (and it needed to be discoverable).

    #Debugging #SoftwareComplexity

  22. If I have to use #strace to debug your software in the first place, you needed more logging and tracing (and it needed to be discoverable).

    #Debugging #SoftwareComplexity

  23. If I have to use #strace to debug your software in the first place, you needed more logging and tracing (and it needed to be discoverable).

    #Debugging #SoftwareComplexity

  24. If I have to use #strace to debug your software in the first place, you needed more logging and tracing (and it needed to be discoverable).

    #Debugging #SoftwareComplexity

  25. Okay, time for an Adam's Law of Software Complexity: if I can't work out which process to strace to debug your software, it's too complex.

    #Debugging #SoftwareComplexity

  26. Okay, time for an Adam's Law of Software Complexity: if I can't work out which process to strace to debug your software, it's too complex.

    #Debugging #SoftwareComplexity

  27. Okay, time for an Adam's Law of Software Complexity: if I can't work out which process to strace to debug your software, it's too complex.

    #Debugging #SoftwareComplexity

  28. Okay, time for an Adam's Law of Software Complexity: if I can't work out which process to strace to debug your software, it's too complex.

    #Debugging #SoftwareComplexity

  29. Okay, time for an Adam's Law of Software Complexity: if I can't work out which process to strace to debug your software, it's too complex.

    #Debugging #SoftwareComplexity