Yeah sorry, there is no other window.
I'm a nightowl too, so the early morning is not an option.
My sleep is definitely disrupted if I do it 2 hours before bed, but I haven't noticed issues with 4.
My fox said I had to get in better shape or I might get hurt. Started going to Crunch and doing some functional training and heavy lifting but Crunch is about as bad as the gym at my Uni when it comes to college students inhabiting the weight machines for too long. Fox said I didn't need more muscle mass but had to improve functional flexibility and get BMI down (ever see a fat fox?)
So I got a 35 lb kettlebell and a TRX system and do those things as well as VR workouts (some Beat Saber, might get back into Supernatural when I've exhausted the free trials of everyone else) around 8-9pm many nights, I usually got to bed around 10-11pm and sleep well. I think going for a hike is fine even as late as 9pm but I wouldn't want to be doing cardio or HIIT that late. Now that I think about it I oughta add some active isolated stretching with the bands.
So far as my fox is concerned [1] I know it puts a lot of stress on my hindquarters (wants to be pronograde?) and to express itself wants to use a range of postures and motion wider than I find comfortable. If I have to explain it to people who might be skeptical I just lie and say I am preparing for character acting in community theater.
Unfortunately I have kids school age, so I'm forced to go to bed by 11pm. During spring break it was pretty evident though, if I go to bed at 1 or 2 am and wake up at 11 am, I feel way more rested than if I go to bed at 10:45pm and wake up at 7:45am. Society really doesn't accommodate that
I can eat unlimited eggs and never feel full (hyperbole, but getting my point). 150g of fat plus a salad with lettuce, tomato and cottage cheese makes me full, which is something hard to achieve for me
I noticed I need high reflexes games to make my brain rest after work, so I don't agree.
It's really hard to shutdown after a day that required a lot of brain power, but high reflexes games do the trick (nine sols, hollow knight come to mind)
We keep saying this and forget that videogames started being sold digital, which saves about 30% on their retail cost, and avoids second market entirely, removing that "cost" too.
So of course videogames haven't gone up in price, companies started saving an enormous amount of money on videogames.
How do you put numbers in there usually?
I'm facing an issue at work where an important factor should be done to correct a serious design mistake, but it doesn't get in the way of any feature. It's probably the cause of a lot of loss of development time over the lifetime of the project, but I don physically know how much of a boost will it give to development.
I know it will, but I wouldn't feel comfortable without quantifying.
I have some rough idea for approaches to this, but would appreciate some external input as well
One way to communicate this is in terms of _schedule risk_, rather than straight-up lost productivity. E.g. for a particularly troublesome design flaw, you might estimate that for any given 4-week project there's a 20% risk of the project blowing out by an extra week due to that flaw.
Depending on the stakeholder(s) you're dealing with, approaching it like this (as risk assessment/management) might help to convey the short-term impact of a long-term problem.
It can be tough, and in some cases measurable numbers are hard to find. That can make prioritization hard.
It's worth keeping open the option that "now is not yet the right time".
One key way to understand the situation well is to explore both thd upsides and downsides of the issue. Its almost never an obvious decision and being acquainted with all points of view really helps both to figure out what is right, whether it's worth doing, if now is the right time, and so on.
If it was obviously necessary it would likely already have been done, so it may be necessary, but it might not yet be time.
Sometimes it comes down to groundwork. Finding out who us affected, and how. (And if you can't find those people, that's a clue too.)
Indeed, I was the one suggesting to not do the refactor because I couldn't find a reason.
Today at standup though, a task that would take 1 hour once the refactor is done, will probably take about 2 days instead, so i'm back thinking about it (the refactor would take longer than 2 days)
I only do small solo projects but the value from maintainable code depends on how often it needs to be updated.
If management comes with new [crazy] ideas and/or feature [cruft] every other week it should be easy to prefer a warehouse with ready to use components over a scrap yard. If you need a set of usable tires a few times per year the scrap yard will provide. If you need a set of tires 20 times per day you want at least 200 sets of each kind stored in a convenient place. You probably live some place in between.
edit: Also, timing is everything. Write down everything you want, add the pony. Wait for the right moment when their head is not raging with 50 deadlines.
Most important imho is to not want anything but explain what options they have. If they want faster results they might be able to get them by attacking the technical debt.
Make them up. If you're uncomfortable with this, ask ChatGPT to make them up for you. Most places don't have any real way to measure productivity or rate of feature delivery, so as long as you promise a reasonable number (5-10%) they have no way of contradicting you.
Incremental refactoring is also the other classic way to do this. Slip bits into other tickets until you've slowly dragged the ship around. But it's not always possible.
reply