What an excellent resource! (And yes Outlook is a pain and supports so very little!)
We've tried building email templates for notifications for our apps where I work, and it has typically been a pain. We have since swapped to using mjml (https://mjml.io/) to build the templates, and it's working wonders. The output seems the be the most compatible with all different devices that we've tested on.
The other tool we enjoy using is Litmus (https://litmus.com), which allows you to throw in an email template and see what it looks like on all kinds of apps and devices. Other thread here mentions https://testi.at/ as well, which we've also had success with.
All of these have been really invaluable to designing emails for our apps.
Shout out to https://virt-manager.org/ - works much better for me, supports running qemu on remote systems via ssh. I used to use this all the time for managing bunches of disparate vm hosts and local vms.
Maybe I’m oversimplifying, but in my experience the most effective reward for extra work is extra time. If somebody that works for me has to work a weekend to hit some objective, I thank them and tell them to take 2 days off the following week.
A parallel comment mentioned burnout, and I think this is the only viable way to enable above-and-beyond surges while minimizing burnout risk: as a business, you have to decide that a surge doesn’t mean you’re getting extra time from people, you’re borrowing time forward against future days.
At my job we can either get paid hours worked overtime or "bank" those hours to use as PTO later in the year. Unused banked time at the end of the year gets paid out. I've (thankfully) never had to work overtime but it's a pretty awesome perk that more companies should do.
The 25hz part is important because microbolometers are under ITAR restrictions meaning no US/allied manufacturer offers anything over 9Hz to ordinary consumers.
Probably relevant for the HN crowd: there's a bunch of very geeky next gen fitness guys that keep up with the cutting edge of fitness research, and occasionally expand it themselves. If you're reading them, this kind of thing is being discussed for years, with new studies just moving the odds a bit in favor of the current hypothesis. Yes, they're very Bayesian, explicitly so.
A few names/links, pick and mix as you will - they're all good:
For code reviews:
White Wine. Gewurztraminer, chenin blanc, off-dry rieslings. You want something that's clean on the palette and not sugary sweet. Chardonnay is far too congenial in this session - you're not necessarily here to make friends.
Alternatively gin and tonic but for crap sake use a good gin.
Brainstorming:
Tequila. Just try it. Margaritas if everyone is under 23.
Structure and Design:
Red wine. Deep, rich, moody cabernets, old style zinfandels that roar out of the glass. This is where you pop for the expensive bottles so you do it right the first time.
There is an argument to be made for single malt scotch or 12 year old bourbon here. Either is a solid choice but avoid mixing them in the same session.
Bug Fixes:
Beer. Hoppy micro-brews but avoid the high alcohol content ones. Also avoid the hazy, unfiltered fadish brews. You want to see and think straight and be sharp.
Dull, tedious refactoring 5 year old crap code:
Rose. Hear me out- it's about creating a mind set here. Rose is just that - it's a mind set more than an actual drink.
Anything having to do with Mongo db:
Grand Marnier, Ouzo, Pernod - something at least 80 proof with a strong flavor to compensate for the bitter taste in your mouth.
McMaster-Carr has the best shopping website I've ever seen. The UI is beautifully intuitive; even if I don't know exactly what I need, odds are I can easily find something that will work and they can have it at my doorstep in under 24 hours, no matter how obscure. Even if I don't plan on buying anything, it can be helpful to click through the site just to see what is available. Because most categories of parts have surprisingly well written descriptions and breakdowns, the sire can actually be a good engineering resource.
I've bought from them many times before and have yet to be disappointed with what I got. It is definitely expensive compared to other suppliers or Amazon, etc. But you pay for the convenience.
I hear they aren't very good outside the US though, which is a shame.
Sort of GTD methodology applied to information found online. Accept that it's impossible read/to stay on top of everything. At every moment more information is being created than you'll be able to consume during your entire lifetime. You need to prioritise.
What about the GTD thing? When you stumble upon something spend no more than few seconds to decide whether you read it now, discard it, or put it into a sort of backlog. The important bit about the backlog is that it's not a "read it later" list of everything, instead you assign it a category. Eg this is related to a branch of biology, maths, computer science, algorithms, Linux io subsystem, etc.
Now don't try to go through the "read it later" list. It's hard to force yourself to do that, especially when it is full of things from a dozen of topics of interest. Instead, you make sure that when the time comes that you are interested in digging deeper on a specific topic you have these links/references readily available. I have a separate list of "topics of interest" and go through it from time to time. If I feel like I'm in the mood of digging deeper on distribution systems today then I open that category and see that there are some pending things I need to go through.
A system like roam research is very helpful at this. You can find free alternatives as well, like foam or obsidian. Check them out.
> Anything outside work hours doesn't need to be on a calendar.
I'm happy that works for you, but for me or anyone else who can be absent minded sometimes, that does. not. work. I need a calendar to remember promises I've made to people about when and where I'll be. Tuesday I'm meeting a friend to catch up in person, Thursday I've got a birthday dinner to go to, there's a show on Friday that I have tickets to. Stack multiple events in a single night if you have a busy social life. That's not a ton of information to remember but human memory is imperfect, and that sort of information is in one ear and out the other for me.
Prior to pocket computers, I'd have a paper datebook to carry around (and lose), but thanks to modern technology, it's stored in the cloud and accessible for me at https://calendar.google.com.
We've tried building email templates for notifications for our apps where I work, and it has typically been a pain. We have since swapped to using mjml (https://mjml.io/) to build the templates, and it's working wonders. The output seems the be the most compatible with all different devices that we've tested on.
The other tool we enjoy using is Litmus (https://litmus.com), which allows you to throw in an email template and see what it looks like on all kinds of apps and devices. Other thread here mentions https://testi.at/ as well, which we've also had success with.
All of these have been really invaluable to designing emails for our apps.