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

#refactoring boosted

[?]Michael K. Laweh (Klytron) » 🌐
@klytron@mastodon.social

Is your codebase a ticking time bomb? 💣

    #refactoring boosted

    [?]Nebraska.Code » 🌐
    @NebraskaCode@mastodon.social

    #refactoring boosted

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

    #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

      [?]Habr » 🤖 🌐
      @habr@zhub.link

      Как мы мигрируем навигацию на Compose в Android-приложениях с 400+ экранами

      Привет, Хабр! Меня зовут Константин Дубинко, я — Android-техлид в hh.ru . Сейчас мы заканчиваем большой переезд навигации в двух Android-приложениях — для соискателей и работодателей. В этой статье я покажу, как у нас там устроена навигация, почему мы решили отказаться от Fragment-навигации и как превратили хаотичную миграцию с «островками» новой архитектуры в управляемый процесс с метриками и понятным планом работ. Заодно расскажу, какие решения сработали, какие — нет, и что я сделал бы иначе, если бы начинал заново.

      habr.com/ru/companies/hh/artic

        #refactoring boosted

        [?]Nebraska.Code » 🌐
        @NebraskaCode@mastodon.social

        🗺️ Refactoring doesn't have to feel overwhelming.

        Joshua Holland shares at Nebraska.Code() how the Mikado Method helps teams uncover dependencies, plan incremental improvements, and safely tackle technical debt in complex codebases.

        nebraskacode.amegala.com/

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

          "The Switcheroo" - a combo that transforms an API *and its call sites* across the codebase.

          A picture of a swiss army knife opened so that all of its blades and tools are visible.

A description of the "Switcheroo" refactoring combo:

1. Extract the entire body of the function into a new function.
2. Refactor the extracted function to have the API you want and the body of the old function to be how you want it to be invoked across the codebase.
3. Inline the old function:
everywhere is now using the new API.

          Alt...A picture of a swiss army knife opened so that all of its blades and tools are visible. A description of the "Switcheroo" refactoring combo: 1. Extract the entire body of the function into a new function. 2. Refactor the extracted function to have the API you want and the body of the old function to be how you want it to be invoked across the codebase. 3. Inline the old function: everywhere is now using the new API.

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

            Four scales of , defined by how difficult it is to disseminate the change beyond an individual developer's workspace, and therefore whether you need to align on a refactoring *strategy*.

            Single commit:
- Affects a single codebase and built artefact.
- Applied by one atomic commit.

Multiple commits:
- Creates wide-spread change in a single codebase and built artefact.
- Use Expand/Contract to minimise disruption to other team members.

Multiple deployments:
- Cannot change all affected code in a single commit without breaking the system.
- Requires multiple deployments with Expand/Contract to avoid downtime.
- Delivery rate affects internal quality

Multiple releases:
- Requires Expand/Contract across multiple organisations to avoid breaking clients
- Must meet contractual obligations with respect to API stability and evolution

            Alt...Single commit: - Affects a single codebase and built artefact. - Applied by one atomic commit. Multiple commits: - Creates wide-spread change in a single codebase and built artefact. - Use Expand/Contract to minimise disruption to other team members. Multiple deployments: - Cannot change all affected code in a single commit without breaking the system. - Requires multiple deployments with Expand/Contract to avoid downtime. - Delivery rate affects internal quality Multiple releases: - Requires Expand/Contract across multiple organisations to avoid breaking clients - Must meet contractual obligations with respect to API stability and evolution

              [?]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

                      [?]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

                        [?]Nebraska.Code » 🌐
                        @NebraskaCode@mastodon.social

                        #refactoring boosted

                        [?]Jürgen » 🌐
                        @elbosso@mastodon.social

                        läuft: heute am rechner- backups gemacht, aufgeräumt, Ticket mit Nummer 3xx abgeschlossen (aktuell ist fast 1900), API ganz tief drin in und grundlegend umgestaltet (großes ) und trotzdem funktioniert noch alles! Plan für die nächsten änderungen genau wie die restlichen it Projekte aufgeschrieben, Einkaufsliste für morgen früh ist auch fertig, plan für den Garten ist fertig und dann war ich heute noch ein wenig betreiben...

                          #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

                              Back to top - More...