Yes the inclusion of children does change things, in that it makes choosing red even more obvious.
The problem is posed to the world. You have children, and they ask you what they should do. You tell them to pick red because you're their parent you can't bring yourself to have them risk their lives for some noble purpose.
According to blue buttoners, this parent is an evil person, right?
What if you entertain the variant of the question where a percentage of red votes die in the event of a blue win? It makes pressing red less advantageous, but also it totally changes the moral balance depending on the percentage.
I think this is already baked in. A world of red pressers must know they’ll adapt to a shortage of things produced by blue pressers. Many red pressers won’t survive.
> But if you want to generate power, you need to get down to where temperatures can boil water.
Why is that the case? Can't you go down to where it's like 70-80 deg C and close the gap using heat pumps? Yes, you need to put some energy in, but I would expect that the whole process would still be energy-positive at some temperature that's lower than 100C?
The predominance of these idioms as a way to zero out a register led Intel to add special xor r, r-detection and sub r, r-detection in the instruction decoding front-end and rename the destination to an internal zero register, bypassing the execution of the instruction entirely.
AFAIK it's the same in the USA, that's why one of the first questions when interviewing with a company is to ask them about their moonlighting policy if you do want to work on a side project.
It varies by state in the USA. Some states have strong protections for work you do "on your own time, on your own equipment, that isn't connected to your work." Others, not so much...
There's no extension support for Chrome on Android. There's no way to stop Chrome on Android from hiding the address bar when scrolling. Those were mine, not sure if they still apply.
The extensions are of course one of my reasons for using Firefox. I'm occasionally mildly annoyed by the auto-hiding address bar, but didn't know that it's configurable, so thanks - I've changed the setting!
But you are specifying source files, although indirectly, aren't you? That's what all those `mod blah` with a corresponding `blah.rs` file present in the correct location are.
Yes and no. You're right that the mod declarations are necessary, but I'd argue that this is actually more direct (it's happening in the code, not in some external build file), and that you still aren't actually choosing where the file is located as much as stating that it's present, since you don't have the ability to look for `mod foo` in an arbitrary location, but only the places that the tooling already expects to find it.
My wife started with wearing one mould for 7 days and went down to one mould for 4 days near the end of the treatment (but the orthodontist knew we wanted to move and may have accelerated the schedule). She started wearing them at ~36. She says they told her it may be up to 2 weeks per mould before she started the treatment but that wasn't the case for her.
I'm in the camp of liking Windows and having had to put up with Linux and MacOS for work. Inertia and familiarity does play a role, but as a dev there are things I really like (ETW + WinDbg immediately come to mind) & really miss on other OSes. I'm not there yet to join an enthusiast group though. ;)
How do you plan to show up on time if one of your meetings ends at 2pm, the next one starts at 2pm, the meeting rooms are 3 floors apart, and you need to go to the restroom because you've been in meetings since lunch and need to pee? You're going to clone yourself?
Tell the people in the first meeting at the start that you’ll need to leave a few minutes early, to set the expectation and make sure any important stuff is done early. Then when it hits your transition window, politely tell them you have to run and leave.
The thing is, a lot of meetings start with presenting evidence of a problem, then have some discussion of the problem and potential options, and only in the last 10 minutes do the proposed actions turn into firm decisions with names against them.
And often if I'm in a meeting it's because I think the problem is important and I want it solved. Getting permission for my team to fix things, or getting other teams to agree to fix things, is the point.
In my experience, this is a time management problem. Meetings tend to fill the time available. Rarely are there meetings that have to last a full hour and could not have been over after 50 minutes.
Or what makes 60 minutes so magical that you can wrap up a meeting quickly once that marker approaches? People need to leave, that's why. If it had been clear from the start that people will leave after 50 minutes, you can wrap up by then, same way you wrap things up at 60.
There is a lot of slack in meetings. What you need is someone to manage the available time and move things along, make sure that there is room at the end to get to a conclusion. You will have these last 10 minutes after 40 minutes instead of 50 if you pay attention to time and keep things moving.
This can be done, even with time to spare for pleasantries. I know this because I've been in meetings and I have run meetings like this. It helps if you can start on time and don't have to wait for stragglers in the beginning who needed a break between their back-to-back meetings.
I'd rather have a 5-minute break built-in for everyone by starting 5-past and actually enforce meeting end-times. Behaviors would change if people knew they had 25 or 55 minutes for a meeting and that folks would just leave when the time is up.
Seen from within the meeting, it does not really matter if you start 5 minutes late or end 5 minutes early.
I think the point is to reduce meeting time from 60 minutes to 55 or even 50 and be firm about it. People need to expect to start and end on time; giving them a natural break between helps make this happen even for people whose job requires them to be in back-to-back meetings.
Personally, I think starting on the hour (or half-hour, etc) and ending "early" is better, because it tends to sync well with the calendars of external folks.
But in the end, moving start or end time is only part of the solution. This is a time-management problem, and in addition to constraining the available time, it also needs proper management of the available time within the meeting.
> Seen from within the meeting, it does not really matter if you start 5 minutes late or end 5 minutes early.
It matters because there sometimes are meeting where it is very important to know how much time you have to prepare appropriately. As long as the expectations are set beforehand, it matters less.
I roughly agree with the rest of your post. "Just be punctual" is a cop out that ignores the fact that I need to have enough breaks between meetings before I can even think about being punctual. Make space for breaks and enforce the time allocated is imo the solution, it matters less where exactly the 5-minute break fits (but I tend to agree that people would more likely end on the full hour, so that would mean we need to start 5 past).
