It's all about finding a routine and following it as closely as possible, and adapting as needed. For me, it's at night when everyone is asleep.

Family is the most important. Cherish every moment. Reflect on those cherished moments. Time is but a fleeting thing.

Do you have a source for this equation or did you derive this yourself?

Another thing to note here that I have experienced is when management has an incompetent mentality that, for a given project, that all tasks for this project are created equal. For example, they expect that if task X took 1 hour that surely task Y will also take 1 hour despite the fact that task X and task Y vary greatly in complexity.

Explaining the difference in complexity helps, but the problem is that often the programmer doesn't really know in detail besides a feeling that comes mostly from many years of experience. And the best thing is if they then get 'their 10x code slinger' who does it indeed very fast, sends the code back to you and you are stuck with something akin to a broken toilet with diarrhea coming out the sides.

True. But it does no good if management is dismissive. But that's another problem outside of the topic of estimating.

> And the best thing is if they then get 'their 10x code slinger' who does it indeed very fast, sends the code back to you and you are stuck with something akin to a broken toilet with diarrhea coming out the sides

A grim picture to think about but I find this to be true a lot of the time.

I always have trouble explaining that it took a week to implement 90 percent of the whole project but then it took another 4 weeks to figure out why some little feature failed sometimes. That's my problem with scrum and velocity numbers. It gives clueless people the illusion that they can estimate everything easily.

I would definitely be interested in this as well.

Out of curiosity, was there any particular reason why you decided to write a blog post about this vulnerability 5 months after the bug was fixed?

I wanted to move from Blogspot to a personal domain, but kept delaying it for a long time.

Currently, most of the links within this thread are becoming rabbit holes for me.

I try to follow this mantra from Kent Beck: "Make it work. Make it right. Make it fast."

I find that most of the development environments that I have worked in, the focus usually ends up being on getting new features completed in order to help facilitate the sales department to make sales. It's a never-ending cycle that will gradually accumulate technical debt such that pushing new features out the door will eventually come to a halt.

Yes, I agree that code can never truly be perfect. However, as developers we should always strive to make our code better.

Since when do you have to be productive when hanging out with friends?

Not productive, value. Hanging out with the same people, doing the same thing and having the same conversations. I try to push for new and interesting and a small subset of friends are stagnant people. It's hard to want to spend time with them any more.

Good point.

Not sure if this has anything to do with it but by default, "Use relay server when required" is checked for each folder you share. But I would hope that it doesn't go through a relay server all the time.

I wonder how this will affect Space Monkey. Thoughts?