4 ms·

I think the point the OPs was making is you cannot store up miles on Monday that you can then release Wednesday. You can with commits / stashes. And that dist

I think the point the OPs was making is you cannot store up miles on Monday that you can then release Wednesday. You can with commits / stashes. And that distorts behaviour

saagarjha 4y ago
You can definitely avoid going on longer runs with the intention that you’ll have an easier time tomorrow.
aliqot 4y ago
I don't think people actually do that though. Who'd do that? Who would you even be lying to, yourself?
- jfabre 4y ago
  Assuming your question wasn't sarcasm. Literally everyone lie to themselves about one thing or another... Including me, and probably including you.
  - lifeisstillgood 4y ago
    See House M.D. for details :-)
  - aliqot 4y ago
    I don't understand how it is possible to lie to myself. It requires you to suspend disbelief and say to yourself that something did or didn't happen, that's something I cannot fathom.
    - Avicebron 4y ago
      Lying to yourself doesn't necessarily require suspension of belief entirely, but convincing yourself whatever you are doing is worth you doing it. Since it's hard (probably impossible) to know the object truth of if something is " right" or not. Then it becomes fairly easy to justify anything, im sure you've done this even if you don't know exactly how to admit it or don't think you're doing it consciouly.
    - a1445c8b 4y ago
      > I don't understand how it is possible to lie to myself. It’s called bias and its various types.
- peanut_merchant 4y ago
  Potentially, the people responsible for deciding your salary. Even without gamefication I am guilty of storing up commits on "productive" days because I am conscious I may not have the same output the next day.
  - aliqot 4y ago
    > Potentially, the people responsible for deciding your salary. Yikes, yeah I forget some people have that type of workplace that isn't necessarily result driven. If that is the case and does get someone escorted at least there's a chance they'll end up somewhere more engaging.
jrumbut 4y ago
But you can also be motivated by a streak and do work you wouldn't have otherwise done. Personally I find streaks are powerful motivators. If this were going to affect my work negatively it would probably be something like "not resting adequately."
- lifeisstillgood 4y ago
  Yeah but what if the streak that motivated you was now "improved" - your annual bonus now depended on keeping that streak. You would be foolish to not have a little dry powder in your stashes. Maybe get a week or so ahead and commit fixes from 5 days back, so that if you hit a gnarly bug today you have five days to fix it for real and your streak is not affected. There is no simple metric for "doing quality work" and any management that is not "i will sit down and read the code and understand it" is not real management. And this does not scale. And so quality, creative work does not scale. Hence clusters. And senior staff engineers. Oh and btw, staff engineers are the executives in software lead companies. any non-coding layers on top should be viewed as financiers - with some interesting organisational implications

I think the point the OPs was making is you cannot store up miles on Monday that you can then release Wednesday. You can with commits / stashes. And that distorts behaviour

saagarjha 4y ago

You can definitely avoid going on longer runs with the intention that you’ll have an easier time tomorrow.

aliqot 4y ago

I don't think people actually do that though. Who'd do that? Who would you even be lying to, yourself?

jfabre 4y ago
Assuming your question wasn't sarcasm. Literally everyone lie to themselves about one thing or another... Including me, and probably including you.
- lifeisstillgood 4y ago
  See House M.D. for details :-)
- aliqot 4y ago
  I don't understand how it is possible to lie to myself. It requires you to suspend disbelief and say to yourself that something did or didn't happen, that's something I cannot fathom.
  - Avicebron 4y ago
    Lying to yourself doesn't necessarily require suspension of belief entirely, but convincing yourself whatever you are doing is worth you doing it. Since it's hard (probably impossible) to know the object truth of if something is " right" or not. Then it becomes fairly easy to justify anything, im sure you've done this even if you don't know exactly how to admit it or don't think you're doing it consciouly.
  - a1445c8b 4y ago
    > I don't understand how it is possible to lie to myself. It’s called bias and its various types.
peanut_merchant 4y ago
Potentially, the people responsible for deciding your salary. Even without gamefication I am guilty of storing up commits on "productive" days because I am conscious I may not have the same output the next day.
- aliqot 4y ago
  > Potentially, the people responsible for deciding your salary. Yikes, yeah I forget some people have that type of workplace that isn't necessarily result driven. If that is the case and does get someone escorted at least there's a chance they'll end up somewhere more engaging.

jrumbut 4y ago

But you can also be motivated by a streak and do work you wouldn't have otherwise done. Personally I find streaks are powerful motivators. If this were going to affect my work negatively it would probably be something like "not resting adequately."

lifeisstillgood 4y ago
Yeah but what if the streak that motivated you was now "improved" - your annual bonus now depended on keeping that streak. You would be foolish to not have a little dry powder in your stashes. Maybe get a week or so ahead and commit fixes from 5 days back, so that if you hit a gnarly bug today you have five days to fix it for real and your streak is not affected. There is no simple metric for "doing quality work" and any management that is not "i will sit down and read the code and understand it" is not real management. And this does not scale. And so quality, creative work does not scale. Hence clusters. And senior staff engineers. Oh and btw, staff engineers are the executives in software lead companies. any non-coding layers on top should be viewed as financiers - with some interesting organisational implications