cstavish

Proscia | Front-end Engineer, Back-end Engineer, DevOps, Research Engineer, Machine Learning Systems Engineer | Philadelphia, PA | Full-time | Onsite

The data to fight cancer is in images--specifically, gigapixel scans of tissue. Proscia is working to make pathology diagnosis more accurate and more efficient through the thoughtful application of artificial intelligence. Proscia's software is in use in laboratories today and has been adopted by world-renowned medical centers.

Our data currency is high-resolution virtual microscopy images, affording unique challenges and growth potential to all technical roles. This isn't another digital health CRUD app. If you're interested working on a meaningful problem alongside talented and good-natured colleagues, send me an email at coleman [at] proscia.com.

We offer competitive salaries, equity, health/dental/vision/disability and relocation assistance.

Those familiar with the field will recognize an augmented reality microscope as an incomplete alternative to, or stepping-stone towards AI applied to whole-slide images, which are multi-resolution images of more or less identical quality quality to that of a microscope.

For some use-cases, deploying AI to microscopic fields of view is a viable, lower-cost alternative to creating whole-slide images and running AI on them in their entirety (whole-slide scanners are a bit expensive). Specifically, if a pathologists identifies a suspicious region, the augmented scope can provide useful support. However, many types of anatomic pathology assessment require laborious review of several slides. Only AI applied to whole-slide images can pre-identify rare events or "hot spots", saving pathologist time while improving diagnostic confidence.

Sapiens?

In a similar spirit, the Bloomberg Businessweek magazine used to have zany cover designs (my favorite featured a sweaty Steve Ballmer in a Clippers jersey dribbling a basketball captioned "BASKET BALLMER") but they've since switched to plain, solid colors.

Programming Pearls by Jon Bentley.

Accredited investors/VC (disclaimer: I am neither, but co-founded a VC-backed startup) are often wary of crowd funding because of the idea that with more investors, the more headaches that can occur with additional capital raises. Having a big cap table doesn't make company operations easier. I honestly don't know how valid those viewpoints are, but that's what I've heard.

> as I don't know if pulling venture capital is as easy as selling the stock.

There's generally minimal liquidity. During a round, an existing investor may have the opportunity to sell some shares to new/other investors, but if she knows something that's not coming out during diligence, there's definitely something fishy going on. If the round is shaping up to be a major up-round, maybe an early investor wants to lock in a good return, but that's beside the point here. And then of course if things really aren't going well for the company, you're looking at the bad kind of liquidity event--a liquidation.

So if a VC wants to pull out based on a negative hunch, it's probably either impossible or the signal itself will doom the company if it wasn't already doomed.

Just my 2 cents as a first-time founder.

Thanks a million, from me and the people who invested in my startup.

edit: apparently SNI isn't supported on legacy dynos.

In 2014, while in college, I did a co-op rotation at the Bombardier Transportation facility in Pittsburgh, PA. The rail division may be based in Germany, but there's a sizable rail engineering contingent in Pittsburgh. I worked with a lot of good people and engineers there--I hope they do alright. Even in 2014 there was grumbling by the engineers about upper management, and I remember attending an "all-hands" meeting where a visiting executive talked of belt-tightening. In a fairly tone-deaf delivery, he spoke of limiting his own business-class international travel.

I use JSONB columns for similar use-cases, but to play devil's advocate, you can accomplish that a fourth way, which is almost certainly better than 1 or 2. A table for fields, one row per field. A table for forms, which has a many-to-many relation to fields. Entries in a link table compose a form of arbitrary fields. Answers can be stored in a separate responses table, indexed by form_id and column_id. I don't know enough about database implementation to speculate on how that would perform at scale, but conceptually that's how I think of the problem.

This is great news; I had been waiting.

Apt reference, but to be clear, it is Donny who jumps on the Dude's attempt to quote Lenin, and Walter who scornfully corrects him, "V.I. Lenin-- Vladimir Ilyich ULYANOV!"

While I largely agree with you, not all ads need to be clicked in order to be considered effective by the advertiser. Look at a Coca-Cola billboard, for instance. There's no action item to call this number TODAY, etc. Just brand reinforcement... And that's valuable to many companies.

The example of the pizza ordering is technologically impressive, yes... But from an end-user perspective it is at best "as hard" as calling the pizza place and talking to a human taking your order.

There are many use cases where it could actually provide value, but I found it funny that they chose to demonstrate one to the press that really afforded end-users no advantage.

This is ironic. It used to be the analog medium that had a sort natural copy protection built in.