3,022 karma · joined March 7, 2012
A technologist, founder, and current Googler, I've repeatedly taken products from inception to commercial success across sectors, from startups to Fortune 10 companies. My specialty lies in bridging the gap between business vision and technical execution, deeply engaging with code and who mentors teams. Beyond engineering, I bring a global perspective from living abroad for nine years and speaking fluent French.
Get in touch with me: --------------------- @jlyman j @ joshualyman.com http://www.linkedin.com/in/joshualyman
[ my public key: https://keybase.io/jlyman; my proof: https://keybase.io/jlyman/sigs/c1xpV7dq3vEGU8gVObbZqSDE1_-E5t97Gl7HCQ98ebk ]
Something similar to what your grandmother had or other unions is a PEO, or professional employer organization. It's a collection of small businesses (usually) that band together to get access to services otherwise only available to larger groups. It's a little interesting because technically you become an employee of the PEO as well as your own company, and there are certainly costs associated with it, but it's in the same vein as union dues, for example. Just not as clear cut and not required.
Killing the group market could create certain efficiencies, but it would lose many others. And like you said, that is politically infeasible.
Other options, like looking at cross-state competition and capping certain medical expenses are likely better possibilities.
I am probably more familiar with insurance than most, having done detailed research in the arena and knowing pros in the industry. My premiums this year increased by only 40%, on top of the 65% from last year's increase; a pleasant surprise. I have a 25 sheet Excel doc that models out my family's expected healthcare costs for the year to compare individual plans. If I were to stay with my current plan (which I won't) it would cost me well over $32,000 in total next year. I've spent many hours trying to figure out what the best financial path forward is, and I still have some huge question marks. (Ever tried to get coverage information for particular CPT codes from an insurer? Ha, good luck!)
Unfortunately, a lot of the cost comes down to the demographics of the individual market, and I don't know much of what can be done about that. I don't fault the actuaries at the insurance cos for doing their job, and it's true that despite the crazy premiums and poor coverage the insurance cos are still bleeding money in the individual markets. Having also lived in countries with single-payer systems I don't believe that is the solution either. But something's got to give or entrepreneurs just won't be able to afford being entrepreneurs anymore. (And the situation will just get worse for non-entrepreneurs who don't have access to group coverage).
Screen sharing is very slick as well, so long as the sharer is using Chrome. The only thing I find missing is the ability to share mouse/keyboard control, but in typical conference settings that's usually not a frequently used feature.
Used the following guide to set up react-snap into an existing CRA application in just a couple minutes: https://medium.com/superhighfives/an-almost-static-stack-6df...
I want to investigate the CSS inlining feature--that's one of the areas where I still am loading a decently large external resource. Experimental, but could be a nice win.
(Edit: added the guide I used where I originally found out about react-snap)
It obviously contains a business CTA, as I’m also trying to gain experience on the sales side of things since I’m coming from a technical background.
I would love any and all feedback! It’s all about the learning process right now as I try to stairstep up the experience ladder.
In my future postings, I will evaluate the market for the type of position I'm posting, decide on a pretty narrow range (even a specific number), and make it part of the posting and the job overall. It worked well for me and many others, and removes so many issues.
It's not, of course, the only thing I care about, but far too few postings offer this level of transparency. Love the other ideas of work week length and problem to be solved as well.
IANAL, but I wish the lawyers at Facebook would take one for the team and relax a bit on this (hey, more work for them, a plus!). If you're going to sue Facebook over patent infringement, you're probably going to spend a lot more on the suit itself than the eng costs rewriting a view layer.
[1] https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
> "...but [Vogt] added that these are destined for deployment in fleets, rather than as individually owned consumer vehicles."
I think this really clarifies the direction that GM (and I believe other auto manufacturers) see as the way forward: moving from an individual-ownership model to an on-demand rent model.
I wrote up a quick explanation here: http://www.joshualyman.com/2017/08/find-hidden-apple-refurbs...
When transported to the current day conceptions around the strength of cryptography, this particular line makes me also think of Dr. Janek's line from Sneakers, where while discussing the virtues of encryption, he says:
> The numbers are so unbelievably big, all the computers in the world could not break them down. But maybe, just maybe, there's a shortcut.
Not that I hope we find a shortcut any time soon, but time has a way of letting us discover interesting shortcuts, be they lockpicking strategies or prime number weaknesses.
http://www.edwardjayepstein.com/diamond/chap17.htm
(tl;dr: though unconfirmed a noted diamond expert believed the Soviets had created a diamond cutting machine instead of relying on human cutters, though others disputed the idea.)
But truth be told, the only thing I really want from Safari is favicons on tabs along with page title. Kills usability for me otherwise.
Unlike most tech recruiters, I actually could vet candidates before presenting them, in theory generating higher quality candidates who are more likely to get placed. There's still a supply-side issue though...
Your professor is correct in that it's widely used amongst such companies, though other competitors are very often in place as well such as Sybase or Microsoft SQL Server.
The right tool for the right job (or in the startup world, the tool you can afford.)
The permission check becomes vital: it's part of the patient authorization at, for example, a first visit, and is best when also followed by a verbal authorization upon checkout. It's one of the big hurdles we're trying to overcome obviously, but we believe there are proper ways to do it and make it work within the boundaries of regulation and privacy. No good problem worth solving is without difficulties, right? :)
Shameless self promotion: this is the exact problem my co-founder and I are working to address: https://www.perspexilabs.com/ (site currently looks broadly-focused, but we're targeting medical).
We're finding patients are actually very happy to give feedback, especially when given a neutral medium to discuss their experiences and when doing so very quickly after an interaction. The super-tight feedback loop not only makes everyone more satisfied, but it also has the chance to improve quality of care too.