49 karma · joined September 5, 2019
This could be a variety of scenarios like working remote on bad ISPs or cellular or a crappy VPN but all that matters is when it acts up it will cause lag, or dropped connections depending on severity. Too many interruptions while trying to focus.
For this reason I keep everything local and use an rsync wrapper over my build system that streams output back. The added delay for each command disrupts workflow less than it happening during editing.
The current summary is that most of them are wildly inaccurate with false positives and you might just be better off checking your outdoor air quality from the EPA using their app.
Would love for someone to provide a better recommendation.
"The Best Home Air Quality Monitor for 2022 | Reviews by Wirecutter" https://www.nytimes.com/wirecutter/reviews/best-home-air-qua...
Gsuite in general is accessible and works well for Collab.
And of course Teams is on a whole different dimension of pain.
From what I can see Microsoft stack is used mostly by enterprises that are not engineering centric.
For all of the largest engineering centric companies that pay top of market only one heavily uses Microsoft....and that is Microsoft. Furthermore most VC funded startups also tend to shy away from Microsoft stacks. (Exception being parts of Azure compatible outside of the MSFT stack and other polyglot tools like VScode)
So while I don't think you need to worry about employability I wouldn't recommend investment in the stack to new graduates. Obviously my perspective is limited so I'm curious to hear counter points.
What would you tell someone with a Drug problem?
When I spent (a relatively small amount of) time working with one this was the main thing the director drilled into my head. Use it to solve large, parallel problems that require lots of intranode communication of intermediate results. Embarrassingly parallel problems can be solved on cheaper hardware like GPUs.
At the same time not smart people or disadvantaged won't be ignored or fall through the cracks. Over time as productivity rises through automation we can ramp up the UBI and make sure all human life is valued and give people real opportunity. Even with a UBI that doesn't require you to work to live doesn't preclude a capitalist persuit of resources to make your most grand ideas come true. Let's just make sure we tax externalized cost appropriately.
Will some smart people choose to not work eventually? Sure, but if our automation can support them, who cares?
I think Yang came up with an eloquent phrase for this - UBI is capitalism that doesn't start at 0.
I don't think he's suggesting your OS is going to be an ML model, but we will be surprised at how many problems they solve better than trying to do everything in a more manual way. I think this is pretty intuitive. Our programs used to say "Move this byte to this register" but now they say "Toggle this button". Eventually they will just say "Learn to produce results like this" with the same reliance on the developers who build the infrastructure as we have today for our compilers and interpreters.
Not trying to make any kind of judgment about this being good or bad. Just trying to point out reality. This is the world we live in - performance matters.
Skydio - https://www.theverge.com/2018/4/5/17195622/skydio-r1-review-...
Shield AI - https://www.shield.ai/nova
Battery life is certainly an issue but even before a major breakthrough happens 10-20 minutes is a long enough flight time for a lot of autonomous tasks. Plus what if they dock and charge themselves?
I think they're going to continue getting smaller, more power efficient, and cheaper and it will continue to open up possibilities.