• non_burglar@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    15 hours ago

    This is neat, and I see that lots of folks are getting a good look at their laid out setup costs. However, you should stop using project management budget coding words. Also:

    1. You are confusing roi with payback period.
    2. There are intangible factors to consider like command of your data, control over security, etc.
    3. Opex and capex are values used for fixed-term projects, they aren’t meant to quantify ongoing efforts past project outset.
    4. Hardware is absolutely NOT a “one-time purchase”. If you are amortizing the cost of equipment, you must include projected failure rates, particularly for disks. Please refer to green-cycling.
    5. Information projects are different than physical processing projects because they “expire”, meaning your i5-7200 is OK now, but will likely be nearly useless in 2030 when everyone is pretty much moved to 4k.
    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      Well it’s a pretty good start (and I do agree with you on using the appropriate terminology). I’ve had to look at it differently and use it with the ideas only head being misrepresented on screen. Still the idea is great.

      Sounds like you’d be a great co-conspirator for OP to really make this project exceptional.

      • non_burglar@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        Jeez, i re-read my answer and I always come across more severe than I wanted.

        It’s definitely a good milestone for someone potentially getting carried away with buying gear, if only to stop and figure out what one is trying to accomplish. And I say this as a person who worked in it for 25 yrs and has waaay too much gear.