bmdavi3

Procured Health | Full Stack Engineer | Chicago, IL | ONSITE | Full Time

As a Full Stack Engineer at Procured Health, you will directly impact our healthcare system by writing and architecting software that enables hospitals to lead real change in the industry. Our Engineering team is expanding and we are looking for full stack engineers with strong front end development experience - specifically Vue.js.

You will work in open source Python libraries, but don’t worry if you lack Python experience. If you have Ruby on Rails, Perl, PHP or experience with another open source language, we will teach you Python. You’ll also integrate data from our machine learning software with various database backends like PostgreSQL and Redshift and develop an interactive UI that drives user adoption and engagement. The products you develop will be used by leading health systems across the country to drive better decision making and patient outcomes.

The successful candidate is a software engineer who is ready to play the crucial role of building the applications that are essential to the success of our business. You like constructive code review and writing useful tests. You bring data to topics of debate. You work with other engineers, designers, and product managers in an Agile environment to help everyone bring their best. You focus on the value delivered to the user and help the team iterate toward a better solution.

Stack: Django, Vue.js, MySQL, PostgreSQL, Redshift, AWS

https://procuredhealth.com/careers/ http://procuredhealth.applytojob.com/apply/uEAQZR95mS

For queries returning results from a majority of rows in the table, won't a sequential table scan be faster than an index scan?

I can't say that I'm affected by this sort of thing to the same extent that you are, but the feeling of 'suddenly losing interest after gaining understanding' is easy to relate to. I have no problem keeping focus for hours trying to understand how a particular bug could possibly be happening, continuing to work after hours until I figure it out. When I'm still in that 'learning / understanding' phase, there's no effort required. I want to know what's going on here and it will bug me until I get it. And hopefully, the end solution is a couple line fix.

And very often, it is. But sometimes it ends up being the type of problem that requires a much more involved architecture change to solve correctly. It's not just a one line change, but something the whole team will have to sign off on. Which will require at _least_ 100 times the work of the usual two line fix. By this point, I already 'know' how to solve the problem, and it could be very easy to lose interest. But the error emails keep on coming. And they're easy to ignore because "they're just those weird errors we get from that 3rd party API we use so there's nothing we can do about it."

But these emails are really annoying. So I find I have to reframe the problems from understanding how to fix the issue to how to get buy in and get the fix actually deployed, and I haven't run out of these types of problems at any company I've worked at, and that works for me to keep my attention.

It's not graphical, but pasting the explain analyze output into http://explain.depesz.com/ helps me see where postgres is spending most of its time.

Fellow aficionado checking in! Thanks for the link, let me also throw in a super recent one from 2014 of Ralf Souquet running 178.

https://www.youtube.com/watch?v=OPFqNhRk70Q

I also enjoy watching competitive 9 ball, where if you aren't running the table, you're putting your opponent into a ridiculous safety, and then there's usually an amazing shot to escape, etc. until one side gives the other an opportunity and they likely run the table, which is also impressive. But then again, I'm just getting into straight pool, and I really enjoyed watching the above video. So straight pool's growing on me too.

For watching any kind of pool, I think it helps to play a bit to get a perspective for just how difficult some of the shots are, but also to be able to picture the thought process the player is going through. There are shots a player might be able to make 75% of the time, but if they miss that shot it's over, so they'll play safe, or choose a lower percentage shot that has a built in safety, and you can usually pick up what they're trying to do next. Or they come out of nowhere with a shot neither you nor the commentators saw coming and nail it, to which the commentators will say something like "well, I guess that's why Shane is the #1 ranked player in the world and we're not!"

In high school, part of the reason I chose computer programming as my future career is because I like it, and part of the reason is that I knew not a lot of other people did, or could do it well. I didn't know what the world would be like in 20 years, but I figured that was a good way of giving myself a chance at having a good job down the road.

Computer science courses in college were much tougher than in most other majors, and there were many, many nights I'd be coding away to finish a project while my friends were out partying, playing video games, etc. I like art, history, and music too, but I figured it was worth it, just a few more years and it would pay off.

Now, just as it is starting to pay off, people are trying to change the rules. I've been trying to get my 10 year old nephew interested in science and math, encouraging him, so he can make the same choices down the road if he wants to. But if the plan is to swoop in at the last minute and remove the rewards for delayed gratification, maybe I should tell him to have a blast and do whatever.

Either allow full immigration for people in any career (best option), or have the same stifling limits for all careers (distant second). Don't cherry pick who's going to have their careers dis-proportionally affected.

With Paypal you get one option for dispute resolution: Paypal. With Bitcoin, you can have any number of companies compete to be the arbitrator for your transactions. May the most even handed one win.