psycr
Flexpa is making it easy for patients to share their claims, benefit coverage, medications, and other data from health plans. We're a developer-first platform with rich APIs, robust developer documentation, and other tools to help applications to build novel patient and provider experiences powered by claims data.
We believe in open standards, open source, and open, transparent culture [1]. We surround ourselves with excellent people who want to build the best products, with high independence, drive, and enthusiasm. We're building the Plaid for healthcare and we want you to join the team.
We build with:
* Fullstack TypeScript (strict mode) and ES2020
* Turborepo and a one repository monorepo
* NextJS, React, and Tailwind
* Fastify and JSON Schema
* PostgreSQL and Prisma
* HL7 FHIR
To apply see our careers page https://flexpa.applytojobs.ca/ or email us at [email protected].
Interview process: - Submit application at http://universe.applytojob.com/apply/6hV3Xj/Senior-Full-Stac...
- Phone screen
- In person + pair programming challenge
As a Senior Full Stack Developer at Universe, you will apply your passion for technology and live events in your quest to build a world-class Event Ticketing platform. In this deeply technical and business-minded position, you’ll architect, implement, and evolve our frontend and backend systems with a talented team of like-minded peers. As a senior developer with great influence on our product, you’ll be challenged with the rewarding tasks of understanding our customers with strong empathy, curating an amazing product experience, and championing our vision to new heights.
_What your day would look like_:
- Writing new application code for our core product API and client (especially transactional pieces)
- Advocating best practices for development and testing
- Performance profiling new and existing features in both our server processes and in the browser
- Mentoring junior developers on the team and promoting skill growth
_What we’re looking for_:
- Experienced in Ruby on Rails, NodeJS, and/or MVC backend frameworks
- Experienced in Ember or React frontends
- Excited about BDD, automated deployment, fixing bugs, and shipping code
http://universe.applytojob.com/apply/6hV3Xj/Senior-Full-Stac...
> Scientists have found some genetic code that contributes to hereditary behaviors, but the bulk of it is unlikely to ever be found. Why? Because it plainly does not fit.
This is plainly not true. We've found lots of evidence for the genomic basis of hereditary behaviors. See Genome-wide Complex Trait Analysis for example - plenty of statistical research is out there.
Do you have any academic literature to support your claim? The only evidence you offered was just an insistence that I should agree, which shouldn't convince any fair minded person. Here's something that I found within 15 seconds of journal searching, that contradicts it: http://onlinelibrary.wiley.com/doi/10.1111/j.1741-1130.2011....
> The results from a series of follow-up studies indicate that the IQ score at age 13 could be viewed as a relatively good indicator for future life outcomes, defined in terms of attained education, occupational status, and material well being
Finally:
> Really, come on. That kind of 'they can just pull themselves up by the bootstraps' is ignorant enough to sound like dog whistling.
I don't think we can, and I don't think I said anything like that.
Also, what's the name of your business?
> Basic income doesn't come off the backs of small business, and that is a silly reason to be so afraid of it.
What's the name of your business?
You probably only need n = 5 for a confident answer to the question "What happens when you are shot in the head?"
- I joined a seed stage startup
- That startup raised a series A ($N millions in total financing)
- Was then acquired by a Fortune 500 company, which has kept the business as a separate unit for > 1 year
- I was a party to the deal :)
I have found salaries to be competitive when total cost of living adjustments are made (even despite the currency value). Importantly, the labour market here values skills over credentials - so there's a distinct pragmatism in the air.
So as far as startups go - not the publicly traded and pre-series-G-mega-SF-corps - I think there's a vibrant opportunity and reality.
Congrats everyone at Bitstrips!
That's what parent means by self-selecting, which is being used in the sense described here: https://en.wikipedia.org/wiki/Self-selection_bias - a perfectly innocuous meaning.
(I say this as someone who has no pony in this race - I'm neither a resident, nor citizen, nor etc of the US)
Regardless, being _biased_ is most definitely _not_ the substance of any interesting critique of media. Rather, it's trivially obvious that the production of media is intricately related to ideological beliefs and political agendas - precisely because media is the primary tool of mass persuasion. Look no further than the long, storied history of newspaper barons.
Fundamentally, media functions as a legitimation strategy for normative beliefs; a structure for the normalization of acceptable opinion.
http://i.imgur.com/rb0GJvQ.gifv
Basically, you create a video, dump the video's frames with ffmpeg, run each frame through the RNN, and stitch them back together. It took me several hours to produce just ten seconds of video. Unfortunately, unless you have a Titan X GPU the max size of each image is quite small (certainly less than 1080p), which may be why the frames in this video are split into four quadrants.
The shibboleth speaks!
But in all seriousness this is, in so many words, exactly what I was describing.
Regardless, I suspect given the nature of media and ideology, and how fickle our notions of bias really are, that any subtle critique of the CBC is bound to be buried in shibboleth dynamics.
"to engage with the people that come to work every day" "its a service that connects you into the building you work at, the company you work for, and the vendors and services around you"
What does this mean? It's not clear on joinlane.com either.
https://en.wikipedia.org/wiki/The_Mythical_Man-Month#The_pil...
The lesson is basically, when you're designing a new system or product - make one with the knowledge that you're going to scrap and it start over. The value in doing so is that you expose flaws and design challenges that you can't anticipate through the speculation that occurs before you've actually started.
----
I decided to give MM-M a read, after seeing it repeatedly listed as one of the classics of the fledgling - as the book maintains - field of software “engineering”. Despite a few dry chapters extensively detailing the development of OS/360, the book holds up remarkably well for being forty years old. Indeed, many of its central, oft-repeated development aphorisms still hold value. Unfortunately, its advocacy for extensive and exhaustive planning and documentation cycles screams “waterfall”, and muddies what is otherwise - I think - a number of worthwhile recommendations:
1. Avoid the second-system effect by being ruthlessly practical
2. Build a prototype and throw it away
3. The essence of programming has an irreducible complexity
Aside from these, I noted with great interest Brooks’ suggested team structure which he refers to as a surgical team: 6-7 people in highly stratified, and complimentary roles, led principally by a “surgeon”-type chief architect. I’ve only worked within relatively flat team structures up to this point, typically set up in junior/senior relationships. Since this is a less frequently cited recommendation in the book, I’m curious to know if it has been implemented with any success.
Finally, this suggestion is tantilizing:
As a discipline, we need an extended information theory that quantifies the information content of static structures, just as Shannon’s theory does for communicated streams.
To have so clearly seen the future (not ours, but the one ours portends) is truly, completely, and utterly remarkable. I cannot recommend it enough, and it is tantalising to me that Sacks devoted some of his last days to its exposition. To have had just a little more time...
Here is my favorite passage:
"Cannot you see, cannot all you lecturers see, that it is we that are dying, and that down here the only thing that really lives in the Machine? We created the Machine, to do our will, but we cannot make it do our will now. It was robbed us of the sense of space and of the sense of touch, it has blurred every human relation and narrowed down love to a carnal act, it has paralysed our bodies and our wills, and now it compels us to worship it. The Machine develops - but not on our lies. The Machine proceeds - but not to our goal. We only exist as the blood corpuscles that course through its arteries, and if it could work without us, it would let us die. Oh, I have no remedy - or, at least, only one - to tell men again and again that I have seen the hills of Wessex as Ælfrid saw them when he overthrew the Danes."