• malloc@programming.dev
    16·
    11 months ago

    In consulting, that’s called “after work”. Got to pump those billables

    Honestly though, unless it’s a feature that is completely outside the domain of the application. If you have to re-write your entire app then your app was probably dog shit to begin with

    • Doc Avid Mornington@midwest.socialEnglish
      6·
      11 months ago

      To be fair, it said “an enormous amount of code”, not “your entire app”, but yes, the ability to add unexpected new features or make focused changes without touching more than a minimal amount of existing code is a very good smell metric of code quality. The problem is that for every dev who understands how to program like that, there are at least five, probably more like ten who don’t, which means most of us are working on teams that produce a blend of clean code and, as you say, dog shit, so the feature request that requires stirring up all that shit is out there waiting for us, like it or not. The best we can do, when it hits, is try to at least improve all the shit that we touch in the process. Maybe some of it can become compost, I dunno, the metaphor breaks there, gonna have to refactor the metaphor.

  • douglasg14b@programming.dev
    14·
    11 months ago

    If you do this enough you know how to design your solutions to be relatively flexible. At least for your backends.

    Your frontend will always churn, that’s the nature of the job.

    • vivadanang@lemm.ee
      9·
      11 months ago

      Your frontend will always churn, that’s the nature of the job.

      Yep. The trick is to be gone before anyone finds the gross stuff needed to make it all work.

  • fsxylo@sh.itjust.worksEnglish
    12·
    11 months ago

    It’s a good thing I’m a hobbyist so that I can avoi- hmm, now that I think about it this feature could be really cool and shouldn’t take too long to implement…

  • Sigh_Bafanada@lemmy.world
    8·
    11 months ago

    We just need to change one field into an array, so that users can be linked to more than one location.

    We estimate around 400 hours work.

    • vivadanang@lemm.ee
      4·
      11 months ago

      We estimate around 400 hours work-

      In order to analyze the problem, inform stakeholders and a allow for a brief period for outlining the next potential steps to be decided by the steering committee. Once there, we can talk about allocating developer hours to enabling the resolution and it’s required upgraded dependencies. See my previous estimate sent 2/7/2018.

      • sip@programming.dev
        1·
        11 months ago

        yea, but it stops being fun when they say it’s a bug and it’s always supposed to work like that.

        • jet@hackertalks.comEnglish
          1·
          11 months ago

          Then it’s a valuable lesson in writing your client contracts and your work change order templates.

          If you bid per project you need to have clear milestones and sign-offs. If you bill per hour then it’s not issue.

  • Naomikho@monyet.cc
    2·
    11 months ago

    This literally happened in my meeting last week. Top position development manager was complaining the existing thing was shit. Basically means we have to build a new thing from scratch. And guess what? The deadline is 12 Sep.

    If you think it was shit why did you let them do what they did in the past?