text
stringlengths
0
1.17k
[2335.46 --> 2342.76] them to open it up because uh you know my sort of thought is not everybody who uses buckets is going
[2342.76 --> 2350.02] to come from assembly uh and and github is clearly in the developer community a pretty well-known
[2350.02 --> 2356.36] prominent tool everybody has an account everybody has used the issues before um but i you know i see
[2356.36 --> 2363.44] both sides of the coin there but yeah in general i love the idea of as open as possible let's pause the
[2363.44 --> 2367.40] show for a minute give a shout out to a sponsor top towel if you've listened to the show over the
[2367.40 --> 2372.54] last year you've definitely heard us talk about top towel we uh we've seen firsthand the the fruits
[2372.54 --> 2377.30] and benefits of having top time the community helping marry really great opportunities for
[2377.30 --> 2384.14] developers with really great developers uh as top towel says elite engineers um i wanted to mention
[2384.14 --> 2390.04] because this is a node.js focus show um you can actually hire top node.js developers right now on top
[2390.04 --> 2395.54] towel and if you are a top node.js developer and you are not working with top towel and you'd like
[2395.54 --> 2400.70] to check out freelancing or go into some of that kind of stuff you can go to top towel.com slash node.js
[2400.70 --> 2406.50] you'll find uh really awesome node.js developers in their community already um and at the very top of
[2406.50 --> 2410.58] the screen you can see apply as a developer click that button right there it'll take you through the
[2410.58 --> 2415.82] process of actually becoming an elite engineer with top towel go to top towel.com slash node.js
[2415.82 --> 2423.08] and now back to the show we've talked a while i guess we try to establish what what size of the
[2423.08 --> 2427.82] team you do have or don't have so it seems like you're the core team right now yeah who else is
[2427.82 --> 2435.06] on the team with you i would say um so nobody i i keep myself as the core team for now like i would
[2435.06 --> 2442.02] i would absolutely adore to sort of promote somebody else to the core team but uh i think as a core team
[2442.02 --> 2450.64] you get sort of i forget i think it's like three to five percent of all um bounties is just sort of
[2450.64 --> 2456.74] reserved for you and it and that five percent i think is split among the core team uh and not like
[2456.74 --> 2461.18] i'm trying to sound greedy but you know uh if somebody's going to if we if i start splitting that
[2461.18 --> 2466.40] and we get 2.5 percent each like i just want to make sure it's somebody that's committed committed yeah
[2466.40 --> 2472.92] into it yeah yeah and uh you know so if somebody was just sort of knocking out bounties for like
[2472.92 --> 2481.28] two months straight um i i i wouldn't hesitate but anyway for now i'm i'm the core team i think if you
[2481.28 --> 2487.38] were to look at our github i think we've had about 15 or so contributors um some of them smaller than
[2487.38 --> 2495.14] others but um i would say 10 to 15 people in general have really jumped up on the the code side
[2495.14 --> 2502.18] so maybe 20 to 25 people total in terms of also design things uh etc on assembly
[2502.18 --> 2509.14] shout out to uh charles pletcher he's got uh let's see how many commits he's got 69 commits so he actually
[2509.14 --> 2516.00] he's part of assembly and uh oh there you go he jumped on early on uh he did he did some awesome
[2516.00 --> 2522.08] fantastic stuff for the templates and everything um i've been sitting over here thinking it just sounds
[2522.08 --> 2527.80] like what you're missing is a is a partner in crime like you like a second person somebody more
[2527.80 --> 2534.04] on the system back end ops side that really would just complement your talents it seems like you're
[2534.04 --> 2539.56] pretty well rounded but to help make those big decisions you know uh i was thinking a lot about
[2539.56 --> 2544.40] last year as i was like trying to do this sort of on my own was i just thought oh if i just had that
[2544.40 --> 2550.06] that technical co-founder you know that like dream thing everybody around here wants but but at the
[2550.06 --> 2558.32] same time i don't you know i've i've done businesses and and sort of apps and things uh with partners
[2558.32 --> 2563.06] that i've met and just sort of reached out to and all kinds of things and i just sort of thought
[2563.06 --> 2570.76] this is for me personally like much more of a long tail thing and if there was that person like i would want
[2570.76 --> 2576.04] a lot of trust in that person you know i i just wouldn't want it to be something i i you know
[2576.04 --> 2583.88] post an ad on weekendhacker.com and somebody's yeah that's a great idea um you know because it's just
[2583.88 --> 2589.72] that's it's great for getting off the ground but it's that like you know two years in and you guys
[2589.72 --> 2594.76] have different ideas of how it becomes a business i just didn't want to deal with any of that which is
[2594.76 --> 2600.40] a little not narcissistic but you know it's a little limiting in that i'm like putting a lot on
[2600.40 --> 2608.16] myself for now but um but like i said i'm i'm open to it i if somebody you know seems like assembly is
[2608.16 --> 2613.44] a decent vetting solution for that where you can you know they can come and put their time in get
[2613.44 --> 2619.50] get some i guess equity over time build up trust show that they've got the skills and then eventually
[2619.50 --> 2627.00] could become that person i actually did offer it to charles to uh charles pletcher uh like a few
[2627.00 --> 2632.26] months ago i said you should become part of the core team because he clearly sort of knew what was
[2632.26 --> 2636.98] going on in the architecture and and i think he had a good idea of where i was going but he was like
[2636.98 --> 2642.24] you know uh i'm gonna eventually i'm gonna have to spend some time on other assembly projects and
[2642.24 --> 2652.30] actually put in time for assembly itself um so he declined but um hopefully one day so if you're out
[2652.30 --> 2659.14] there and you're a back-end hacker as jared just uh described and and you like david and you think
[2659.14 --> 2665.92] that buckets has a good direction and you could just hop in work hardcore for two months and he'll
[2665.92 --> 2673.40] promote you to core totally right yeah i mean if i were to describe my dream situation if like i've
[2673.40 --> 2679.30] completely loved working on the node side and i love working with node um but like you said like
[2679.30 --> 2685.56] it's sort of more in that sysops realm that i i just it's not as fun for me like if i got to spend
[2685.56 --> 2692.52] you know twice as much time just kicking out the user interface and doing more custom fields you know
[2692.52 --> 2700.60] we need like relationships um types of fields we need repeater types of fields anyway so we talked a ton
[2700.60 --> 2705.60] about the the product itself but we're obviously this is the change log we like to get a little technical
[2705.60 --> 2712.58] um on this show so you mentioned node obviously mongodb i i saw earlier in in your history too you
[2712.58 --> 2719.02] moved from rethink to to mongo i think that was for windows is that still like what were some of the
[2719.02 --> 2726.10] reasons why you chose node and chose mongo and and why node so node was the easy choice because i just
[2726.10 --> 2735.22] knew i wanted to do it in node um the reasons for that are um you know partly convenience because i'm a
[2735.22 --> 2742.82] front-end guy and so javascript feels natural to me um it was partly an experiment because i just
[2742.82 --> 2750.20] wanted to try something new um i think you know and again i'm more of a front-end guy so i i don't
[2750.20 --> 2755.36] want to like say the wrong thing but like looking at sort of the spectrum of all the different
[2755.36 --> 2762.46] server-side tools and things you have now um you know i'm personally i'll just never build a java app
[2762.46 --> 2772.56] um ruby is to me just ruby seems like the uh i'm gonna get in trouble here but sort of a childish
[2772.56 --> 2786.06] equivalent of node oh yikes not yikes not quite as no no i think uh yeah um how so how so it's it's
[2786.06 --> 2795.70] just not quite as impressive in terms of its scalability right um and the the sort of
[2795.70 --> 2805.32] asynchronous evented nature of of node um actually allows for certain things like i think on the the
[2805.32 --> 2812.44] surface they seem quite similar um but at the end of the day in a lot of situations node is much much
[2812.44 --> 2822.84] faster um and for me easier to develop in because it is javascript the evented model provides for that
[2822.84 --> 2830.70] right so yeah and um which you can do in ruby but it's not the typical web frameworks are not using
[2830.70 --> 2838.90] event machine so they don't have that built right in whereas node does yeah what about the the back
[2838.90 --> 2844.94] end um i think a document-based database makes a lot of sense because your cmss are basically just
[2844.94 --> 2849.64] storing a bunch of documents is that kind of where you started and then you yeah and and that again
[2849.64 --> 2856.30] was partly an experimentation and and i still have people once a week warn me that mongodb is gonna
[2856.30 --> 2863.84] start vomiting in my face at some point but um but so far it's been great uh you know it was something
[2863.84 --> 2871.42] that again during while i was at censia i basically only worked on client-side projects for for three
[2871.42 --> 2879.80] years or so and i and i saw sort of these uh you know no sequel or document-based databases were
[2879.80 --> 2885.68] becoming really popular around then um i mean that's a bit of a miss it was obviously i was probably late
[2885.68 --> 2892.42] to the bandwagon but um but i i saw a lot of that while i was there without actually using one and i just
[2892.42 --> 2897.60] you know after you when you spend so much time with javascript and working with objects the idea
[2897.60 --> 2904.34] of using objects to query your database or to be able to inject objects into places within your
[2904.34 --> 2911.92] database is just sort of extremely appealing and that was sort of the initial uh impetus and i did i
[2911.92 --> 2919.80] started with rethink just because i had heard sort of various war stories of of mongo and uh rethink
[2919.80 --> 2925.74] seems to be sort of one of the cooler new kids on the block but you know a big reason i went with
[2925.74 --> 2933.94] mongo was just because of mongoose in the node ecosystem it's it's just i to me at least far
[2933.94 --> 2942.72] sort of further ahead than any other sort of orm odb type thing that's interesting so the the mongoose
[2942.72 --> 2947.70] library itself was the kind of the deciding factor there for you yeah definitely one of the bigger
[2947.70 --> 2956.50] uh decision makers you know just the built-in validation the uh relationship management it
[2956.50 --> 2962.46] was all just super super straightforward i guess there's some there's some symmetry there with
[2962.46 --> 2967.82] you know your desire for uh clean user interfaces and thinking about that user experience if you find
[2967.82 --> 2973.64] an api that you really love it makes sense it you know it's it's a huge factor and that's another
[2973.64 --> 2980.64] thing which i put a lot of sort of focus on within buckets and and you know it's it's i do say like
[2980.64 --> 2986.96] it's it's my project and so i i do stuff in it that um not everybody's gonna like it's how i like to
[2986.96 --> 2995.22] program certain things but in reality again this is highly contentious um buckets is like 90 percent
[2995.22 --> 3002.54] like if you look at the stats on github it's like 90 percent coffee script um like pretty much the
[3002.54 --> 3008.30] entirety of buckets whether it's the front end user interface or it's the server side uh models and