81–90 of 734 posts
In real estate, developing with MLS data. - There are over 900 regional MLS providers each with different schemas. - You use RETS, a complicated, non web standards interface for downloading data. - MLS data is plagued with errors and denormalized data making queries difficult.
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…
As a SaaS provider, one of the key indicators of a customer at risk of churn is the presence of another competitor in their account. A service which notifies you once an account signs up for a competing service would be immensely valuable in helping to target retention activities.
These questions pop up every now and then, and while I get the intent, you're not gonna get anything useful out of it. The idea that someone who knows how to code can disrupt an industry that they are not a part of is disingenuous, and the examples that you can find are exceptions, not the rule. It's also extremely naive and presumptuous...what makes you think people in the industry haven't already tried? People who…
So they are imensly useful and many time more relevant than most other discussions about building companies.
Think somewhere on the order of 10,000 models per day throughput.
There's $BNs waiting for you. It's ridiculously hard.
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…
There are good open source options for each step here - is the solution you are looking for just a UI and easy install process? Or would your ideal solution make all of the decisions for you - data structure and format, which data is/isn't valid, what output options are possible, managing server resources, etc.?
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…
Have you got an example/names of existing software? I'm interested to see what kind of features they have.
You need computational geometry, computer graphics, and structural engineering expert level domain knowledge to implement anything. You need to create traditional 2D machine/construction design drawings from the 3D models. Then you need to sell it to corporations, whose work, most of all, must be dependable and free of guess work.
You need to know what sort of geometries you can use to model the reinforcements. Then you need to know how to design the system so it can handle very large amounts of geometry.
The worst of all is you need to deal with god awful industry standard formats- DWG, DGN, IFC, Step/Iges and so on. Maybe DWG import and export first.
To have any real chance you need a guy or two who are good with numerical code, someone who is familiar with e.g. Game engines, soemone who knows computer graphics, a structural engineer to tell how he does his job and what the thousand inconsistencies in the field are (this is not a trivial domain like housing or transport), a sales/marketing guy to connect and push the product.
And, like someone else estimated, the potential market is not gigantic - which is kinda funny because we all depend on reinforced concrete but don't need so many engineers for the design work...
I would suggest we make a monthly of these as they provide important insight into industries.
Content and patch distribution for video games: Data integrity, progressive downloads, file-level patching, compression, encryption, and platform/version branching. It's quite mind-boggling; nobody is really doing it on an industry-scale level. Every video game developer has their own way, all of which have their own problems. It is a very hard problem. Blizzard actually came up with a very good system, but it's not…
Quoting Wharf's spec intro:
Wharf is a protocol that enables incremental uploads and downloads to keep software up-to-date. It includes:
A diffing and patching algorithm, based on rsync
An open file format specification for patches and signature files, based on protobuf
A reference implementation in Go
A command-line tool with several commands
It is used to power itch.io's Steam-like application, itch: http://itch.io/app, delivering multi-gigabyte game installs & updates.
These questions pop up every now and then, and while I get the intent, you're not gonna get anything useful out of it. The idea that someone who knows how to code can disrupt an industry that they are not a part of is disingenuous, and the examples that you can find are exceptions, not the rule. It's also extremely naive and presumptuous...what makes you think people in the industry haven't already tried? People who…
Uh, no. The idea is that you identify the problem, build the team to solve it, build something quick that can prove that you can solve it in a better way than others, iterate to the point that CAC < LTV, scale.