467 karma · joined January 7, 2012
[ my public key: https://keybase.io/tomusher; my proof: https://keybase.io/tomusher/sigs/drm2q9HG4Adl61ltjgJ7ja61Cj4JvxEs1SbsGFrSVL4 ]
I'm linking my keytrace.dev: did:plc:f6h4cad4yuzqeu3up2dzcsxk
That rule can be overridden if you're having this issue on your own site.
Algorithmic feeds don't give us that opportunity - they're designed to require minimal effort and to keep the dopamine coming without any conscious decisions.
The more people that do this the more we can start rebuilding networks of people we trust and still retain control over the diversity of our sources.
I'd hoped it would be a way to share my own opinions on it, summarise my own personal concerns, as well as adding my own recommendations - but totally appreciate if you feel it is derivative, and I appreciate the call out. As a big Technology Connections fan I certainly don't intend to steal his work.
It's also intended as something you can link to your friends and family that might be a little more digestible than a 30 minute video.
Can't get it to work at the moment - but hopefully with a bit more experimenting, this will replace my current options.
Hadn't realised until reading this submission that Zoom has added blur support on Linux recently - on trying it out it does seem quite poor though - a very sharp edge and quite slow to update.
It's not a game designed purely for expert bluffers. Everyone I've played The Mind with has their own tells and quirks - even when they know the rules forbid it - they'll cringe at their hand, tentatively hold a card forward, or lower it to the table. It's just fun to pick up on these and have a laugh about them.
I'm sure there are people that will rules-lawyer the fun out of it, but with the right crowd this is one of the games I've been pulling out most frequently recently, and haven't heard a bad thing.
At the moment I've settled on a three-tier system:
NVAlt - as a scratchpad, clipboard buffer and other transient notes.
Moo.do - for structured notes, Todo lists, reminders and agenda/scheduling
Dokuwiki - for long term knowledge base stuff and for documenting personal and home projects. Love this because my family can easily read and use it too.
I've tried loads of tools but I've stuck with this set longer than any other so far.
This seems to distill the concept down very nicely - quicker to load and straight to the point. Sadly I'd miss the structure of Moo.do but I can definitely see a world in which I'd use it - nice work.
Hope this is fixed in a firmware update, my repeater is quite a nice device otherwise.
With this, VSCode, Slack & Boostnote - a good portion of my daily work is done in Electron apps and I can't say I'm itching to switch to native alternatives.
Definitely appreciate how people have issues with it, but it doesn't seem like it's going away and hopefully will only get better.
I can see it getting repetitive, particularly as there's not a huge amount of storytelling - and from what I've heard, some people aren't enjoying the need to replay hours of content when you die - but so far, I'm impressed.
The second printing (+ expansion) Kickstarter is live at the moment (https://www.kickstarter.com/projects/1926712971/the-7th-cont...) which seems like it's adding a lot more content. I'm in, but whether I'll still be interested in playing more when it ships in October 2018 is another question...
Welcome to the Dungeon/Dungeon of Mandom - https://boardgamegeek.com/boardgame/150312/welcome-dungeon
Love Letter - https://boardgamegeek.com/boardgame/129622/love-letter
Hanabi - https://boardgamegeek.com/boardgame/98778/hanabi
No Thanks - https://boardgamegeek.com/boardgame/12942/no-thanks
Archaeology - https://boardgamegeek.com/boardgame/191300/archaeology-new-e...
Linko/Abluxxen - https://boardgamegeek.com/boardgame/153065/linko
I've been enjoying Lost (https://github.com/peterramsing/lost) with PostCSS for grids recently - it has Flexbox support which works well and keeps grid class names out of my markup.
The main thing I'm still trying to get my head round with React/Redux/Router is where in the lifecycle to do data fetching - I noticed you're doing it in componentWillMount, when the React docs suggest componentDidMount, and I've seen others do it in various other ways with no clear indication what the 'best practice' approach is.
As with anything new and interesting, it's easy to insert a fictional future scenario that takes away what makes our personal lives rich and enjoyable.
I love to cook but it's all a bit sci-fi and uncomfortable to think that we'll all have our government mandated NutriSludge dispensed twice a day so we can all stop worrying about cooking and work harder.
I could never imagine myself in a situation where I'd consider it so important to be constantly busy that I wouldn't be able to find the time to throw a few vegetables in a pan - but I understand different people have different priorities (and demanding jobs).
It just seems to me like this is an odd way to solve the problem, maybe because I'm extrapolating a bit and seeing it as trying to replace one of the things that makes us human; the ability to prepare and cook food.
I'd be interested to see if any research comes up as to the long term psychological effects of this sort of product. Do people who replace the varied textures and tastes of different foods (if only partially) with a liquid supplement notice any adverse effects or cravings?
Out of interest, is Soylent more interesting than offerings from companies like Graze/Naturebox?
I can certainly appreciate the science behind it - this would be a great boon to helping feed those that are less fortunate, but from what I can see that doesn't appear to be the aim of the company.
More recently, Ansible Inc's faceless approach to marketing has me a little frustrated, but this isn't the time for complaining.
Thanks for all your hard work on Ansible Michael! I hope the team you've built can continue to pursue your vision for the project, and best of luck wherever you end up next!
For the dev/prod parity use case, where do you usually draw the line between Packer and Vagrant? I'm currently building boxes with Veewee with all dependencies pre-installed and distributing this to the team. Vagrant could easily deal with this, installing dependencies when the VM is launched using provisioners.
Does anyone have any preferences/reasons to go one way or another?