home.social

#codedesign — Public Fediverse posts

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

  1. 🚀 Now showing test coverage directly in class diagrams.

    No more guessing what's tested — it's all visual, right where you design.

    #DevTools #DX #TestCoverage #CodeDesign

  2. 🚀 Now showing test coverage directly in class diagrams.

    No more guessing what's tested — it's all visual, right where you design.

    #DevTools #DX #TestCoverage #CodeDesign

  3. small piece on refactoring messy "god objects" in our old project:
    dev.to/janmpeterka/concerning-

    it's fun to write about what I do, even if it's possibly more of a journal for me than something people really read.

    #rails #codedesign #poodr

  4. small piece on refactoring messy "god objects" in our old project:
    dev.to/janmpeterka/concerning-

    it's fun to write about what I do, even if it's possibly more of a journal for me than something people really read.

    #rails #codedesign #poodr

  5. small piece on refactoring messy "god objects" in our old project:
    dev.to/janmpeterka/concerning-

    it's fun to write about what I do, even if it's possibly more of a journal for me than something people really read.

    #rails #codedesign #poodr

  6. small piece on refactoring messy "god objects" in our old project:
    dev.to/janmpeterka/concerning-

    it's fun to write about what I do, even if it's possibly more of a journal for me than something people really read.

    #rails #codedesign #poodr

  7. small piece on refactoring messy "god objects" in our old project:
    dev.to/janmpeterka/concerning-

    it's fun to write about what I do, even if it's possibly more of a journal for me than something people really read.

    #rails #codedesign #poodr

  8. Java's final classes stifling innovation

    I wanted to extend Optional for seamless integration of my TypeMap library. Fluent, functional, and reflection-free. But nope, Optional is final. Now I’m stuck recreating and syncing its methods manually. Final or Private classes don’t prevent misuse, they block creativity and create more mess when copying functionalities. I love final, but not on classes.
    TypeMap: github.com/YunaBraska/type-map

    #Java #Programming #Optional #FinalClass #CodeProblems #DevLife #TypeSafe #InnovationBlocked #FunctionalProgramming #CodeDesign

  9. Java's final classes stifling innovation

    I wanted to extend Optional for seamless integration of my TypeMap library. Fluent, functional, and reflection-free. But nope, Optional is final. Now I’m stuck recreating and syncing its methods manually. Final or Private classes don’t prevent misuse, they block creativity and create more mess when copying functionalities. I love final, but not on classes.
    TypeMap: github.com/YunaBraska/type-map

  10. Java's final classes stifling innovation

    I wanted to extend Optional for seamless integration of my TypeMap library. Fluent, functional, and reflection-free. But nope, Optional is final. Now I’m stuck recreating and syncing its methods manually. Final or Private classes don’t prevent misuse, they block creativity and create more mess when copying functionalities. I love final, but not on classes.
    TypeMap: github.com/YunaBraska/type-map

    #Java #Programming #Optional #FinalClass #CodeProblems #DevLife #TypeSafe #InnovationBlocked #FunctionalProgramming #CodeDesign

  11. Java's final classes stifling innovation

    I wanted to extend Optional for seamless integration of my TypeMap library. Fluent, functional, and reflection-free. But nope, Optional is final. Now I’m stuck recreating and syncing its methods manually. Final or Private classes don’t prevent misuse, they block creativity and create more mess when copying functionalities. I love final, but not on classes.
    TypeMap: github.com/YunaBraska/type-map

    #Java #Programming #Optional #FinalClass #CodeProblems #DevLife #TypeSafe #InnovationBlocked #FunctionalProgramming #CodeDesign

  12. I read a question that I quickly replied to, but I wanted to expand on my recommendation

    #Ruby #Pattern #Return #CodeDesign

    What I will share here is an exploration and a proposal about how I think we can improve it:

  13. I read a question that I quickly replied to, but I wanted to expand on my recommendation

    #Ruby #Pattern #Return #CodeDesign

    What I will share here is an exploration and a proposal about how I think we can improve it:

  14. I read a question that I quickly replied to, but I wanted to expand on my recommendation

    #Ruby #Pattern #Return #CodeDesign

    What I will share here is an exploration and a proposal about how I think we can improve it:

  15. I read a question that I quickly replied to, but I wanted to expand on my recommendation

    #Ruby #Pattern #Return #CodeDesign

    What I will share here is an exploration and a proposal about how I think we can improve it:

  16. I read a question that I quickly replied to, but I wanted to expand on my recommendation

    #Ruby #Pattern #Return #CodeDesign

    What I will share here is an exploration and a proposal about how I think we can improve it:

  17. Quite nice examples about the problems over-engineering and how to better design future-proof code.

    «Don’t overgeneralize or abstract too much too soon. It’s great to solve today’s problems and allow for future growth. But trying to predict every future scenario can backfire.»

    16elt.com/2024/09/07/future-pr
    #SoftwareEngineering #architecture #codeDesign

  18. Quite nice examples about the problems over-engineering and how to better design future-proof code.

    «Don’t overgeneralize or abstract too much too soon. It’s great to solve today’s problems and allow for future growth. But trying to predict every future scenario can backfire.»

    16elt.com/2024/09/07/future-pr
    #SoftwareEngineering #architecture #codeDesign

  19. Quite nice examples about the problems over-engineering and how to better design future-proof code.

    «Don’t overgeneralize or abstract too much too soon. It’s great to solve today’s problems and allow for future growth. But trying to predict every future scenario can backfire.»

    16elt.com/2024/09/07/future-pr
    #SoftwareEngineering #architecture #codeDesign

  20. Quite nice examples about the problems over-engineering and how to better design future-proof code.

    «Don’t overgeneralize or abstract too much too soon. It’s great to solve today’s problems and allow for future growth. But trying to predict every future scenario can backfire.»

    16elt.com/2024/09/07/future-pr
    #SoftwareEngineering #architecture #codeDesign

  21. Quite nice examples about the problems over-engineering and how to better design future-proof code.

    «Don’t overgeneralize or abstract too much too soon. It’s great to solve today’s problems and allow for future growth. But trying to predict every future scenario can backfire.»

    16elt.com/2024/09/07/future-pr
    #SoftwareEngineering #architecture #codeDesign

  22. «Let’s take a look at the ideas behind the design of a small number of the major programming languages. We will start with the oldest languages first because later languages were strongly influenced by these earlier ones and their design philosophies—understanding these “proto” languages will allow you to better understand the modern languages that followed.»

    welcometothejungle.com/es/arti

    #SoftwareEngineering #history #codeDesign

  23. «Let’s take a look at the ideas behind the design of a small number of the major programming languages. We will start with the oldest languages first because later languages were strongly influenced by these earlier ones and their design philosophies—understanding these “proto” languages will allow you to better understand the modern languages that followed.»

    welcometothejungle.com/es/arti

    #SoftwareEngineering #history #codeDesign

  24. «Errors need to propagate upwards from the lowest layers of the software stack to the highest, and as they do so, the error object needs to be transformed: low-level errors get translated into high-level errors that the user can understand, often by adding additional context information. This works because each layer of the software stack that the error rises through understands the context of the current operation, even if the layers below it do not.»

    medium.com/machine-words/a-few

    #codeDesign

  25. «Errors need to propagate upwards from the lowest layers of the software stack to the highest, and as they do so, the error object needs to be transformed: low-level errors get translated into high-level errors that the user can understand, often by adding additional context information. This works because each layer of the software stack that the error rises through understands the context of the current operation, even if the layers below it do not.»

    medium.com/machine-words/a-few

    #codeDesign

  26. 📢 PaperMod now adopts Hugo's syntax highlighting using chromastyles by default 🪅

    Experience enhanced code readability and aesthetics! 🎨✨

    github.com/adityatelange/hugo-

    #PaperMod #Hugo #SyntaxHighlighting #CodeDesign

  27. 📢 PaperMod now adopts Hugo's syntax highlighting using chromastyles by default 🪅

    Experience enhanced code readability and aesthetics! 🎨✨

    github.com/adityatelange/hugo-

    #PaperMod #Hugo #SyntaxHighlighting #CodeDesign

  28. 📢 PaperMod now adopts Hugo's syntax highlighting using chromastyles by default 🪅

    Experience enhanced code readability and aesthetics! 🎨✨

    github.com/adityatelange/hugo-

    #PaperMod #Hugo #SyntaxHighlighting #CodeDesign

  29. 📢 PaperMod now adopts Hugo's syntax highlighting using chromastyles by default 🪅

    Experience enhanced code readability and aesthetics! 🎨✨

    github.com/adityatelange/hugo-

    #PaperMod #Hugo #SyntaxHighlighting #CodeDesign

  30. I just completed a two hour long #chat with #openai (it's free) about some #CodeDesign issue I was stuck with and it's the perfect rubber duck tool.

    It basically explained that I wanted a DSL (Domain specific language) instead of a rule engine (that was turning in a script engine) and then we continued the discussion with where the boundaries should be.

    #programming #architecture #code

  31. I just completed a two hour long #chat with #openai (it's free) about some #CodeDesign issue I was stuck with and it's the perfect rubber duck tool.

    It basically explained that I wanted a DSL (Domain specific language) instead of a rule engine (that was turning in a script engine) and then we continued the discussion with where the boundaries should be.

    #programming #architecture #code

  32. I just completed a two hour long #chat with #openai (it's free) about some #CodeDesign issue I was stuck with and it's the perfect rubber duck tool.

    It basically explained that I wanted a DSL (Domain specific language) instead of a rule engine (that was turning in a script engine) and then we continued the discussion with where the boundaries should be.

    #programming #architecture #code

  33. I just completed a two hour long #chat with #openai (it's free) about some #CodeDesign issue I was stuck with and it's the perfect rubber duck tool.

    It basically explained that I wanted a DSL (Domain specific language) instead of a rule engine (that was turning in a script engine) and then we continued the discussion with where the boundaries should be.

    #programming #architecture #code

  34. I just completed a two hour long #chat with #openai (it's free) about some #CodeDesign issue I was stuck with and it's the perfect rubber duck tool.

    It basically explained that I wanted a DSL (Domain specific language) instead of a rule engine (that was turning in a script engine) and then we continued the discussion with where the boundaries should be.

    #programming #architecture #code