231–240 of 734 posts
We'd like to run learning algorithms on robots, but there are no great options for hardware. (Happy to discuss in depth if someone wants to build it)
We want to train large models much faster than any GPU box you can buy. (There are several new things announced, but there's room for more).
A monthly subscription service for a fee of $5 - $10 where every month I get a new kind of quirky instrument (shaker, wind, wood block and stick, whistle, triangle, or other noise maker) as a surprise by mail. The point of the service in the music industry is to inspire new sounds and the device can either be kept or given away to somebody without a lot of second thought. Getting stuck is a big problem. Also in music…
$5 doesn't even pay for shipping, sadly. Amazon still pays a average of $6 per order.
I feel like there's a big opportunity for a tool/tools that are installed in apps as a package and then customized from there. Many teams build a version of this in house (Instacart open-sources theirs), and I think it should be a product.
A ticketing system that doesn't sux (I like RequestTracker, but it shows its age). Top players are ridiculously overpriced. My management style is like this: every task/request is numbered, placed in a queue and assigned to a professional. What I expect from my ticketing system: - every manager should be able to assign tasks to someone and set the order they must be executed. He needs know what his team is doing and…
I blogged recently about some problems I have with JIRA: http://www.storytotell.org/constraints-and-semantics/ In a nutshell, I argue that the problem with most ticket systems is that they do not constrain the domain enough, so they wind up having similar problems to email (sifting through a chronologically-ordered pile of text rather than structured, semantically-ordered information). Your comments make me think the…
In fact, my usual approach to dealing with tickets/issues/emails which start to develop this problem is to make my own private copy of the thread and edit it in precisely this manner, though I'm the only one this benefits since it doesn't get sent back upstream.
Everyone I know in law is dissatisfied with every part of their tech stack. If someone could come up with an integrated SaaS solution, and be SUPER careful about compliance... they would be printing money.
Curing congestive heart failure. We're not even close. The space is ripe for disruption by a team of Growth Hackers with a foosball table.
Not my industry, but a friend of mine in law was discussing how incredible her in-house software is for managing billable hours relative to all her past companies. I poked around, and most law firms, even very deep pocketed ones, use somewhere between a bad tech system and no tech system to manage and track their work. A small team could easily collaborate with some law firm (maybe take an investment from a few law f…
Immigration. Every time I change jobs as an H1-B employee, I've to fill in the same ridiculous data with every law firms weird interface. I wish the US Digital Services would focus on streamlining forms and having auto-import from all the data they already have about me (e.g. automatically translate I-94 records to how much time I actually spent in the US, infer my past I-797 records automatically, have a one time ed…
Unfortunately any assumptions built into an immigration business are likely to be upended soon. I'd wait at least a year before trying to solve this problem because the regulatory environment could break your resulting startup.
I'd say closer to four to be safe.
As a structural engineer, I see a good opportunity to make reinforced concrete design software available in a SaaS format. The competition is outdated, clunky, requires local installation and messing about with licenses. Design firms are paying $1000-$3000/year per user/seat for what amounts to a pretty basic app. Unfortunately, there are very few people that understand both computer science and structural engineerin…
I suspect much engineering software is ripe for innovation. My wife is a Water Resources Engineer- a specialized form of Civil that focuses on "when it rains, where the hell is all this water going to go?". The software for that kind of modeling is apparently pretty basic, pretty expensive, buggy, etc.
Data management. 1) Cleaning the data as it comes in rather than in batches so we can use it sooner, invalid data is discarded, outlier detection, normalizing inputs etc.... 2) Warehousing of the data with proper indexes so you can perform some advanced queries on unstructured data 3) Some data is sent in bulk at the end of day, some of the data is streamed in fire hose style. How can we preprocess the fire hose data…