schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Search results for tag #Refactoring

[?]Nat Pryce » 🌐
@natpryce@mastodon.social

Expand/Contract: a strategy to avoid disrupting work in progress by other team members, or to avoid breaking clients during zero-downtime deployments.

Expand/Contract illustrated by an old black-and-white photograph of accordion players.

The Expand/Contract refactoring strategy is:

1. Add new features
2. Migrate code to use the new features
3. Remove old features when is safe to do so

Alt...Expand/Contract illustrated by an old black-and-white photograph of accordion players. The Expand/Contract refactoring strategy is: 1. Add new features 2. Migrate code to use the new features 3. Remove old features when is safe to do so

    Jason Gorman boosted

    [?]Nat Pryce » 🌐
    @natpryce@mastodon.social

    To refactor a system from an object-oriented design to a functional design, we adopt a strategy of moving actions to the edge of the system, leaving the application domain model as immutable data and pure calculations.

    We are using the terminology of "data", "calculations", and "actions" from the book "Grokking Simplicity" by Eric Normand.

    In our workshop we work through different refactoring techniques to move actions to the edge of the system.

    Nested hexagons representing the hexagonal architecture, with an arrow labelled "actions" pointing from the center to the edge.  The core hexagon representing the application domain model is labeled "Calculations & Data".

    Alt...Nested hexagons representing the hexagonal architecture, with an arrow labelled "actions" pointing from the center to the edge. The core hexagon representing the application domain model is labeled "Calculations & Data".

      Ted M. Young boosted

      [?]Nat Pryce » 🌐
      @natpryce@mastodon.social

      Duncan and I will be at UK on June 18th and will use some of these practices to take control of LLM-generated code. LLMs default to generating code that is monolithic, procedural, and makes wide use of mutable state. is a good way to give the LLM patterns to follow. Separating actions from data & calculations, composing calculations, and proving consistency by type checking, are all good strategies to keep generated code comprehensible by humans.

      socratesuk.org/training_day.ht

        #refactoring boosted

        [?]Leanpub » 🌐
        @leanpub@mastodon.social

        A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $6.50! leanpub.com/naming_shortguide

          #refactoring boosted

          [?]Frontend Dogma » 🤖 🌐
          @frontenddogma@mas.to

          #refactoring boosted

          [?]Leanpub » 🌐
          @leanpub@mastodon.social

          A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $6.50! leanpub.com/naming_shortguide

            #refactoring boosted

            [?]Frontend Dogma » 🤖 🌐
            @frontenddogma@mas.to

            #refactoring boosted

            [?]Leanpub » 🌐
            @leanpub@mastodon.social

            A Short Guide to Naming: Understand how and why to better name modules, classes, functions, and variables. by Tim Ottinger is the featured book 📖 on Leanpub!

            if you've read my chapter on naming in a famous software book (first or second edition) you may want to go a little deeper. Same author, same topic, all-new content!

            Link: leanpub.com/naming_shortguide

              #refactoring boosted

              [?]Leanpub » 🌐
              @leanpub@mastodon.social

              A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $5.00! leanpub.com/naming_shortguide

                #refactoring boosted

                [?]N-gated Hacker News » 🤖 🌐
                @ngate@mastodon.social

                🤦‍♂️ Oh, joy! Another thrilling 12-minute treatise on code complexity that rivals a calculus textbook in zest. Apparently, if you throw enough fancy terms like Cyclomatic and Halstead at your spaghetti, it suddenly becomes gourmet 🤔👌. Who knew held the key to nightmares? 🍝🔍
                philodev.one/posts/2026-04-cod

                  8 ★ 4 ↺
                  kabel42 :LowSpoons: boosted

                  [?]Amitai Schleier [he/they] » 🌐
                  @schmonz@schmonz.com

                  It’s hard to fix something because it’s easy to break something else?

                  That’s your clue: refactor first.

                  (Special case of the general KFB wisdom “First make the change easy, then make the easy change.”)