 These people in the community, they're dedicated to Node, you know, they're dedicated in their free time to Node and, you know, they're dedicated enough to take a day off from work and go and do this other consulting thing if it's going to help people do better with Node. What sort of clients would you expect to have? I mean, are you thinking large enterprises or startups? So I can tell you like the kind of approaches we had so far. We already have like five to ten emails of companies that are really serious about getting our our services and they're dramatically different to be surprising. For instance, we had talks with people that are trying to pour the Facebook application that they run on PHP because they think that the streaming model is going to really help them deliver more music in real time or we have a large blogging network from Chile that might be interested in talking to us and actually migrate their things to Node and they want to know that they can do it right, that it actually works so they can get our expertise to actually know so does this work and how do we do it? How do we pull it off? So we think that enterprise will be more interested in this so maybe telcos or energy but we're at this point not sure but those are the kind of companies that are right now reaching out to us. Companies that want to migrate to Node and they recognize that there is this gap and they're like okay you're leveraging the gap that I was really afraid of please come here and help me do this. Your team can help us. We've had a few people already make a comment like this is exactly what we need actually and I think we are going to stretch the scale between startups and enterprise I think. I think we're going to get a few big customers that really want us to go in and do a training for like 30 people so that they can all learn Node and then we're also going to get a lot of startups that really need architecture help or early code reviews that they're not doing things that just aren't kind of best practices but I think that the key difference here between our services and what you might hire a traditional consulting services for and what we wouldn't fit into that is you need to have a development team of your own you know like we're providing services that invest in your team you know we're not providing the team for you we're not writing the code for you so you know a lot of traditional consulting services go to people who have a great idea for a product or they end up having a great design or they might have great content but they don't have any developers and so they hire a consulting firm to do that and that's not what we're going to do at all. Do you know of any precedent for for this type of firm like within any other language I mean it seems like a pretty novel idea? Not a lot of other languages but I think some of the services that we provide are a fraction of what other consulting services have done in the past particular smaller consulting companies that tend to be involved in really early technologies you know like like Boas Center is a very good friend of mine at Boku who runs like a very successful consulting firm and they're doing everything from WebGL HTML5 games to you know like phenomenal new stuff with Backbone and they were one of the first people to sort of do stuff with Node and with Couch and they really like to invest in really new technologies and take really exciting contracts and they take longer-term contracts that's their business but every once in a while they will do a training or you know they will just go in and do one day of onsite something for somebody because you know they get that opportunity but they can't really specialize in it or only do it because you know they want to employ those people full time and they want to take on that other work and it's it's a lot of work to negotiate with companies who want to pay you to come in for a day right and having a lot of overhead in that negotiation in that billing process to do it you know hundreds of times a month possibly is just not what what they want to do you know like but Boas definitely does not want to spend all this time doing you know accounting work so a thing like you're right that this is a novelty but it's in a novelty in the sense that the community is running this it is not necessarily a novelty in enterprise if you look at enterprises that sell very well to enterprise markets but because they are in such tip top of the enterprise there's not a lot of developers that know how to do that kind of technology well those kind of companies software companies normally provide professional services that look a lot like these to get people ramped up so that exists a lot in the industry it's just that normally there's like a big company that actually owns the technology that does these kind of things in here you have kind of the inverted ways like the community the actual experts are scattered across different companies and the companies just agree that it's in everyone's benefit to actually go and still help the customer succeed even though it's a technology that is still emerging you mentioned one of the things that you i would be able to help people out whether avoiding common pitfalls what are some of the some of the pitfalls or scenarios that that you've you've seen a lot i mean certain things that you think would be really obvious by using the api a lot really simple things you know like when i create a new api that takes a callback it needs to have the standard callback parameter you know one error and one success result callback and a lot of people you know they won't they still won't use those in their own code like they'll use them constantly when they're using libraries but then when they write their own code in their own api they'll just they'll never give it an argument or they'll they'll pass it know when there's an error and that's a really really bad pattern to try and do you can't mix and you can't mix and match that very well with the core api you end up swallowing errors when you don't mean to um and you know most importantly you're not able to use a lot of the value that's being created on top of node um in the user community because you're not following the same patterns a lot of other patterns you see is that people end up rewriting things because they just didn't know about a library that's out there you know a lot of i think a lot of our early advisory stuff is going to be telling people about denode or you know telling people about socket i o and and how you can integrate that with redis and do your distributed real-time stuff a lot of people just aren't comfortable enough knowing that these things exist and end up trying to go and rewrite them when there's a really good one that's really battle tested and being used across a bunch of companies in production that they just don't know about because it's it hasn't been big enough for their people to see it yet okay do you have anything uh yeah there's there's also companies that want to be more involved in the community because they feel like it's safer for them if they're heavily involved in the community and understand what's going on and i think like this kind of skill will complement what they have they feel like they can do it but they feel like it would be good if they had an entry point to the community where they feel really safe for instance if they're doing a private npm store if they can talk to isaac well isaac can actually listen to them and help them not only set that up but he can only maybe reason about something that is missing on npm that would allow people to have more private registries so they can get that engagement point that they need in the community because these are open source modules so they can hook up to open source modules that they couldn't ever do because they were just open source and some handle on the internet now they can meet this person and talk with them so that's also something that people are at least they told me that it looks very interesting about the node firm yeah and we we also hope that eventually a lot of this uh the feedback that we get by doing by you know having these new relationships with new startups and enterprises we want to feed that information back into the community you know like i run a bunch of meetups and we're going to keep doing even more you know i run a conference for node like knowing what problems people are running into the most is going to be the best content to have at events like you know meetups and conferences and stuff like that so that we can start to spread this knowledge more i mean like one of the goals of the firm is that eventually any company that we work with won't have to use our services you know and hopefully in the future like you won't even need services like this because everybody the community will be so grown and involved that you can hire really good people and that everybody's connected okay so node's been around for it seems like three years now about and uh this is the you know the afternoon of the second day of this event so there's a you know certain things that were you've probably heard a lot over and over again by now so i'm kind of wondering what are you guys uh what common misperceptions are you guys tired of hearing about what uh what errors are there in the in the community that you would like to maybe set people straight wow so much uh i think like one one of the biggest things that i've heard over and over again uh is the event model it's all about the event model and and like i really think that most of people that are talking about that are thinking about the event model from a different language um because like yet we have these uh asynchronous i o patterns in node but when you're in node when you sort of internalize the node way of doing things the way that you think about the problem is actually like all i o is in callbacks you know and all events are actually you know when you call admit that's like a blocking in memory operation and all the listeners have to do something right now and then you're going to move on and do something else and so events in node actually are this thing that's not entirely asynchronous like yes when i add a listener to it it's going to happen sometime in the future but calling that event is actually not deferred until later and doesn't enter into the event loop um oh man i'm trying to now i'm trying to think about a lot of other things that i have problems with and i should probably not get into too many of them yeah i mean like i i think what i'm excited about is that people start focusing start focusing on problems that node can solve really well network problems that have like high traffic and that can really help companies like do businesses that they can't i've already heard stories about companies that are trying they have huge java stacks and they just can't deliver as much information as they can't as they need to because of the impedance of all these huge frameworks and node is just such a lean way of getting your network programs to deliver so much information i'm super excited about that so sometimes i don't get a lot very excited when people go like and are doing something that for instance is very superior intensive or is just very huge case that you should just use a patches to serve static files because it's already there it's very solid or engine x so that's yeah i think that the only other thing that i would bring up is that uh because the focus of the conference is on you know getting a lot of people in the business world in the venture capital world uh comfortable with node and understanding node knowing about node all the focus is on core and sort of like what node offers in core and as a technology and and how that changes things but you know there's an order of magnitude more value being created right now on top of node in in the develop in the module community um in things you know like we have the best package manager that i've ever used across any language or platform before um and you know people haven't really mentioned it that much you know this is like one of the one of the reasons why i've heard people come to node is because this package manager is so nice and and npm is just amazing um and npm has enabled us to build all these other great new modules you know like socket i o like express um like d node you know they solve all these amazing problems and and we haven't spent a lot of time talking about that to some extent well we have to take a break now but uh thanks a lot for your time guys thank you