I heard about it from the React community on Twitter and I've been using it exclusively for system design interviews. I love the look of 'whoa cool' when candidates see my cursor moving around the screen :)
Microsoft Healthcare: EmpowerMD | Full-time | Seattle/Redmond, WA, USA | Onsite
Imagine a visit to the doctor’s office where the focus is on you. Not the computer. We’re EmpowerMD in Microsoft Healthcare (https://aka.ms/empowermd), and we’re building an ambient intelligence for the clinic you can see in our 2 minute demo video (https://www.youtube.com/watch?v=jnGlOCBK3kM).
If you’re mission driven, want to work on a collaborative multi-disciplinary team to build AI for good, we’d like to chat with you. We’re actively hiring engineers with full-stack engineering experience on a modern stack (React, NodeJS, serverless, K8S, NoSQL, etc.)
All positions are Redmond, WA only and international relocation is not available at this time. We are currently working remotely from home due to COVID-19 but we are looking to hire full-time employees now who can work with us in Redmond, WA when we are able to return to work at the Microsoft main campus. We cannot support long-term remote work because of our partner's privacy/security requirements.
If you’re interested, please email (with an updated CV): ask-empowermd@microsoft.com
Fork is awesome. I've been using Windows for the past year for a project and missed GitUp on Mac.
After trying a few clients (Tower, SourceTree, Kraken, and a few others) I stayed with Fork - very fast, performant, and intuitive. Right now I have about 15 repo tabs open in Fork with a large number of branches in each. The tree view is excellent (I actually liked the older one-line-per-entry version).
Fork recently added the ability to compare branches - literally click two times to get a diff within half a second.
I really can't believe this app is free. Well done to the makers of this excellent app!
Microsoft Healthcare | Redmond, WA | Data Scientist (Junior/Senior/Principal) | Full-Time | ONSITE | https://aka.ms/empowermd
Did you know that doctors spend over 60% of their time on medical documentation? Did you know that this is a major contributor to doctor burnout and soaring medical costs?
At Project EmpowerMD, a team within Microsoft Healthcare, we’re working on fixing this problem. We aim to harness the power of machine learning and NLP by automatically generating notes from clinical conversations.
Want to leverage your knowledge of speech-to-text, NLP, or machine learning on one of the biggest problems in healthcare? We’re a fast-moving multi-disciplinary team. You’ll have opportunities to work with the latest NLP/ML technologies, work closely with doctors, and make a huge impact.
In this role, you will:
- Drive the team’s NLP efforts, extracting intelligence from clinical dialogues to generate medical notes.
- Be a technical leader in the design, prototype, implementation, testing, deployment, and monitoring of ML models for data annotation, language processing, language generation, and dialogue management/ranking.
- Help define our product and architecture while learning from and collaborating with experienced ML/NLP/ASR leaders around the company.
- Join and help build a low-process, high-output team, doing groundbreaking, socially meaningful work.
I worked with Typescript for 2 years, then worked with Flow for 2 years and now I'm back on Typescript working for a big company.
I agree that Flow had better capabilities around soundness. But the tooling around Typescript really made me jealous, specifically in VSCode.
Near the end of working with Flow, Typescript was getting some cool capabilities like refactoring JSX for React apps.
Nowadays I can easily say that Typescript is a far better experience than Flow. There are updates every two months, adding some neat features that you might find in other languages.
Then you add in the power of surrounding tools and their ecosystems like TSLint and it really feels like a next-level coding experience where the tools start writing the mundane code for you, driven the core TS static analysis.
I'd agree with everything you've said. Flow isn't bad but after working with TypeScript I could never go back. You're spot on with the tooling and ecosystem.
Yeah my laptop of choice is 15" MB Pro mid-2015. Picked up 2 of them over the last couple of years from Apple's refurbished store and I think with OS X it really is still one of the best laptops out there. A little tip - you can use https://refurb-tracker.com/ to get alerts when they get in stock.
TBH it's the MB Pro + OS X combo that works so well. MB Pro + Windows is definitely sub-par... lot of other great laptops for that. I've never tried Linux on a MB Pro.
Ubuntu runs great on my 2013 15" Macbook Pro. It does mess with the boot manager, and can become unstable if you install it simultaneously with boot camp.
The only issue is that the trackpad drivers aren't so good. Stick to OS X if you're a trackpad gesture power user.
Thanks for the tip! I reluctantly bought a 2018 MBP but returned it within a week. I thought I would have to stick with my workhorse 2012 MBP, but now I'll check out refurbished 2015s.
Pretty sure they're being sarcastic. But I'm guessing the commenter hasn't used Google Cloud anyway - Python 3 was supported on Flex enviroments for a long time. The news here is that they're supporting it on Standard environments, and there seems to be good technical reasons for taking so long.
Okay I know nothing about trading halts but reading this: https://en.wikipedia.org/wiki/Trading_halt it seems that Tesla is supposed to tell the exchange to halt trading 10 minutes prior to releasing news. Did Tesla initiate the trading halt here (late) or did the exchange?
I am not familiar with this area but based on the glossary here https://www.nasdaqtrader.com/Trader.aspx?id=tradehaltcodes , it seems if the halt was done by the exchange it would have a T12 halt code. SteveGregory's comment cites Tesla trading was halted using a T1 halt code (defined as "Trading is halted pending the release of material news"), which I assume would be initiated by Tesla.
Have you migrated anything off of Firebase? Or still kept the “base” projects and upgraded around it? I’m interested specifically in how expensive Firebase is for popular products
I haven't migrated off of Firebase but this is something I've thought a lot about as I've selected Firebase for many of my client projects.
As far as I can tell there is no open-source alternative with feature parity that makes it easy to migrate away from Firebase. I'd be curious to hear about how people have done this.
This is actually what I'm afraid of - specifically vendor lock-in and being stuck with a stack that has high operating cost. From some of the comments I've seen, Firebase has high operating costs. But I'm still planning on testing this out myself with a small project soon.
