TL&DR: Some people have different circadian sleep cycle and that's okay.
3,151 karma · joined October 7, 2009
phzbox at gmail @phzbox
We are a passionate team of MDs, PhDs, designers, engineers, and scientists who help medical professionals and hospitals deliver the best possible care to patients.
We are looking for back-end and front-end engineers. Stack includes Rust, Node, React and React Native. We are well funded and offer competitive salary, equity and benefits.
Please email jobs@listrunnerapp.com and mention "[hn]" in the subject line. Sorry, no remote option at the moment.
Here's one way to look at it, considering everything else equal, if you were an employer, would you pick someone who knows X (where X is jquery or whatever requirements you need) or someone who knows X + Y (where Y is some interesting technology that may eventually turns out to be useful)?
I'd say something like: We have such and such problem and I have looked into various standard and well-known solutions. Unfortunately, those solutions don't solve our problem because X. Good news is I found this new technology that could help. Is it worth giving it a try?
And, to be fair, if you have one solution that is standard, well-known and solve your problem, I'd stick to it instead of chasing trendy things.
We're working to fix the software doctors use. If you have seen what physicians have to put up with, it's a bad version of the 90s, and makes medical care worse and more expensive for everyone. We are a group of previously successful engineers and entrepreneurs (MIT, Dartmouth, Datapower, Stripe, Salesforce, etc) and senior doctors (John Hopkins, UCSF, Oxford, etc) who are determined to finally fix this.
Compensation: market salary & equity -- we are well funded.
Stack: includes Rust, React and Node. We will also be solving some very interesting problems in the areas of APIs, domain-specific machine-learning and fine-grained application security.
Please email jobs@listrunnerapp.com and mention "[hnjobs]" in the subject line.
One of the hard challenge of DOTA is whether or not to "trust" your teammate to do the right action. I.e. One can aggressively go for a kill knowing that their support will back them.. but one can also aggressively go for a kill while their support let them die, and then the whole team starts blaming and tilting because the dps "threw". It's a fine balance.. From personal experience, it seems like in lower leagues it's better to always assume that you're by yourself, whereas in higher leagues you can start expecting more team plays.
Another example is often many players will use their ultimate ability at the same time and "wasting" it. It would be easy for an agent controlling all 5 players to avoid this.. but how would a individual agent knows whether or not to use their ult? Are the agents able to communicate between each others? If so, is there a cap to "how fast it does it?". I.e. on voice, it takes a few seconds to give orders.
In Canada, they get the benefit of "free healthcare / transit / education" + amazing house that can be paid almost cash thanks to the years in US banking up + back to their friends and family + "senior" level jobs thanks to their expertise learned at the top 5 tech company.
We are a stealth startup working to fix the software doctors use. If you have seen what physicians have to put up with, it's a bad version of the 90s, and makes medical care worse and more expensive for everyone. We are a group of previously successful engineers and entrepreneurs (MIT, Dartmouth, Datapower, Stripe, Salesforce, etc) and senior doctors (Johns Hopkins, UCSF, etc) who are determined to finally fix this.
Senior Frontend Engineer:
- help us delight physicians with great UX that helps them take care of patients
Requirements:
- production experience with react.js, redux & related ecosystem
- strong general programming skills
- success in shipping complex products
Strong pluses:
- react-native and/or other mobile experience a plus
- passion for great UX
- experience with enterprise products and/or healthcare IT
Compensation: market salary & equity -- we are well funded.
We are a stealth startup working to fix the software doctors use. If you have seen what physicians have to put up with, it's a bad version of the 90s, and makes medical care worse and more expensive for everyone. We are a group of previously successful engineers and entrepreneurs (MIT, Dartmouth, Datapower, Stripe, Salesforce, etc) and senior doctors (Johns Hopkins, UCSF, etc) who are determined to finally fix this.
Compensation: market salary & equity -- we are well funded.
Stack: includes Rust, React and Node. We will also be solving some very interesting problems in the areas of data processing, APIs, UX and fine-grained application security.
Please email jobs@commure.com and mention "[hnrust]" in the subject line. Other positions available, but please use [hnjobs] in subject line.
You could write about new programming languages or new algorithms that just came out. Anything with nice animation is a plus. (I.e. to illustrate the algorithm)
Another thing that I find interesting is interviewing great people in the field. Often, there are questions I wish I could ask them that most other interviewers don't because they're not technical enough.
You can write about weird bugs that you encountered, how you fixed them and what lessons you learned.
For the first time, I used a webapp and was hoping that the ios/android experience would be good enough. Unfortunately, It wasn't and it was a big mistake. I'd only recommend this for quick mvp knowing that it'll need to be rewritten or if your audience really understand what it means to have a mobile webapp compared to a native app. I.e. if there's an IT department in place that can install it on the devices and understand the limitations.
For the second time, we went with ionic/phonegap. It was a huge improvement, but we hit too many limitations and scenarios where we wanted native tweaking for animations or handling the keyboard hiding fields or the topbar acting weird, etc. You don't see those issues at first.. but they start appearing as you start doing QA on more devices and with real users. And at that point, you've invested so much in trying to make it work that you can't just go back, so you start piling weird hacks on top of weird hacks.
For the third time, we went with react-native. Overall it was a great experience and unlike ionic, it's a real native app, not just a webview. We could reuse a big part of the code between web, ios and android. The issues we faced were often related to weird edge cases that are buggy within react-native itself such as input fields not working correctly when dictating or a "pull-to-refresh" supposed to be stateless but in practice being stateful and buggy if you call "refresh" on it twice within 30ms. However, it's a good feeling to know that when we'll have the time, we have the flexibility to either fix the library itself or re-write it (compared to ionic where we couldn't do much and web apps where the solution to most our problems would be to "wait a few years until the browsers decide to improve it".)
If I had to do it another time (a fourth time), I'd go with react-native again but I would make sure to stress test the libraries with real data on all the devices we'd want to support. Also, it's popular in the javascript ecosystem to have libraries that depend of another library that depends of another library that wraps another library.. in most cases, it's just better to write a quick wrapper for your app and only include the inner-most library that does most of the work anyway. Otherwise you're depending on too many authors and libraries quickly go out-of-sync and you're stuck with old versions that aren't compatible with new ones.
We are a stealth startup working to fix the software doctors use. If you have seen what physicians have to put up with, it's a bad version of the 90s, and makes medical care worse and more expensive for everyone. We are a group of previously successful engineers and entrepreneurs (MIT, Dartmouth, Datapower, Stripe, Salesforce, etc) and senior doctors (Johns Hopkins, UCSF, etc) who are determined to finally fix this.
Senior Frontend Engineer: - help us delight physicians with great UX that helps them take care of patients
Requirements: - production experience with react.js, redux & related ecosystem - strong general programming skills - success in shipping complex products Strong pluses: - react-native and/or other mobile experience a plus - passion for great UX - experience with enterprise products and/or healthcare IT
Compensation: market salary & equity -- we are well funded.
Stack: includes Rust, React and Node. We will also be solving some very interesting problems in the areas of UX, APIs, and fine-grained application security.
Please email jobs@commure.com and mention "[hnmontreal]" in the subject line.
Then, quite simply, your options are a) Find product/market or b) Quit.
To decide between a) or b), try to think how close you are to getting it. Do you have a few users that love your product but the pricing is wrong? Did you find something interesting in the market that you think you can compete on but didn't execute well-enough?
I would say if you lost your passion and don't think you've got something interesting enough to get a few users to love your product, then it's time to quit and (maybe) start over on a fresh idea. If on the other side you're still passionate about the space and think you're onto something, then keep trying.
In the end, I find Rust to strike the right balance between expressiveness and correctness. Unlike C/C++ where you can shoot yourself in the foot, with Rust you're forced to write thread and memory-leak safe code. And in the end, Rust code often look much cleaner AND safer than the C++ equivalent.. what's not to like.
We are a stealth startup working to fix the software doctors use. If you have seen what physicians have to put up with, it's a bad version of the 90s, and makes medical care worse and more expensive for everyone. We are a group of previously successful engineers and entrepreneurs (MIT, Dartmouth, Datapower, Stripe, Salesforce, etc) and senior doctors (Johns Hopkins, UCSF, etc) who are determined to finally fix this.
Compensation: market salary & equity -- we are well funded.
Stack: includes Rust, React and Node. We will also be solving some very interesting problems in the areas of APIs, domain-specific machine-learning and fine-grained application security.
Please email jobs@commure.com and mention "[hnjobs]" in the subject line.
As a side note, it would be great to have more programming books written like this. I.e. We assume you already know language X so here are the differences and why; focusing mainly on specific code examples and gotchas of the new language.
I would prefer semi-pseudocode:
import { drawDragon } from 'drawing'
<other imports..>
function(screen) {
screen.render(drawDragon.new('red'))
}
As a fun exercise, one could take a big programming book and trim it down to a 1/10th (or more). There are so many useless sections. Most great devs are good at skipping through the bullshit.. why not just remove that part entirely!
Reason is probably monetary or politic. I.e. can sell to a larger audience by being more beginner friendly and/or need to have a certain amount of page and follow a template to be published.