3 ms·
This is the hardest thing to explain to people about companies like ours. When I say that machine vision systems are comparable to building hardware people can'
by AndrewKemendo 10y ago
This is the hardest thing to explain to people about companies like ours. When I say that machine vision systems are comparable to building hardware people can't conceptualize that because they have never really worked with novel CV/ML systems.
I think this post has it right too in that finding a small application of the technology is a good approach to sustaining yourself while you get to a bigger goal. This however adds a magnitude of complexity - which means funding requirements aren't that much smaller. For example you have to build a product while also building the technology - vs just building a product on exiting technologies, which is hard enough itself. It's also a risk because if that one product is not a winner, then it poisons the larger play - even though it might be itself very valuable.
The challenge comes when you have to explain that, no actually this first thing is just the POC for a larger thing we're trying to do - especially when you are building the market for that larger thing.
I think the best path for hard tech companies is to have a lot of money from the start. I know that sounds obvious, but I think it's true specifically for hard tech companies.
Unfortunately that usually means you as a founder are a known entity in the venture world. Whether that means you use your own money from a previous exit (like Musk) or convince someone to fund a lot of it (probably because you had a previous exit and have connections) you need a lot of capital up-front.
So if you are an unknown to the people with cash, with hard tech plans, prepare for a tough time ahead.
- tedmiston 10y agoI'm not super familiar with your company. Does the approaching of building the smallest nucleus of your tech like Sam described work for Pair? A glance at Crunchbase looks like you are seed stage so maybe this is a real pain point right now. > Very often, the first thing we do is help hard tech founders find a small project within their larger idea that fits the model of quick iteration and requires a relatively small amount of capital. This project is often the smallest subset of their technology that still matters to some user or customer. It may at first look like a detour, but it’s a starting point that lets founders build measurable momentum–for themselves, for recruiting employees, and for attracting investors. Edit: The realtime 3D object placement in the demo video [1] is incredibly cool. I've done enough computer vision to realize you have some non-trivial technical work, but I'm not sure if I would label it hard tech personally. I think the gray area is all around the real-time constraint. [1]: https://angel.co/pair-2 https://angel.co/pair-2
- AndrewKemendo 10y agoDoes the approaching of building the smallest nucleus of your tech like Sam described work for Pair? So far it is working - but as you say it is a real pain point. The biggest problem we have is that venture people focus on our first product only so they are looking at traditional metrics such as MAU, Revenues, exits etc... which is reasonable if they assume that Pair the commerce platform is all we ever want to do - nothing else we are doing seems real to them. In theory, the commerce platform alone is a big product, but it's maybe 1/1000th of our whole stack we're building. but I'm not sure if I would label it hard tech personally. I think the gray area is all around the real-time constraint. Without going into a long technical explanation, our mobile monocular SLAM implementation, semantic segmentation, structure from motion and relocalization (loop closure) systems are firmly in the Machine Learning/Hard Tech sphere. Our team is ML/CV people and we're focused on building fundamental infrastructure for future computing platforms. None of that is obvious from our marketing materials - because it would just be confusing for those in our first market/vertical. As I said before, this approach is doubly hard than building just a product because you have to build it on top of all the other stuff. Trust me, if I had 10s of millions of dollars, we probably wouldn't be working on this commerce platform (even though we have had good success and it's a great tool.)
- tedmiston 10y agoYou're correct that it wasn't obvious (at least to me), and given your explanation it makes much more sense, especially from knowing more about the implementation. The video reminded me of Ikea's virtual furniture app [1]. Tech-wise the comparison is superficial, as your tech is so much harder / more sophisticated, but my first thought as a consumer was "sounds like an iteration of that". I wish I had suggestions. Computer vision research on the edge is hard x starting a startup is hard. That's tough. Maybe someone else will have more insight. [1]: https://www.wired.com/2013/08/a-new-ikea-app-lets-you-place-3d-furniture-in-your-home/ https://www.wired.com/2013/08/a-new-ikea-app-lets-you-place-...
- rawnlq 10y ago> Without going into a long technical explanation, our mobile monocular SLAM implementation, semantic segmentation, structure from motion and relocalization (loop closure) systems are firmly in the Machine Learning/Hard Tech sphere. I am sure it was hard for you guys but aren't these systems no longer technical unknowns? There are lone PhD students who managed to build them and open sourced their work. [1] This is no longer hard in the sense of "I'll need a research team and five years -- and we might not figure it out." It seems like it's just academic technology transfer where you need people who can read the latest papers and implement them. [1] http://vision.in.tum.de/research/vslam/lsdslam http://vision.in.tum.de/research/vslam/lsdslam (The author is now at oculus research)
- snovv_crash 10y agoIf you don't have to design for assembly, you aren't dealing with hardware. The fact that software essentially has zero reproduction and distribution cost is what makes it so much easier. Put it this way, when you buy a car, the difficult part for the manufacturer wasn't the customer-experienced design of the car, or even the driving concept. The hard part is designing the assembly line, and designing the car in such a way that 100,000 of them can be put together such that the assembly of each individual piece takes exactly the same amount of time, otherwise there are assembly line stalls. Then you also have to design, or at the very minimum optimally position and program, the machinery to put the pieces together, organise supply chains, deal with subpar contractors whose quality changes even if they are delivering theoretically the same product, etc. Seriously, I have done my time in the CV space, and it is a lot easier than real world hardware, even if CV is still being explored, just because of the distribution and replication of a finished product.
- cbhl 10y agoThis reminds me of the video game Factorio. Is there software that solves this problem of factory layout? Why or why not?
- tel 10y agoThere are whole fields more or less dedicated to it! In mathematics, queueing theory; in engineering pretty much the entirety of Industrial Engineering; and there are probably 10 competing frameworks in management, the most important being Lean, Theory of Constraints, Six Sigma.
- AndrewKemendo 10y agoI don't disagree that hardware itself has more dependencies. I don't think that makes it harder or less probable of delivering though than bleeding edge computer vision/machine learning systems. I too have worked hardware and on those projects we could get fairly low level line workers on assembly up to speed quickly, source our parts in a repeatable fashion and build systems to scale without too much brain power. Not easy, but more logistics management than creativity. With these non-deterministic CV systems (for example point cloud generation) the path to working is much less clear. I'm not saying one is harder than the other, but the class of unsolved problems in CV/ML doesn't have off the shelf solutions, so they pose different but similarly hard problems as hardware.