itajaja

android is currently under development

Yes you are right, except for the fact that this probe uses a silicon chip instead of a piezoeletric ceramic transducer, and that's exactly the reason why it costs 2000 dollars.

Butterfly Network | Senior Cloud Engineer | NYC | Full Time, Onsite

We just unveiled our first product[1][2][3] and We are looking to expand our team of engineers. For our cloud team, we are looking for the following skills:

- track record of shipping or maintaining modern cloud systems in production

- python (Flask, Django)

- SQL Databases (Postgres, MySQL)

- javascript (react, webpack, ES6, node, graphql)

- docker, kubernetes

- knowledge of internet protocols, REST, microservices architecture

- Unix

- previous experience with medical imaging technologies and systems (PACS)

You can contact me directly at gtagliabue[at]4catalyzer[dot]com or careers@butterflynetinc.com. For a full list of open positions, visit: https://careers.smartrecruiters.com/4Catalyzer

http://butterflynetwork.com

[1] https://news.ycombinator.com/item?id=15588711

[2] https://www.technologyreview.com/s/609195/this-doctor-diagno...

[3] https://www.forbes.com/sites/matthewherper/2017/10/27/an-ent...

Engineer at Butterfly Network here, very excited to see interest on HN. As you can imagine, we are hiring, there are a lot of very interesting open opportunities https://careers.smartrecruiters.com/4Catalyzer

Butterfly Network | Cloud Engineer | NYC, NY | ONSITE

At Butterfly Network we are building a device that will make medical imaging accessible to everyone in the world. It’s a breakthrough that will save millions of lives.

As a full-stack cloud engineer you are expected to take ownership of several aspects of the architecture and to be able to contribute at different levels. Here are some of the technologies being used and skills required to apply (knowledge and experience in all of them is not mandatory)

• 3 or more years of experience developing flexible cloud-based computing environments

• Experience with cloud computing leveraging AWS

• Experience with Docker and Kubernetes

• Comfortable with Linux system administration

• Experience with modern web frontend development (React, css modules, ES2017, Webpack)

• Experience with designing RESTFUL APIs for a microservice architecture

• Experience developing with Python environments

• Experience developing with NodeJS environments

• Experience with Graphql or similar technologies

• Experience with scripting, management, and automation tools for CI and CD

• Experience developing high availability systems and software for fault-intolerant applications such as medicine, scientific computing, aerospace, and finance

• Experience with fast and agile development life cycles

Apply through https://angel.co/4catalyzer/jobs/40282-full-stack-cloud-engi... or email me at gtagliabue @ 4catalyzer.com

https://www.butterflynetinc.com

4Catalyzer/Butterfly | Sr Full Stack Engineer | NYC | ONSITE | Full Time

At 4Catalyzer we work with different startups that aim at reshaping the status quo of medicine, especially through devices, deep learning/AI, and cloud based services. it's a very unique and stimulating environment, where people from the most disparate background (ASIC, software engineering, mechanical engineering, chemistry, biology) work together on very ambitious projects and we are looking for extremely talented and motivated people. We got extensive funding and unique opportunities to work across multiple projects and startups and build an interesting and diverse portfolio of stock options. Here is a short list of technologies we use and some high level skills we are looking for: docker, kubernetes python (Flask, Django) react, webpack, ES6, node, graphql experience with CI/CD pipelines REST microservices track record of shipping modern cloud systems in production

https://angel.co/4catalyzer/jobs/40282-full-stack-cloud-engi... or email me directly at gtagliabue[at]4catalyzer[dot]com

Butterfly Network | New York City or Guilford, CT | Full Stack Engineer We're a team of world-class scientists and engineers working to build the next generation of low-cost, ultraportable medical imaging devices to really change how medicine works. We need you to help us make the software as awesome as the hardware, and build an integrated system that will bring laboratory-grade medical imaging to everyone. Email me at gtagliabue at 4catalyzer.com or learn more at: https://www.butterflynetinc.com/#opportunities Some of the technologies we use: docker, kubernetes, python (Flask), postgres, react, graphql, node, react native.

Butterfly Network | New York City or Guilford, CT | Full Stack Engineer, Mobile Developer (React Native)

We're a team of world-class scientists and engineers working to build the next generation of low-cost, ultraportable medical imaging devices to really change how medicine works. We need you to help us make the software as awesome as the hardware, and build an integrated system that will bring laboratory-grade medical imaging to everyone.

Email me at gtagliabue at 4catalyzer.com or learn more at: https://www.butterflynetinc.com/#opportunities

Some of the technologies we use: docker, kubernetes, python (Flask), postgres, react, graphql, node, react native.

Very true. Our builds are very slow, and they could be much faster if docker caching worked properly. Seems like these issues will be solved soon with the next major release of the platform. Let's hope

just for curiosity, what do you use for creating a k8s cluster on aws? Do you use any of the available open source tools like kube-up, coreOS on aws, kops, etc? And if I decide to stop using distelly and preserve the cluster created, will I be able to do so?

But that option requests a Key Name. What that key would be? there is no arn identifying a kubernetes cluster on aws. It also requires aws credentials, but if distelli manages the kubernetes cluster, you can't do much with the aws credentials

hi @kt9, in the kubernetes dashboard, when adding an existing cluster, under "Select a Provider" there is AWS. that means that it also support ECS? I am not aware of AWS supporting kubernetes directly. I have a k8s cluster running on an aws autoscaling group, but I guess in that case I should just click "Other". What's the AWS option for then?

our strategy is to have two dockerfiles for each repo. The main Dockerfile and a Dockerfile-test, that builds FROM the main one and contains the test dependencies. during CI we first build from the main Dockerfile and then from the second one. since the test one builds from the main one, there is no significant overhead and it's usually a very fast build. we run the tests on the test image and if they pass, we push the main image to the tests. This means that we do not in practice, deploy the same image we test, but it's pretty close to that. It just requires some discipline to make sure that the test one just adds test dependencies and nothing more to be as similar as possible to the main one. We use circle for continuous integration but distelli looks really cool. Something that circle and travis don't give you is a pipeline feature. Having a system that is aware of your cluster technology enables some nice pipelines and better control

Same question. Hopefully they are going to extend it soon, I see no reason why bikes are left out

The plugin author should definitely be blamed for this. But I think that the root problem is with the `teacher` npm package. An issue[0] was also opened just 6 days ago raising doubts about using http.

[0] https://github.com/vesln/teacher/issues/4

We use dumb-init[1] to handle containers with multiple processes when it's necessary.

[1] https://github.com/Yelp/dumb-init

Shamelss plug: We are using flask-resty [1] for our microservices and it's awesome. it uses sqlalchemy and marshmallow and the resulting code is very terse and declarative.

[1] https://github.com/4Catalyzer/flask-resty

That's true, but even not updating such part is a symptom. I don't want to compare different ecosystems and culture, and I am very excited to starting to learn python overall, but you hardly see such things in a project of comparable size in the node or ruby world. As I said, I am loving python and Flask, but this is a symptom that the topic is not as hot as I though it should be.

I started learning Python a week ago and I sat in front of the computer for hours trying to solve the same dilemma. If you look at famous Python projects, eg Flask, they still advocate for Python 2 over 3 in their documentation[1]. I found it extremely unsettling, to find the python community still so divided, after so many years. I eventually decided to learn Python 3 because I couldn't accept the idea of learning a legacy technology. But until the important projects don't take a strong take in advocating Python 3, I fear the conversion from 2 to 3 will still take a long time. My hope is that the big Python players will start regarding Python 2 as legacy ASAP. From an outsider perspective, this python 2-3 seem ludicrous, and I am sure that it gives a very bad impression of the python community.

[1] http://flask.pocoo.org/docs/0.10/python3/

I don't know if I would use branch restriction, it sounds like an anti pattern for the git philosophy (SVN file locks, anyone?). Why would I commit to someone else's branch, unintentionally? I think that a "gentlemen’s agreement" as your link states, is more than enough. Can you provide a use case where this feature is useful? Do you use it often in your workflow?

The new collaborator feature makes it easier to include stakeholders in the communication loop.

The feature I really think github is lacking right now is the ability to give selective permission to some sections of the repo (issue|wiki|code|releases). Right now the only way to share issues but not the code is to create a separate repository, which is cumbersome to do and maintain for every project.

Adding to babel and traceur, Typescript is catching up with all ES6 features, so you can use destructors (discussed [here](https://github.com/Microsoft/TypeScript/issues/240)) in Typescript v1.5--beta

I agree with that. All these features are amazing, but the fact that these modification must be only additive make their implementation feel clunky.

Javascript was born with enormous defects that it's too late to remove, and adding new features, regardless of their undoubtable usefulness, make the whole language more difficult to handle. The number of concepts required to read ES6 is far more than the one required for ES5, and this number is just destined to get higher and higher, with no possibility to decrease.