clinth

GOG is excellent for this reason and my experience playing older/unsupported games from them is top-notch. It stings to buy an older game again, but they're almost always inexpensive, and you can say, "Well, this is the very last time I'm going to purchase HoMM3" (or your game of choice).

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 get where you're coming from, but go to Stadia's page. Click "Buy Now". You land at $130 plus $10/month with no other options. This isn't a future product or preorder, this is launch. The hardware and service are live right now. If you want to play: $130 plus $10/month.

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.

Right now, $130 is the only edition. I think the one you're talking about comes out next year.

New York Genome Center | Software Engineer | New York, NY | Full-time | ONSITE

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.

We do not, we're a combination of grant-driven research, production/clinical genome sequencing, and scale computing; the work is hard to structure for ad-hoc volunteer contribution.

Doing software work in support of scientists trying to cure cancer. Scientists aren't curing cancer with a notebook and pen, they have have problems that a software engineer can really help with. Boring internal software, with some public-facing software.

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.

Agreed. I love Thunderbird, and gave it a shot last year as my work email client (exchange). Loved almost everything, but ultimately the search and lack of threading sent me back to outlook web access.

A Short History of Nearly Everything, by Bill Bryson -- https://www.goodreads.com/book/show/21.A_Short_History_of_Ne...

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

New York Genome Center | Princpal Software Engineer | New York, NY | Full-time | ONSITE

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/

GOG is a good curator/vendor for old games. A fan put together a list of scummvm-compatible games here:

https://www.gog.com/mix/games_compatible_with_scummvm

I love it but use it only to view and process notes/deadlines/status from my mothership org files (maintained on non-mobile computers). I don't think I'd use it as a primary note application.

I get what you mean, but would argue that, "it only takes 2-3 trolls plus 300 people who respond to them to create a 300-comment shitshow". An ignored troll is a powerless troll. They get their power to disrupt from the responses, not their words.

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?

Scheduling a meeting for 5am does not overlap with most people, while scheduling a meeting at 3pm does. You understood that when you scheduled it for a time that you were available and your coworkers weren't.

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.

I have a ton of respect for people who choose not to have children, for whatever reason. Good on them. I think the societal drive to marry and have children is bullshit, especially for women. You can be a fully-realized person without children.

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.

Yes, No, Yes. However, it's possible to be a parent, read and understand his position, and not get into personal attacks. I respect Stallman a mountain, including his choice not to have kids, but the essay is muddied.

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.

Thanks for asking, I've updated the listing. You can use the NYGC careers page; also happy to respond to direct question via the email listed on my personal home page.

New York Genome Center | http://www.nygenome.org | SoHo in New York City | ONSITE

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.

Mercury/amalgram fillings isn't the best example, but biocompatibility is still the primary constraint.

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:

https://medlineplus.gov/ency/article/002495.htm

It's been quite a long time since I studied this, but the primary problem with materials in implants is the quality of being bioinert. Many titanium alloys are not bioinert. Any combination would have to be tested separately.

Requests - https://github.com/kennethreitz/requests.

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.

Why embed the message in an image, instead of text?

I don't really get why giving only 25%?

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.

It's a slideshow, probably intended to accompany a presentation. I used my right and left arrow keys to navigate.

while I can see not wanting to provide a full movie metadata API, having "is this or is this not available on Netflix right now" seems like a really important API to have, one that allows websites people use to browse and find movies to funnel users into Netflix (and seems a natural fit for their very popular affiliate program).

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 haven't worked at companies who think along these lines, but friends of mine in the private sector have received bonuses similar to those they'd get for excellent annual performance: a stock grant or cash bonus ($3-5k, although I'm sure it varies).

Small correction: you get a year of Prime free with purchase of the phone, and if you're already a Prime member, they extend your existing membership by one year. This is way down the page though.

I'm really surprised that they didn't feature this information in the price displays themselves for existing Prime members.

Cross-platform: Dropbox, Sublime Text, Toodledo, Balsamiq Mockups, Pinboard, Newsblur OSX: Alfred 2, Dash, Pixelmator, Clearview Win: ExpanDrive Other: Linode, Dreamhost (legacy)

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.

It might be weird, but I'm a thank-you letter writer. I wouldn't write those exact letters, but I've written similar sentiments.

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.

How great do Yahoo's investors feel that their CEO is spending her time on trying to be designer instead of streamlining and turning her company around.

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.

I was a technical reviewer of that book (although no knowledge of PCI in practice), and I found it to be less moment-specific and more general grounding and strategy than I expected. It really is a good book.