• Project Statistics from Backers

    Monday, October 7, 2013

    #####10/7/2013— [Kelsey Breseman](/blog/"tmblr-full" data-orig-height="389" data-orig-width="785" data-orig-src="https://lh5.googleusercontent.com/f0ifsWlNwcOQe1rUXkt3tgZFdYki1jlQUyWfFfyG4rR1QQHRbN-dB_Jc0UgzWu4x_QioNAKi-yMorJK4WGd4_IbZzIjT_iNoedF9WU8sbRfVxsP9JZ64T7Nl">

    (Take this graph with a grain of salt; not all of our backers responded here.)

    What does this graph say to us? Here are the main insights:

    1. “JS and Node-compatibility on a microcontroller is a childhood dream of mine.” Our backers probably come from a web development background– hence the excitement about JS and Node.

    2. “The tech seems cool and I wanted to try it out.” Backers on crowdfunding platforms, as expected, are inherently excited about new technologies. No one is surprised.

    3. “I’m excited about where I think you guys are going” is interesting because it seems almost like an investment. We’ve had a few verbal/email reactions from people who think Tessel might be the next evolution in democratizing hardware. Thanks for believing in us– we’re trying to make sure you’re right!

    4. “I don’t know hardware too well, but I want to build and this project gives me hope.” Personally, I had expected more backers to be in this category. The fact that this wasn’t a main self-categorization suggests that some of our initial audience is from people who have at least tried hardware before. Perhaps this is not so surprising; Jon, Jia, and Tim came up with the idea for Tessel after becoming frustrated with existing platforms for making internet-connected hardware– likely many of our backers are coming from a similar place.

    5. “I want to incorporate Tessel into a professional/corporate project.” This is a category we’re keeping an eye on. Tessel’s OS is designed so that the same code can be run from prototype to full-production product, and we’re excited about working with other entrepreneurs in the Internet of Things space. Some of these backers have already reached out to us to tell us their stories, and we’re really excited to work with them!

    Through the same backer survey and by email, we’ve been asking people about what projects they’d like to do with Tessel. Here’s what we know:

    (Take this graph with an even bigger grain of salt; sample size is small and categorizations are my own.)

    By far the largest portion of the backers surveyed were interested in home automation projects– ranging from energy conservation applications to automated barbecues. Additionally, you could arguably lump the (surprisingly large) percentage interested in pet-related applications into that category for a whopping 40% of the pie chart.

    This is one place where we see a bit of data skew. The Project Plans chart incorporates data from a backer survey and from emails we have received. The people with the most incentive to reach out to us directly are entrepreneurs with industry-type applications. (My categorization of “industry” rather broadly stands for any application you could make a business out of– though you could arguably add RC into that category for a combined 32.7% of the pie.) Most of the “Smart home” category comes from survey data and most of the “Industry” category comes through emails. Thus, since the Smart home and other categories have little reason to reach out to us, there are likely even more of them than are represented here.

    Oh- and in case you were wondering, that >10% “Joke” wedge is just our backers having a sense of humor… or at least, we assume they aren’t really plotting Skynet or world domination.

    What does this mean for us?

    The main reaction here is that these statistics are interesting, but they don’t mean much– at least not quantitatively. Partly, the data collection is hard to trust. Coming from a scientific background, I would throw out the results here as “not enough information”, since the sample size is so small– on the order of 300 respondents out of our over 1,000 backers, and easily self-selecting.

    We’ve also been warned that our backers on crowdfunding might not be representative of our long-term audience. This makes sense; early adopters understand the value of a project before it is fully realized, and often back on crowdfunding campaigns because they want to be a part of that project’s future. We love our early adopters precisely for this reason, but it also means that not all of our backers had specific plans in mind when they backed us. Thus, it’s hard to gauge what the long-term uses of Tessel will be based solely on backers’ responses.

    On the whole, these results are a good reality check for us; mostly, nothing too surprising has shown up in these graphs, and we’ve enjoyed hearing about specific projects from our supporters. Keep in touch!


    #statistics #Tessel #smart house #smart home #rccar #rcplane #remote control #dragon innovation #backers #crowdfunding #skynet #data #drones #diy #kelsey breseman

  • 8 Tips For Jumpstarting a Hardware Startup

    Friday, October 4, 2013

    #####10/4/2013— [Jon McKay](/blog/"http://technical.io" target="_blank">hardware more accessible to our fellow web developers, but it’s a hardware company nonetheless. We’d all worked at startups before and knew how to move fast with software, but making a hardware company just as agile was a completely new experience.

    There are eight ideas that helped us move fast, and if you come from a web background and are looking to build a hardware company like I did, hopefully they’ll help you move faster too:

    1. The Lean Startup Still Applies

    All the rules for lean startups still apply for hardware companies. Make the easiest, quickest prototype and get user feedback on it. Once you can prove you’re heading down the right path, iterate as quickly as you can. We prototyped with an Arduino for the first few weeks to get developers’ feedback on our direction. Only after ensuring we struck a chord did we start using more specialized hardware.

    2. Use Evaluation Boards to Save Money

    A great way to create hardware prototypes iteratively is to order “evaluation boards” for the chips you’re going to use. Most integrated circuit (IC) manufacturers sell pre-made circuit boards for some of their chips that include all of the support circuitry the chip needs to work, along with nice connectors for integrating the board into a more complete system. As you build up your prototype, you can just wire those eval modules together. The major draw here is that you can put off designing your own circuit board as long as possible. When small manufacturing runs and assembling your own boards cost you thousands of dollars, eval modules can really spread out your runway.

    3. Use Reference Designs to Maintain Sanity

    You’ll have a lot less trouble with weird hardware bugs if you stick to reference designs. Every (good) manufacturer will release documentation with their ICs that contains a section with a reference design. The reference design gives you an idea of all the other components (resistors, capacitors, etc.) that you’ll need to support the IC (see example for our WiFi chip below).  Stick as close to that design as possible (especially for high frequency chips) and your technology will work much more reliably.


    4. Use the Web for Validation

    Driving traffic to your hardware’s website is crucial for gaining early mindshare and validating your ideas. When we got started with Tessel, we felt like we couldn’t get an accurate picture of how our users would like the device by reading about it on a website. We felt that they wouldn’t “understand the experience”. As if there was something magical about using the device that words just can’t describe. The fact is, if you can’t get across the value of your product with words, then you’ll never be successful. Almost no one will have the opportunity to try your product before they buy it. Make a website and get it out there as soon as possible (well before you’ve finished actually making it). When our website was picked up on HackerNews (a month before we planned to launch ourselves), we got over 10,000 awesome, excited people on our mailing list that we could notify when our crowdfunding campaign began.

    5. Crowdfunding Is Not For Revenue

    Crowdfunding is completely revolutionizing the hardware world, especially hardware startups. By gauging interest and essentially eliminating the need for up-front inventory, crowdfunding has changed the way entrepreneurs start (and even run) their hardware companies. But for the time being, crowdfunding isn’t so much a means of making money on a finished product, as it is a way of getting the most important pieces of validation: how many people (and who) will click the buy button, how many won’t, and why. You’ll hear it in comments, tweets, articles, and blogs, and you’ll need to analyze the feedback to make your product better. An entire crowd of early adopters become accessible to help you grow your business in the right direction. Crowdfunding makes you data rich, not money rich – use it to grow.

    6. Test Driven Driven Development

    Test Driven Development is not just a software development process; it speeds up hardware development as well. When the start date for our crowdfunding campaign was approaching, we had a two-week turn-around time for each hardware revision. Hardware companies in China can get that turn around time down to days, but for U.S. manufacturing (at least in Boston), two weeks is fairly fast. Since it takes so long to get the boards, the key is to reduce the amount of time manufacturers are not spending making your boards. Here is Technical Machine’s process:

    1. Create a test suite. Before you have even sent out a board revision to be made, you should have a document describing each feature that needs to get tested, each test for each feature, and how to run those tests. When you begin manufacturing thousands of units, you’ll also need to create hardware test rigs.

    2. Know what you want to get out of each test. Taking the time to decide exactly what you want to measure and how you plan to measure it before powering on the device will save you time, tears, and inventory. In hardware it’s exceptionally rare that “it’ll be different next time” you power it unless you change something physical on the board. More importantly, if the product on your desk breaks, you often need to go out and build a new one from scratch, not just hit compile.

    3. Create a F*#!-Ups Document. There is something wrong with every revision. Expect it. Stop crying. It’s just going to happen. Create a document to keep track of every problem with the board, because as soon as you plug it in, you’ll find them. Run through the whole suite of tests, adding every problem to the list.

    4. Revise continuously. While one engineer is testing the revision and noting mistakes, another should be fixing those problems in the design.

    Each board revision consisted of about a week fixing the previous revision and a week waiting for the new boards to come in. During the manufacturing week, we would write all the firmware for new features and the test suites firmware.

    7. Free Samples (Shhh!)

    Most manufacturers will give you free samples of their ICs if you just ask for them. Some manufacturers even offers samples on their website and will overnight ship them for free. Take advantage of it – they will dramatically cut prototyping costs. We’ve probably used hundreds of dollars worth of WiFi module samples alone.

    8. Open Source Hardware Is Growing

    As most software developers know, the ability to use open source code dramatically increases productivity and learning. The same principle holds true for open source hardware. Great open source hardware companies like Sparkfun and Adafruit allowed us to
    adopt their designs for Tessel so that we didn’t have to come up with the billionth RFID antennae on our own. In turn, we give all of our hardware designs back to the community so that we can grow and innovate together.

    Those eight ideas helped us keep our overhead low and get our minimum viable product in front of potential customers as fast as possible. Of course, Tessel is only a circuit board with no industrial designed casing or external components so I can’t speak to the problems you’ll encounter there. As (open source) hardware startups become more and more popular, I hope that we’ll hear from more entrepreneurs who will shed some light on those topics and how we can work to make hardware as agile and iterative as software development has become.


    #Tessel #technical machine #hardware #startup #lean startup #tdd #samples #crowdfunding #internet of things #internet of everything #pervasive computing #jon mckay

  • Updates

    Tuesday, October 1, 2013

    #####9/30/2013— [Updates](/blog/"http://www.dragoninnovation.com/projects/22-tessel" target="_blank">you can now order a module that has SIM card support. Tweet this.

    The next stretch goal module will be at $160k, and will be one of the following:

    nRF24 – low power wireless communication with mesh capabilities (good for tying lots of Tessels together without WiFi)

    IMU – accelerometer, gyroscope, and algorithms to calculate position and heading (good for more advanced motion tracking

    Thermocouples – high-precision temperature measurement that works in liquids, too (good for monitoring high temperatures at a distance)

    Other – do you have a better idea? Let us know!

    We sent out a survey to our backers earlier today so they could choose– look for an update soon!


    Tessel at RealtimeConf (Portland Oct 18/19)

    Continuing the West Coast tour, Tessel is coming to RealtimeConf! The conference takes place in Portland, October 18th & 19th. Speakers include Brendan Eich, Isaac Schlueter, and Amber Case–so obviously we’re excited to be there. Come say hi and try programming on Tessel!

    Get $100 off on tickets by entering the discount code ‘TESSELATIONS’.

    Additionally, Realtimeconf just announced a scholarship ticket for women– read more about it here.


    Website Redesign

    We refreshed Tessel.io last week– we’ll continue to update the site with new information about Tessel even after our crowdfunding campaign. Particularly of note is the new Modules page, with information about each module.


    San Francisco Tour

    Jon and Kelsey visited the offices of GitHub, Firebase, Twitter, and Heroku to talk about the future of web development. Thanks to all our attendees! Slides from the talks are available here.


    Jon talking at Github. Photo credit to @reyner.

    #tessel #crowdfunding #GPRS #update

  • A Candid Conversation with Jialiya Huang

    Saturday, September 28, 2013

    8/25/2013— Kelsey Breseman

    This interview was originally published in the September 2013 issue of Frankly Speaking, the unofficial newspaper of Olin College. It has been modified to make it more accessible to the general public.

    A Candid Conversation with Jialiya Huang about the changing face of hardware development, working with co-founders, and what it feels like to get a company off the ground.

    Jialiya Huang, Olin class of 2013.5 [ed. note: the ’.5’ denotes a December graduation], founded Technical Machine with Tim Ryan (Olin ‘13.5) and Jon McKay (Olin ‘13) this summer. The company is launching Tessel, their first product, on September 5th, and is both thrilled and innervated by all the interest the Tessel has received already on Hacker News, Hackaday, and Japanese Slashdot.

    Full disclosure, I’m working for Technical Machine too– mostly on press and marketing at the moment [Kelsey Breseman]. But it was still a great opportunity to speak with Jia at length about the future of hardware development and her personal goals in starting a company.

    BRESEMAN: What is the mission of Technical Machine?

    HUANG: Technical Machine is trying to make it easy for software developers to get into hardware. It’s a different take on our last year’s SCOPE project. [SCOPE is Olin College’s senior capstone in engineering.]

    Hardware is something that I’ve always wanted to get into, but never felt like I was ready to, because it always seemed like there was a lower level that I needed to get knowledge of.

    For something like web development, I always knew that there was a tutorial, and I could make it, and boom, there’s a site. That’s it.

    As I got into hardware, it was like, here’s a simple circuit that can flip an LED on and off, on a 5-5 timer, for example. And then now, well, you can do that with transistors instead of just a 5-5 chip.

    Well, crap, now I need to know about transistors. You can just keep on going lower and lower, and I wasn’t sure where it stopped.

    That always has been a fear of mine, because I was never that into hardware. Technical Machine is trying to make that problem easier.

    BRESEMAN: What do you want from hardware?

    HUANG: I very much see everything as– that should behave like software. There should be a well-established API call for any action that I want to accomplish, or I should be able to look at how other people have done it and be able to replicate their actions.

    With the open hardware movement, it’s getting easier, but back in highschool, I never knew that was a thing. I wouldn’t even know where to start first. Even when I was taking circuits classes, learning physics, all the stuff that we did was very much textbook-like. It wasn’t me designing my own circuits. Very much so when I started computer science, it got to– oh look, here is a simple program, and then I was modifying it, I was adding to it, I could make it into whatever I wanted it to do. The steps just really weren’t there with hardware.

    Technical Machine, and the Tessel in particular, is a way of trying to expose an entire world to software developers, who otherwise wouldn’t have gotten into it.

    BRESEMAN: Is Tessel just a starting place for your users to get into hardware?

    HUANG: Right now, when software developers look at something like hardware, the first thing that I think of is, if I create something cool, how do I share it with the world? That’s one of the biggest thing that I want to do with any software library that I write, is put it up in the open, have people using it, and put my name out there.

    With hardware, it’s just like, this is cool, I can put that in my room; all my friends will know about it, but that will never get out into the world.

    Tessel is trying to make it easier for that entire process to happen. The set of knowledge that you would get from making one hardware device doesn’t really translate into making more of them. Tessel is just trying to streamline that entire process so that if you can make one, you can make ten; there’s a service that lets you make 100, or make 1,000.

    BRESEMAN: How does Tessel streamline that process?

    HUANG: Some of the things that we looked into in particular were other services: an API for hardware, essentially. You have all these capabilities that you want on your device– let’s say I want Bluetooth and accelerometer, for remote sensing or something. And that’s all I need. And I can do that on an Arduino: I can get an Arduino accelerometer shield; I can get an Arduino Bluetooth shield. But in order to migrate onto my own PCB requires me to now know hardware design. Whereas with the Tessel, what I hope to accomplish is making a service so that someone can say, here’s what I need, and then we send them back something that is exactly that.

    BRESEMAN: Did you make Tessel to start a company, or did you start a company to make Tessel?

    HUANG: A bit of both. Somewhere along, sophomore, junior year, Jon and Tim and I decided that we should be doing a company. At that point, I think it was the summer after sophomore year that I was at Amazon and Jon and Tim were at Microsoft, and we realized what cushy jobs we had.

    It scared me that I could see myself doing something like that. It scared me that I could be static, just spend the next 10-15 years of my life doing nothing in particular, and yet still getting paid. It was weird that I was doing less work than when I was at school, and yet I was making a lot more money than I ever had in my life before.

    I think that both Jon and Tim felt the same unease with that situation. We decided, the only way out of this is to get way out of this and do our own thing. And then we were trying to think of products and things we could make.

    Along the years, there’s been half-baked ideas that we keep pushing out. They’ve all been very much restricted to software only. It wasn’t until SCOPE that we had much hardware experience at all, and then we just suddenly launched ourselves into hardware, and we just found so many new issues that we could solve.

    The problem with software is that it’s so crowded is that anything that we would have experience with students is catering to the educational market, which is kind of a bad market to be in, or like, a hobbyist playful, nothing really necessary market, because we don’t really have domain expertise in anything else. However, one of the main things that we do have skill in is software, and if we can take the software paradigm and establish it in hardware, that’s one of the things that we’re trying to do now.

    BRESEMAN: What software paradigm are you bringing into hardware?

    HUANG: It starts with the community. That’s what the open hardware movement is trying to do. Right now, if I had a question on Rails programming, no matter how weird it is, a weird error message, I could just Google it, and then up on StackOverflow, there would probably be someone else asking the exact same thing. Something like that is so standardized, and so many people are using it, that there’s very little risk in putting your skill set in there and putting your time in there and making it even better.

    However in hardware, the space is kind of fragmented in that sense. If you get really good at one particular microchip and all of a sudden you’re moving to another one. Now you’re learning an entirely new chipset, you’re learning new instructions. Your knowledge isn’t that transferrable. So whatever you put into one hardware set, you’re stuck there, in a sense. That prevents people from going out and diving really deeply into these technologies, because there’s no easy fallback. If you were the only person doing a startup in the world, and your startup fails, no one else would hire you. But if you’re doing a startup and there’s ten other companies in your related space, one of them will probably snap you up for your domain expertise alone.

    BRESEMAN: It’s not like that in hardware?

    HUANG: In hardware, I’m actually not sure about this, because I’m not a real electrical engineer. It is definitely a lot harder to, one, formulate hardware questions about hardware such that it is easily searchable, so that could just be my bad, but two, even when we do run into hardware issues, the way you find- especially for the NXP chip that we’re currently using– I have an issue about how to configure SDRAM, for example. I look it up and the top replies are one guy, on a forum post. This is literally like ten years ago for software, how these things are answered: weird forums in the middle of the internet somewhere.

    BRESEMAN: How does Tessel solve that?

    HUANG: With Tessel the idea is that our layer would abstract away those kind of questions so that you wouldn’t need to ask those questions until you’re at a point where you’ve proven out your product and you have enough money to hire someone to do that.

    When you’re first going into the hardware space, the number one thing that you want to do is establish that your hardware product would be successful if you launched it. Getting that as quickly as possible reduces your risk in entering that space.

    BRESEMAN: What is your ideal market?

    HUANG: Our ideal market is changing. There are two sections of the market that we’re trying to hit with this. One is people who aren’t into hardware right now, who are primarily web developers. That’s the way we’ve pitched it on the site, and that’s the way everyone has run with it, as JavaScript right on the hardware. We’re taking a language that everyone knows and we’re giving them the ability to control very low-level things with it.

    That’s great for starting out in the hobbyist space, that’s great for building up a community, and that’s great for us figuring out what the overall market would want. And there’s also the space of enterprise-y things: it would be cool if my washing machine had an API that I could interact with, or it would be cool if my oven did, or my everyday devices. I wouldn’t have to open up my washer, figure out what chipset it’s using, and there are ways to hack around programming every single chip– if there was a way for me to easily control physical devices out there. That’s a different enterprise market that we’re trying to breach, but we have to gain legitimacy in the hobbyist market before we can go into that.

    BRESEMAN: What is most exciting to you about Technical Machine?

    HUANG: Everything is incredibly exciting because I have no idea what’s going to come the next day.

    For the longest time, we were unsure about technical development, the first few months. That was a lot of getting our heads down, making sure that what we were proposing was feasible. Of course, that has its own highs and lows. And then all of a sudden we launched on Hacker News, and suddenly we were getting so much attention that we had to respond to it, and it’s just been building up.

    There are so many decisions that we need to take care of, and that we need to think about. It’s very different from any other job I’ve had. I’ve been an intern at other places, but those are very much low-level. You get thrown a very specific task, or a chunk of a task; the parameters are very well-defined. But with Technical Machine, because we’re creating this company and creating the market as we go along. Every decision that we make is impactful.

    BRESEMAN: What are you worried about at the moment?

    HUANG: Absolutely everything. I’m worried about moving out of my house, I’m worried about finding enough things to eat. What happens when we’re no longer at Highland and I don’t have access to oatmeal 24/7? [The team worked from the offices of Highland Capital Partners this summer as part of their startup accelerator program.]

    I’m worried about living, and then I’m worried about the business, and then I’m worried about technology and how this is going to go.

    I’m freaking out every night about this. If we are successful, what are people saying about us on Twitter? What does the creator of JavaScript think about us?

    BRESEMAN: Are you still glad you’re doing this?

    HUANG: Yes. This is definitely one of the best experiences I’ve had. It’s amazing how easy it is to actually do. A lot of our– looking at where we are right now versus where we started the summer, we are so much further than I thought we would get. Opportunities just pop up, and we grab them. It sets us on a path to success, almost.

    I went to a talk by the creator of– they’re now called Ink, they were called Filepicker.io– Brett van Zuiden, and he was saying how you can just set yourself on railroad tracks. You make all these goals, and then all you have to do is hit them. And hitting goals is something you’ve been trained to do since you started school: you have a test; all you need to do is pass that test. You have a project; all you need to do is get to the next stage of the project. And along the way, people have opened themselves up to us and have said, “Hey, why don’t you do this? We’ll give you expertise in this field,” and all we have to do is take it. And we take it, and we’re like, “Oh, that was a good decision.” And then that just leads to more good decisions.

    I guess starting at Highland was the very first good decision we made, and since then I think we have been setting ourselves up for better decisions. It’s not so much of a “what the hell are we doing”, and more like, “here are the five possible choices; let us pick out the best of these five based on these metrics.”

    BRESEMAN: What do you think of starting in an accelerator versus starting on your own?

    HUANG: I have one other startup which I tried to do the summer after freshman year, with Charlie Offenbacher. It was essentially a marketplace connecting students with jobs: a less sketchy Craigslist, in a way. Parents needed babysitters; you don’t want to find a babysitter on Craigslist because that’s super sketchy. But you would trust the high schooler who babysat your friend’s baby for your own child. It was more localized, more geared towards parents.

    We were working out of Dogpatch Labs, and they gave us an office space, but it wasn’t really an accelerator program. Throughout the three months that I was there, we were iterating on product, but we just never really got anywhere. At the end of the summer we were kind of in the same place that we were at the start of the summer. We were getting a few sales, and our product had developed, but everything else wasn’t really in place. And that was for a few reasons.

    One is, the market is kind of hard. Every competitor to Craigslist fails. I don’t even know why we tried. I wouldn’t try that again. Two, I guess– Highland helped us establish a lot of legitimacy around this. I’m not sure if Dogpatch Labs had the same. Because we’re a very technical group and Highland invests in a lot of high-tech companies– so do most accelerators, actually. But working out of Dogpatch didn’t really open us up to that many more contacts than just working out of someone’s basement would have. Especially not in the case of our market, which was parents, for example, would not have heard of Dogpatch; they would not have cared. If they had more experience in nannying services, for example, that would have been a lot more useful.

    I guess it really depends on the kind of market that you’re going after, but for us, because we’re students, and we’re young, and we’re building a platform that other people have to rely on, having this sense of legitimacy and have other people think that we’re not just playing around, that this is a real project and we’re actually going to deliver, and doing it from Highland I think has opened up some doors for us.

    BRESEMAN: You said before that it felt easy to start Technical Machine. Why do you think it was easy?

    HUANG: It was me and Jon and Tim, and we have been working together since freshman year. I’m comfortable with Jon or Tim picking up tasks of mine. I’m comfortable with them taking my tasks, and I think they feel the same with me. I think there’s a lot of mutual trust between us because we’ve been working together for so long on so many different projects.

    Some of them have gone really shittily– which is one of the best parts, that things will go shittily, and if I’m at a loss as to what to do, one of them will know what to do. So that was the easy part, in terms of cofounders, and then we brought on some other Oliners. Eric ended up helping us a lot on things; so did you [ed. note: directly addressing the interviewer], on things that we lacked. Things that we didn’t have the bandwidth for. That allowed us to focus on things that we were better at, instead of having to constantly think about, we need press, we need to get all of this coverage. How do we do it?

    That was one of our main things that we were not going to do unless you had joined the team, for example. We wouldn’t have had the bandwidth to cover it. Bringing on these people, in these strategic places that you need help in, makes life so much easier.

    Hiring is like the best thing ever. I didn’t realize that before I started, but employees are awesome!

    BRESEMAN: You’re going back for another semester at Olin– are you going to leverage the Olin community while you’re there?

    HUANG: Definitely at least for testing, and I think that we should also be able to leverage the Olin community for some development tasks. There are plenty of good engineers at Olin. Plenty of them are hacking away at stuff anyway, and they’re very much a demographic that we want to hit with our market: tinkerers, hackers, whatever. And I also think that they would be good people to bring on for at least some projects– we need to ship out a ton of peripherals. We want to have a great community in place when Tessel first launches, and I think Olin is a great place to get that started.

    BRESEMAN: How does it feel to be running a company and going back to Olin at the same time?

    HUANG: Really strange. School feels very familiar; I know exactly what I’m going to be doing in school, and it’s not dangerous, and I get kind of a warm feeling because I’ve been there the last four years.

    On the business side, I’m always angsting about Technical Machine. It’s the combination of not a lot of anxiety, because we have a lot of safety in this– just because it’s Olin, it’s like coming home, really. I know that I can be safe, that I can hide, at Olin, from people that I don’t want to see on the internet, for example.

    I’m taking like 12 credits. One of them is E! Capstone, which will literally be working on this business; one of them is Chinese, because I’ll be going to China for manufacturing, and the other one is Sanjoy’s Bayesian class, which I heard was good.

    I’m not worried about the workload because I got all my hard work out of the way. Hopefully I can just cruise and have a free place- well, a very expensive place to stay while I work on the business.

    My mom told me that I had to get my degree. I told her, “Oh, look, we’re trying to raise a round, things are going well–” and she’s like, “I hope you stay in school!” No, mom, God! You don’t understand!

    BRESEMAN: Have you seriously considered dropping out?

    HUANG: I don’t really care about the degree. I think that I’ve gotten a lot of Olin these past four years, to the point where if I was the weakest link here– if everyone else would have been working working in Boston, in an office together, I would have dropped out. But since Tim also had a semester to finish and he’s not dropping out, and I think it’s important for the team to stay together in this sense, because Tim’s at Olin, I’m going to be joining him at Olin.

    BRESEMAN: If Technical Machine were to fail, do you think you would start another company?

    HUANG: I don’t know what would happen if Technical Machine failed. At one point, I get really anxious thinking about it because I’ve spent a lot of my time on this, my name is kind of tied to it. My reputation as a developer is almost tied to it because we’re working on a platform for developers.

    If it were to fail, I think I would have trouble separating myself out of the product that failed. I really wouldn’t know the next steps that I would take. Eventually, I do think that I would try to start another company. I would try to iterate some more in this space because I do think that it’s incredibly interesting, and the space is growing.

    No matter what, the knowledge that I have gained from working at Technical Machine is more than I would have gained anywhere else at this point in my life. Overall, it’s a win-win scenario for me. It doesn’t matter if it fails or if it succeeds. Obviously, it’s way better if it succeeds, but if even if it failed, I would have gained knowledge and made the connections I needed to in order to set myself up for success in the future.

    #technical machine #olin #kelsey breseman #jia huang #tessel #startup #interview #crowdfunding #company culture

  • Mid-Campaign Updates

    Monday, September 23, 2013

    9/23/2013— Updates

    Tessel goes on tour!

    Technical Machine’s Jon and Kelsey are coming to San Francisco this week! Catch us at our public tech talk (food & drink included) and play with a Tessel:

    Tues, 9/24 6:30pm, San Francisco (SOMA)– get free tickets (required)

    RSVP | Tweet about it

    Crowdfunding success and stretch goals

    Our crowdfunding has been a great success so far– check it out! We were the first project ever backed on Dragon Innovation, reaching our goal in under 3 hours. We’re now over 225% backed, but the more funded the project is, the more modules we can afford to build:

    At 100k funding, we added an ambient sensor to the Class A modules. The ambient sensor sends/receives sound, visible light, and IR light. Ever wanted to make a television turn on with a clap? You can with the ambient sensor.

    We surveyed our backers to see what to offer next, and they picked a GPRS/SIM module– so if we hit 130k, we’ll add it, too. A GPRS module will add 2G connectivity, which means Tessel can connect to the internet without wifi. The SIM part will allow Tessel to interact with the telecom network, e.g. sending/receiving text messages.

    What’s more, every additional 30k we raise, we can add another module picked by our backers.

    Help us reach our stretch goals by adding your influence!

    Demo videos and documentation

    We believe in open source.

    Our hardware documentation is now live at https://github.com/technicalmachine/tessel-design-docs. Check it out, share it around, and please let us know what we can clarify! (Tweet this)

    We’ll add more hardware and software documentation as soon as we can.

    Cypress and Jia show how they use Tessel.

    Our friend Cypress and Co-Founder Jia show a couple of simple uses for Tessel.

    Cypress uses Tessel to make a wireless switch for his on-call mother, a midwife, to tell clients when she has to leave the office suddenly. View.

    Jia uses Tessel to help her wake up and get to work. View.

    A little more Q & A

    We’ve had some good questions from our backers:

    How about a video module?

    We would love to make a video module. We played around with the idea before launching the campaign, but didn’t feel comfortable enough with it to release it as a module … yet. We’re open to suggestions for what camera specifications you would enjoy.

    What are the current usages while Tessel is idle, sleeping, and transmitting?

    The peak current while transmitting is ~600mA. Normal usage draws 300mA, and turning off select components (e.g. WiFi, external SDRAM) and putting the main chip to sleep can bring it down as low as 15mA. Tessel has various sleep modes, which we will expose through our JavaScript API. Note that we expect the usage to drop once we begin implementing smart software power control.

    Does the success of crowdfunding speed up shipping dates?

    The best answer we can give is … maybe. We want to ship to you as soon as we can, and the more we raise, the faster we can move. For example, buying parts overseas is cheaper, but also takes weeks longer than buying from a more expensive local supplier. Every bit we raise goes towards Tessel development.

    Will the price change after the crowdfunding campaign?

    Again, the best answer we can give is “maybe”. We want to price Tessel as low as possible, while still sustaining a development budget. The main factor is volume, so it will really depend on our order size. Since we’re still below 1k in order quantity, we’re not yet getting the best possible price.

    Keep asking questions!

    We love hearing from you– reach out to us on Twitter, Facebook, and email.

    Our announcements get to the blog eventually, but we typically email our subscribers first– sign up here to get Technical Machine news.

    Want Technical Machine to give a tech talk at your organization? If you’re in Boston or Seattle, we can probably oblige– shoot us an email!

    That’s all until next time. Keep in touch!


    Kelsey, Jia, Jon, Eric, and Tim

    #update #updates #crowdfunding #tessel #technical machine #javascript on hardware #tour #san francisco #sf #software #hardware #stretch goals

August 2018

January 2018

July 2017

February 2017

November 2016

October 2016

September 2016

August 2016

July 2016

June 2016

April 2016

March 2016

February 2016

November 2015

September 2015

August 2015

July 2015

June 2015

May 2015

March 2015

February 2015

January 2015

December 2014

November 2014

October 2014

September 2014

August 2014

July 2014

June 2014

May 2014

April 2014

March 2014

February 2014

January 2014

December 2013

November 2013

October 2013

September 2013

August 2013

July 2013