228 karma · joined March 12, 2010
- work: www.crayon.co
- email: clint DOT howarth AT gmail DOT com
They also do fine as a purchase platform for modern games, but it's less than perfect because modern games are supported and some smaller publishers choose not to push updates to their offerings on GOG.
I think this release structure is pretty daring. They're getting a lot of bad press, it's expensive, it's not a smooth experience. Also, if nobody gets on this holiday season, I'd expect game developers to throttle on putting money into optimizing for the platform, which would begin the platform death spiral.
NYGC is not a software company; it is a sequencing lab trying to push science at scale, and needs software to do so. We are hungry to become the lead sequencing firm. We're aggressively building our clinical services, so if you have even the smallest allergy to documentation or process, please stop reading now.
These positions is for the Production Software Engineering group, which currently has twelve people. We're replacing prototypes with better solutions while rolling out new applications to help the organization with scale. People who join NYGC software are expected to learn quickly, be self-motivated, and be comfortable switching tracks. You don't have to understand e.g. genome sequence alignment, but you do have to be able to read a manual on a tool's use and learn enough vocabulary to have an intelligent conversation with an expert on the subject.
We are intentionally boring (https://valdhaus.co/writings/boring-systems/) in our technology choices because our goal is data analysis, not novel software work. We design everything for reliability, maintenance, low cost of ownership, and failure recovery. It is a combination of boring technology and fast pace: we are the computational pipeline team, the automation team, the LIMS team, the database team, and the data transport team (surprisingly fun at >20PB), the customer delivery team. We don't do genomic methods software (e.g. better variant calling) -- we have a great computational biology group for that. This group is focused on making a sequencing lab and automated analyses run at scale.
The lab and automation combined drive some really interesting real-world problems, particularly in the clinical space. How fast can we get first-order cancer screening done for people?
(contact info in my profile)
POSITIONS
1) Principal Software Engineer: Serve as a project lead. This person should be able to work independently and in a team, from requirements through implementation/iteration and testing and deployment. Python and postgresql on the backend, React on the frontend. We're looking for someone who has both python application development experience and javascript/front-end experience.
2) Senior Software Engineer: Serve as a primary contributor. Strong individual and team contributor, familiar with breaking down tasks into work plans, and then driving those plans through design, implementation, testing, and deployment. Python and postgresql on the backend, React on the frontend. We're looking for someone who has either strong python application development experience or strong javascript/front-end experience and is willing to learn/work in python.
It's not glorious work, and your team is typically understaffed and overworked. There are tradeoffs in the job, it's not for everyone. I work at New York Genome Center, and at the Broad Institute before that, both are nonprofits, and there are plenty of firms with software jobs out there where you can do "just software" and help with something meaningful.
Drop me a note, I'm happy to talk about this more. I missed the monthly jobs thread, but my group is hiring.
First half of the book changed my life, and second half is merely good. I wrote a full review [0], and eight years later, that first half has become one of my favorite reads ever.
[0]: http://www.spaceponies.com/review-of-a-short-history-of-near...
NYGC is not a software company; it is a sequencing lab trying to push science at scale, and needs software to do so. We are hungry to become the lead sequencing firm. We're aggressively building our clinical services, so if you have even the smallest allergy to documentation or process, please stop reading now.
This position is for a Principal Software Engineer to serve as a project lead. This person should be able to work independently and in a team, from requirements through implementation/iteration and testing and deployment. We use python and postgresql on the backend, we have just chosen React on the frontend. We're looking for someone who has both python application development experience and javascript/front-end experience.
We are intentionally boring (https://valdhaus.co/writings/boring-systems/) in our technology choices because our goal is data analysis, not novel software work. We design everything for reliability, maintenance, low cost of ownership, and failure recovery. It is a combination of boring technology and fast pace: we are the computational pipeline team, the automation team, the LIMS team, the database team, and the data transport team (surprisingly fun at >20PB), the customer delivery team. We don't do genomic methods software (e.g. better variant calling) -- we have a great computational biology group for that. This group is focused on making a sequencing lab and automated analyses run at scale.
This position is for the Production Software Engineering group, which currently has thirteen people. We're replacing prototypes with better solutions while rolling out new applications to help the organization with scale. People who join NYGC software are expected to learn quickly, be self-motivated, and be comfortable switching tracks. You don't have to understand e.g. genome sequence alignment, but you do have to be able to read a manual on a tool's use and learn enough vocabulary to have an intelligent conversation with an expert on the subject.
The lab and automation combined drive some really interesting real-world problems, particularly in the clinical space. How fast can we get first-order cancer screening to sick people? More formal description under "Principal Software Engineer, Applications" on our careers page: http://www.nygenome.org/careers/job-positions/?sc=7389/
I like this idea, but I don't think it's possible to get the shared agreement you discuss. I've never seen an online community where the hands-off, community-ignore method worked. Have you seen one?
They're not wrong for wanting what they want, and you're not wrong for wanting something else. Find a job where you don't have to be online at 3pm sometimes or 6pm anytime. There are good jobs out there that will accommodate that.
Having said that, it's not a bad choice to have children. This essay covers a lot of ground very quickly, but the part about effort distribution resonated with me and I disagree with it. Yes, career plus family are challenging, but I'm glad I have both.
There's never 100% done with with anything, including parenting and work. I don't know a single person who has fully accomplished everything they want to do, no matter how singly focused they are. I don't know what 100% parenting would look like. Kids aren't sculpture which stop progressing when not being worked. They're people. Yes, as a parent you spend time with them, and thinking of them, but you're not failing when you're thinking of something else.
It starts with explaining why it wasn't good for him and continues on to urge others to not have children, with the reasoning that not everyone will read this essay. It's not a complete thought. It's like saying that you've seen bad software projects, and the time for those people would have been better spent somewhere else, so everyone reading this comment shouldn't do software, because there are more than enough software engineers. There's a better version of this essay within itself.
New York Genome Center is a nonprofit in SoHo aiming to become a leading sequencing lab and general driver of genomics science excellence. NYGC's partnerships with nearby top-tier hospitals in Manhattan enable unique human analysis studies. We have both junior and senior software engineering positions available. The group is a mixed local/remote team, but all of the currently open positions are ONSITE. Our interview process is phone conversation followed by onsite interview.
NYGC is not a software company; it is a sequencing lab trying to push science at scale, and needs software to do so. We have gone from zero to top-three in five years, and we are hungry to become the leader. We're aggressively scaling our clinical services, so if you have even the smallest allergy to documentation or process, please stop reading now.
These positions are for the automation group, which currently has ten people. NYGC is graduating from successful startup to a medium-sized company. In software, we're replacing duct tape with small applications, and introducing larger applications to help people with scale. We also introduce duct tape to make impossible things happen. People who join NYGC software are expected to learn quickly, be self-motivated, and be comfortable switching tracks. You don't have to understand e.g. genome sequence alignment, but you do have to be able to read a manual on a tool's use and learn enough vocabulary to have an intelligent conversation with an expert on the subject.
This group uses python and postgresql, adding minimal javascript when making frontend applications. We are intentionally boring (https://valdhaus.co/writings/boring-systems/) in our technology choices because our goal is data analysis, not novel software work. We design everything for reliability, maintenance, low cost of ownership, and failure recovery. It is a combination of boring technology and fast pace: we are the computational pipeline team, the automation team, the LIMS team, the database team, the data transport team (surprisingly fun at >20PB), the customer delivery team, the JIRA team. We don't do genomic methods software (e.g. better variant calling) -- we have a great computational biology group for that. Our team is not Agile, but our business is. We make it all run at scale, on our local cluster of >6k cores. This group is focused on making a sequencing lab and automated analyses run at scale.
The lab and automation combined drive some really interesting real-world problems, particularly in the clinical space. How fast can we get first-order cancer screening to sick people? If you want to be part of a growing firm that drives science with stable software solutions, please drop me a note or use NYGC's careers page.
Mayo clinic has a good overview and timeline regarding the discovery process for cobalt-chromium, which was previously thought to be a good all-around implant material:
How to make a usable api. The decisions that went into each method call were fantastic. Great test coverage as well. I use package in most python development.
Valve took their ~30% platform charge, and left the remaining amount to be split per the discretion of the publisher of the game, in this case Bethesda. Bethesda chose to give mod makers roughly 1/3 of the money left, resulting in a final split of Valve 30 / Bethesda 45 / mod author 25.
Wouldn't that API use would also funnel users to its competitors in the case that Netflix doesn't offer the movie you were looking for?
I see their API closing as a natural business decision — anticipating a time when streaming services are a commodity and margins are thin on streaming licensed content they don't own. They'll have to compete with something else: their core service, their own content, and their recommendation engine (which I find to be fantastic). A public API fights against the recommendation engine. They want you to sit down and watch Netflix, not a movie in particular.
I'm really surprised that they didn't feature this information in the price displays themselves for existing Prime members.
Funny enough, my home machine is Windows and I spend far more money on productivity tools for my work (OSX) machine. I'm not counting Steam.
I've written my CEO, because I live in a house I bought with money earned from this job, raising a family of three kids, and appreciate that my enterprise is sustainable. I'm grateful for my job, the opportunity to do the work I do, and to the people who make it happen.
However, I write a half-dozen or so such letters per year. Not just professional: personal, community, and so on. This rate is trending up as I get older. I'm getting more and more grateful for how our lives all fit together. There are many people working hard toward good ends and probably not being thanked for the good work they do.
Depends how it turns out. Steve Jobs spent a lot of time on details, with the argument that one guiding vision has value. If it works, you're a visionary.