I wonder if there's a way to snooze emails using time spaces like how SRS systems (like Anki) do it. First snooze is for 1 day, second for 3 days, etc.
1,651 karma · joined May 28, 2019
My issue is that any place I've lived with central AC (or a condo with a fan coil unit) is that when it's actually hot, the central units don't have enough capacity to cool my unit down enough and don't provide enough control. It's like the old cable modem congestion problem where the whole neighbourhood slows down during peak times.
Heat is even worse; when buildings are heated centrally they're usually much too warm in the winter and I end up with my balcony door opened to let the heat escape. Vastly less efficient than letting me heat my own unit.
By forcing people to heat and cool only their units as required, people either get the exact temperature they want, or will accept a non-ideal temperature and supplement with fans to save money.
I wanted to let others in my situation (longtime Mac user, avoided the butterfly keyboards so much that I considered a Thinkpad with Linux) know: the new keyboard in my 13-inch 2020 is amazing.
I upgraded from my 2015 to this 2020 a couple of weeks ago under duress: my old machine failed me during an interview videoconference and I couldn't have that happen again. Ran out to buy a new machine and return it if I hated the new keyboard (I expected it to be somewhere between the old keyboard and the terrible butterfly, but at least it has an inverted-T.)
It's spectacular. Key travel is awesome, and it's nice to have inverted-T and dedicated escape key back. This machine is also way faster than my old one thanks to (2x as many cores [thanks to 2018 model]) and the 10th gen stuff (much faster RAM and graphics, etc.).
ARM is coming soon, but there's a lot of uncertainty about that transition and I'm happy to have a highly performant machine that will last me at least three years (when my AppleCare will run out).
This setup could let me do it without the USB wifi hanging off the USB OTG adaptor.
* This is not secure but it’s fine for my vintage computing hobby
Executives and clients like to see timelines and total project estimates. I wrote an article* about this. The idea is that you do some rough planning, applying the principles of Agile story point estimation, and extrapolating a rough/relative timeline.
Relative timelines with non-specific dates are useful for getting an idea of the scope and possible time of a project. Helps determine what should be built first, prerequisites, and what other teams might need to be involved (and at what stage). Also useful to get the product managers or executives thinking a bit more deeply about the project and perhaps reconsidering it, or reducing scope if it looks like it will be larger or take longer than expected.
Once a project is kicked off, after a few sprints the initial plan can be updated based on the actual velocity of the team.
* https://jonpurdy.com/pm-framework/how-to-quickly-plan-and-es...
I thought I should replace my 2012 Mac Mini (HTPC) with a modern Hackintosh and 6c/12t or 8c/16t and do my testing workloads on that (or even just use my current 2c/4t for small workloads). But it's just so easy to spin up DO droplets within seconds and do so programmatically. Plus you can snapshot and create droplets from those, and turn on backups if you need to.
It did make me a way better street rider though!
Also glad to have read this article. Was thinking (more like daydreaming) of building a Korean Hanok one day but it seems unrealistic without a lot of professional help.
But now that gyms are closed (I wouldn't go if they were open anyway), I don't have a good substitute. And bodyweight exercises take significantly longer to get the same "pump".
At the gym, I'm forced to get through the workout. At home, it's so easy to hop on the laptop during breaks between sets and get distracted.
Decentralization is the key. Microservices, or segregated services, stateless (as much as possible), and perhaps even partitioning groups of users into totally separated instances. One group gets attacked and service only goes out for the 1000 users in the group. Of course, infrastructure costs would go up but maybe not that much (since you need less resources for 1000 users than 100,000). This is relatively easy to build from scratch these days thanks to various IaaS providers and DevOps tools (obviously hard for established companies with legacy tech).
Then, keep employee computers totally separate from production servers. Let employees back them up themselves, especially since so much can just be stored in the cloud (I'll get there next). Forget about VPNs where everyone can talk to everyone else. Don't try to save money by hosting your own Jira and Bitbucket instances. Pay extra for Atlassian to host for you, then let them deal with security (actually it's cheaper from what I remember). Companies already pay for Office 365 and don't self-host that. Don't host your own email servers. Just focus on the core of what the company needs to do and that's it.
This way you spread your attack surface across a whole bunch of services that are better than you at security, and you get the benefit of not having to deal with other issues. If Atlassian or Cloudflare goes down, no big deal; they'll fix it. And all your other stuff still works.
You still get the best experience (and quality) going through BitTorrent.
If velocity gets turned into a target, corners will be cut (less testing, poor code quality) in order to get those story points for that sprint. Code quality suffers and tech debt accumulates, reducing output down the road.
On the flip side, as time goes on teams could just progressively estimate a greater number of points to stories of similar difficulty during the planning process. So velocity goes up but actual deliverable features goes down or stays the same.
I don't mind replacing a machine after 8 years of service, but h.265 still isn't supported by Google/YouTube, and Apple refuses to add hardware decoding for VP8/VP9, so there's no universal codec that will work as efficiently as h.264 did on my Mini and multitude of MacBooks and iPhones all this time.
Can't do that anymore without either buying a new computer or youtube-dl and recompress the bigger version (which takes hours for minutes of video on my poor machine).
The bigger problem that I didn't mention is with videoconferencing: FaceTime is hardware accelerated and has no issues with 720p, but anything WebRTC seems to prefer VP8 or VP9 codecs, which fails on my Mini and strains my 2015 MBP. Feels like a waste of perfectly good hardware to me.