psycr

Flexpa | Remote (US timezones) | Full stack engineer | https://www.flexpa.com

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 hiring@flexpa.com.

[1] https://handbook.flexpa.com/

Senior Full Stack Developer @ Universe | https://www.universe.com/ | ONSITE | Toronto

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...

You pay for the underlying instances + storage provisioning, so performance is price-configurable.

Now they just need to support the Foreign Data Wrapper extension with egress connections. Really wish that was built in because FDW itself is amazing, and AWS RDS is easy to manage.

Kind of strange that there's no mention of actual behavioral genomics research here. Aside from the quip that:

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.

If we want to compare across QoL, opportunity, really almost any metric, we're going to group across socio-economic lines, not IQ.

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?

Opportunity is not evenly distributed, yes. But neither is skill.

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?

Depends on the effect size.

You probably only need n = 5 for a confident answer to the question "What happens when you are shot in the head?"

Depends how big the effect size is. For putting a loaded revolver next to your head, and pulling the trigger, n=30 is plenty.

So this article is about people like me. I went to school in Toronto and stayed. In the > 5 years since:

- 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.

Counter fact check: there's a massive Shopify office on Spadina

Can you articulate this in the form of a binary outcome? If so, I will happily make a $N00 sized bet (odds to be negotiated) on the false outcome with anyone who is interested.

Wow! Massive news for the Toronto tech community. We don't have too many deals this size.

Congrats everyone at Bitstrips!

This comment is strange to me, I did not have the same impression whatsoever. The numbers here, and overall picture, match all of his previous annual summary posts. It's been fairly clear in those summaries that his attention has shifted to other projects/consulting opportunities etc, and that BCC was declining in profitability.

> My mother didn't "sacrifice" everything for us, she worked hard; became a programmer; and didn't allow my sibling and I to work less then her.

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)

You lost me with your jargon, not sure what your point is there.

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.

Frankly, this is wilfully ignorant. To suggest that the production of media is devoid of political or ideological interest beyond ad dollars is, I think, stretching the boundary of believability to a breaking point.

The content in this article is disgusting and despicable. I will be moving my code from GitHub as soon as possible.

You're an entryist. I hope anyone reading your comment reads the rest of the thread to which you link. Much sanity is to be found.

Because they discriminate based on political beliefs completely unrelated to the conference. For shame.

I produced something similar to this shortly after the release of https://github.com/karpathy/char-rnn:

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.

Herr Harper private media political clickbait celebrity gossip real scientists political too

The shibboleth speaks!

But in all seriousness this is, in so many words, exactly what I was describing.

When Harper was in power, sure. Lately, the coverage has been a bit, shall we say, fawning?

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.

What is Lane? What is your core product?

"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.

Do you ever host public meetups, discussions, presentations, etc of your work? Or are there bioinformatics meetups in Toronto more generally that you, or your staff, attend?

Are you referring to string-overlap graphs for de novo assembly? In that case, isn't CRISPR addressing another problem?

Further information from the MM-M wiki article:

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 second the recommendation for MM-M, after recently reading it. You may find the chapters around how to structure a team to be interesting. Here's my review (posted elsewhere):

----

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.

This is of course correct - I myself needed some sleep when writing the comment ;)

The book referenced by Sacks - The Machine Sleeps - is positively, absolutely wonderful. It is, equally wonderfully, free for all, having been published in 1909: http://archive.ncsa.illinois.edu/prajlich/forster.html

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."