6 ms·

This is the perfect time to take a break. Kick back, have a coffee, contemplate your life choices. That commit can wait, that PR (i was about to merge) can wait

by harel 7y ago

This is the perfect time to take a break. Kick back, have a coffee, contemplate your life choices. That commit can wait, that PR (i was about to merge) can wait too. It's not the end of the world.

deleted 7y ago
[deleted]
dekhn 7y ago
well actually I spent the holiday weekend not working and now I have a time window to work with our east coast contractors before they stop work for the day (they don't work on the weekends or after 5PM) so having the system down isn't really end of the world but it will impact our productivity.
mattnewton 7y ago
Why not just keep working? That next commit will work just fine without a central server.
- dekhn 7y ago
  merging work with contractor right now...
  - mattnewton 7y ago
    That works too, believe it or not. Just add another remote and pull it.
    - dekhn 7y ago
      I only coordinate my remotes through github. I don't use git in "decentralized mode".
      - giggles_giggles 7y ago
        >
        hackmiester 7y ago
        A lot of people do that too.
      - darkpuma 7y ago
        That's not something you decide once at the beginning and get stuck with it. You can reevaluate that decision at any point and easily add more remotes to a git repo on the fly.
        dekhn 7y ago
        So, uh, it's not clear what exactly people are expecting me to do here. Wire up my repo to my contractors temporarily (not even sure how I'd do that as i don't have access to their machines or filesystems) then detach when github is back (it's already back)?
        darkpuma 7y ago
        A single repo can have many remotes. Adding additional remotes does not prevent you from also using old remotes, nor do you ever have to remove a remote that you intend on using again in the future. Obviously it's a moot point for you now, but getting comfortable with how git remotes works is something that could pay dividends for you in the future.
        dekhn 7y ago
        I have multiple remotes already and know how they work. What I'm asking is, if github is down, and I don't have ssh or other access to my contractor's repo on their machine, what is my remote supposed to attach to? Also, the additional effort to manage multiple remotes is entirely nontrivial.
- ilikehurdles 7y ago
  At some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and I can't submit a PR for review.
  - inflatableDodo 7y ago
    It should be easy to move the center. Having a single 3rd party be the only central point you have available is asking for trouble.
  - mbrumlow 7y ago
    But you could continue working and only have to apply minor patches forward if you later find your starting point needed to be fixed. You don't have to wait for CI, just create a new branch and continue your work as though CI passed, and your PR was accepted. If that comes true you don't need to worry much, just rebase and continue. On the other hand if you find out you needed to make changes - do those on the branch you made those changes, and finish your PR/CI cycle. Then go to the new branch you continued work on and rebase, and continue. Is there something I am missing?
    - zymhan 7y ago
      Heaven forbid we find a reason to take a break
      - deleted 7y ago
        [deleted]
      - jnbiche 7y ago
        In the old days at least we had compiling. Not so much anymore.
        tjoff 7y ago
        No, today we have something else to wait for, it is called the runtime.
- harel 7y ago
  Because we forget how to let go of all this work stuff and get sucked into it. There is a life out there too. some one us can balance, some find it hard. this is an opportunity to just pause for a few minutes. Mentally pause.
  - deleted 7y ago
    [deleted]
  - nickthemagicman 7y ago
    Right. There's an entire world out there of of personal projects and open source contributions you can be doing when not working. People get so caught up in their daily coding they forget about all the other fun coding they could be doing outside of work. It's a shame.
    - fwip 7y ago
      Or, not coding.
      - jstimpfle 7y ago
        I think there was a joke in there ;-)
        deleted 7y ago
        [deleted]
- rv-de 7y ago
  Of course, you know that, I know that, we all know it - but our bosses don't ;)
  - harel 7y ago
    They are living in the technical stone age then. Time on keyboard does not equate good productivity. Happiness, balance, freedom - that increases output.
- partiallypro 7y ago
  Because programmers always need a break. Don't go giving our bosses ammo. It's compiling, it's uploading, Github is down. Have some compassion.
bassman9000 7y ago
And reflect why keep using git when we still work the good ol' centralized workflow style of SVN and the likes.
deleted 7y ago
[deleted]

by harel 7y ago

This is the perfect time to take a break. Kick back, have a coffee, contemplate your life choices. That commit can wait, that PR (i was about to merge) can wait too. It's not the end of the world.

deleted 7y ago

[deleted]

dekhn 7y ago

well actually I spent the holiday weekend not working and now I have a time window to work with our east coast contractors before they stop work for the day (they don't work on the weekends or after 5PM) so having the system down isn't really end of the world but it will impact our productivity.

mattnewton 7y ago

Why not just keep working? That next commit will work just fine without a central server.

dekhn 7y ago
merging work with contractor right now...
- mattnewton 7y ago
  That works too, believe it or not. Just add another remote and pull it.
  - dekhn 7y ago
    I only coordinate my remotes through github. I don't use git in "decentralized mode".
    - giggles_giggles 7y ago
      >
      - hackmiester 7y ago
        A lot of people do that too.
    - darkpuma 7y ago
      That's not something you decide once at the beginning and get stuck with it. You can reevaluate that decision at any point and easily add more remotes to a git repo on the fly.
      - dekhn 7y ago
        So, uh, it's not clear what exactly people are expecting me to do here. Wire up my repo to my contractors temporarily (not even sure how I'd do that as i don't have access to their machines or filesystems) then detach when github is back (it's already back)?
        darkpuma 7y ago
        A single repo can have many remotes. Adding additional remotes does not prevent you from also using old remotes, nor do you ever have to remove a remote that you intend on using again in the future. Obviously it's a moot point for you now, but getting comfortable with how git remotes works is something that could pay dividends for you in the future.
        dekhn 7y ago
        I have multiple remotes already and know how they work. What I'm asking is, if github is down, and I don't have ssh or other access to my contractor's repo on their machine, what is my remote supposed to attach to? Also, the additional effort to manage multiple remotes is entirely nontrivial.
ilikehurdles 7y ago
At some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and I can't submit a PR for review.
- inflatableDodo 7y ago
  It should be easy to move the center. Having a single 3rd party be the only central point you have available is asking for trouble.
- mbrumlow 7y ago
  But you could continue working and only have to apply minor patches forward if you later find your starting point needed to be fixed. You don't have to wait for CI, just create a new branch and continue your work as though CI passed, and your PR was accepted. If that comes true you don't need to worry much, just rebase and continue. On the other hand if you find out you needed to make changes - do those on the branch you made those changes, and finish your PR/CI cycle. Then go to the new branch you continued work on and rebase, and continue. Is there something I am missing?
  - zymhan 7y ago
    Heaven forbid we find a reason to take a break
    - deleted 7y ago
      [deleted]
    - jnbiche 7y ago
      In the old days at least we had compiling. Not so much anymore.
      - tjoff 7y ago
        No, today we have something else to wait for, it is called the runtime.
harel 7y ago
Because we forget how to let go of all this work stuff and get sucked into it. There is a life out there too. some one us can balance, some find it hard. this is an opportunity to just pause for a few minutes. Mentally pause.
- deleted 7y ago
  [deleted]
- nickthemagicman 7y ago
  Right. There's an entire world out there of of personal projects and open source contributions you can be doing when not working. People get so caught up in their daily coding they forget about all the other fun coding they could be doing outside of work. It's a shame.
  - fwip 7y ago
    Or, not coding.
    - jstimpfle 7y ago
      I think there was a joke in there ;-)
      - deleted 7y ago
        [deleted]
rv-de 7y ago
Of course, you know that, I know that, we all know it - but our bosses don't ;)
- harel 7y ago
  They are living in the technical stone age then. Time on keyboard does not equate good productivity. Happiness, balance, freedom - that increases output.
partiallypro 7y ago
Because programmers always need a break. Don't go giving our bosses ammo. It's compiling, it's uploading, Github is down. Have some compassion.

bassman9000 7y ago

And reflect why keep using git when we still work the good ol' centralized workflow style of SVN and the likes.

deleted 7y ago

[deleted]