text stringlengths 0 1.17k |
|---|
[2620.18 --> 2626.28] hundred people that are actually actively watching the the issues um at this point pretty much everybody |
[2626.28 --> 2631.08] who's using it in any kind of serious capacity if you have a production dependency on it you're |
[2631.08 --> 2641.24] watching what's going on and we we have uh we've basically um went all in on on github as our |
[2641.24 --> 2645.94] everything you know it's our project management solution our team communication solution it's basically |
[2645.94 --> 2652.46] we put everything there there there is no other like ticketing system for for happy like in privately |
[2652.46 --> 2658.16] in walmart or anywhere else um we basically made a decision that it's an open source project and we're |
[2658.16 --> 2663.78] going to run it completely as an open source project even though um you know we like i get bug reports |
[2663.78 --> 2668.14] from you know internal teams and i always say like go open an issue and they're like really like this |
[2668.14 --> 2672.38] issue you want me to like put it on the web i was like yeah go open an issue it's like i'm not |
[2672.38 --> 2676.50] embarrassed by it it's like it's a bug and we'll fix it you'll go open an issue i mean people will see |
[2676.50 --> 2683.92] the the the the commit so it's not like you know you can hide it sneak it by him yeah um but we've |
[2683.92 --> 2689.32] also made extensive use of milestones even before uh github kind of cleaned their act with versions |
[2689.32 --> 2694.80] um so we've been using milestone quite extensively so we don't do release notes because all we're doing |
[2694.80 --> 2701.94] we're like we're very religiously tagging everything to uh to an issue and then the issues are all part of |
[2701.94 --> 2706.30] of milestones so you can see exactly if you just look up you want to say okay what changed between |
[2706.30 --> 2711.16] this and this you can just bring up the milestones and you can see exactly what issues were associated |
[2711.16 --> 2716.46] and then once we did that we kind of added the uh the breaking change uh uh label and we said hey |
[2716.46 --> 2721.42] you know what if we're gonna make a change that's gonna be breaking um and we and before we were 1.0 |
[2721.42 --> 2726.68] you know basically every minor release was a was a breaking change like every one of them was like |
[2726.68 --> 2733.60] oh yeah you can't upgrade unless you like rewrote your entire app um and and after that it became |
[2733.60 --> 2739.70] a lot more less sorry a lot less significant i think we made like two breaking changes throughout |
[2739.70 --> 2746.64] 1.0 and both were for security reasons so like we changed the default of uh like multi-part uh parser |
[2746.64 --> 2752.48] not to create files by default um stuff like that that we felt like you know this is a a breaking change |
[2752.48 --> 2757.40] worth making um yeah the note the whole node community had to kind of to do that pretty much |
[2757.40 --> 2766.20] right if i remember correctly yeah so um we we we had a couple of breaking changes in 1.0 that were just |
[2766.20 --> 2773.24] that important um but overall uh it hasn't been a big deal and now we're working on 2.0 and um |
[2773.24 --> 2780.54] we're kind of like we have the one issue that we collect everything and it's more of like edited and |
[2780.54 --> 2786.02] it's it's a lot more friendly for you to understand but then every individual issue that is actually the |
[2786.02 --> 2792.04] one where the change is being made we also tag that so um because i'm not expecting everybody to be able |
[2792.04 --> 2798.02] to sit there and go through my you know 300 breaking changes issues in 2.0 and like read every one of |
[2798.02 --> 2804.26] those i mean that would be awful so instead like we're you know we're basically doing it that way and |
[2804.26 --> 2809.18] it's also great because then once we're done writing a migration guide it's just kind of like doing |
[2809.18 --> 2814.04] some editorial on that particular issue yeah uh and then and that and that's how we do it too like |
[2814.04 --> 2818.18] we're going to go in and edit that and that will be the migration guide like we're not going to |
[2818.18 --> 2824.48] actually like publish a like a wiki page of doing that so do you know anyone like that's using happy |
[2824.48 --> 2832.14] in production besides you guys at a at a at a large scale i don't know about large scale um i know that |
[2832.14 --> 2839.86] uh mozilla was using it for some of their identity stuff um for some of their the browser id uh they're |
[2839.86 --> 2844.50] using happy i don't know what's the status right now but they they uh were using it as of a few |
[2844.50 --> 2853.02] months ago um i know uh mastercard um is using it for some of their new project uh con and asked the the |
[2853.02 --> 2860.16] publisher uh they're using it as a as a building block for their new uh um uh cross-platform environment |
[2860.16 --> 2867.04] uh so and of course walmart is using it uh um uh quite heavily right now for mobile and we're |
[2867.04 --> 2872.88] looking this year to expand beyond mobile to a lot of other uh areas of the of the e-commerce business |
[2872.88 --> 2882.30] so yeah so it has some uh significant adoption um but then others you know um have have made a decision |
[2882.30 --> 2889.98] to uh uh either build their own or use express so uh i i think i the the default behavior |
[2889.98 --> 2894.46] for other people right now is um is to pick express because everybody else is using express |
[2894.46 --> 2902.72] and then um they they tend to once they got into express they they feel like it's too much right now |
[2902.72 --> 2907.22] to make changes so they just keep building more and more layers on top yeah to make it more manageable |
[2907.22 --> 2914.60] for them um so i'm hoping that you know as this time passes and more people are seeing what we're |
[2914.60 --> 2921.98] doing with it um you know they can uh they can make a a different decision and for example like if |
[2921.98 --> 2926.56] you you know if you if you have an existing api and you want to take the uh the proxy strategy |
[2926.56 --> 2932.18] to migrate to a new stack which is a it's a really great uh um approach in terms of you know sticking |
[2932.18 --> 2937.48] your your layer in between and slowly making changes you don't have to go in yeah otherwise you |
[2937.48 --> 2942.10] have to sit you know sit in in in dark room for a year and you know and rebuild everything and of |
[2942.10 --> 2945.98] course we know how well that works in production like when you ship the new version and nothing |
[2945.98 --> 2950.58] works right and then you know it's a year behind and probably get canceled and everybody quits right |
[2950.58 --> 2958.46] so yeah and and and basically you can you can uh deploy happy with probably about 30 lines of your |
[2958.46 --> 2964.46] own code and get all the proxy functionality immediately at walmart you know walmart scale |
[2964.46 --> 2969.16] yeah so that that's kind of neat yeah i was gonna ask i mean that that's kind of my next |
[2969.16 --> 2973.78] question was what you know what's the future of walmart look like for this kind of stuff so how |
[2973.78 --> 2979.84] much kind of so you're on the mobile team how much um you know i don't know what the best way to ask is |
[2979.84 --> 2985.70] but how much impact have you had on the other teams in walmart so it was kind of interesting because uh |
[2985.70 --> 2992.34] there was about a year ago there was some effort within the uh the people in the company who like to set |
[2992.34 --> 2997.08] standards and they came to me and they said we you know more people are asking us about notes so |
[2997.08 --> 3001.80] can we make it the formal that like happy is the official framework at walmart and i said no |
[3001.80 --> 3006.28] like i don't want that to be the case i don't want anybody to use happy because some policy is |
[3006.28 --> 3011.46] dictating it um because i wouldn't use it because you're telling me what to use so so i don't want |
[3011.46 --> 3017.60] to do it to other people um so we never like actually like promoted within the company and people |
[3017.60 --> 3021.74] just picked it up all on their own it's kind of neat all of a sudden like we're getting uh issues open |
[3021.74 --> 3026.02] and then like after like a few back and forth they're like oh wait a minute are you from the |
[3026.02 --> 3032.04] santa clara office um so it's kind of like this this funny where like we were meeting other people |
[3032.04 --> 3038.30] on like the irc channel like you know co-workers that we have never met before um so some of the other |
[3038.30 --> 3044.42] um other teams were building like smaller uh like like panels for the main website like |
[3044.42 --> 3050.08] recommendations and like the social stuff uh they're using happy to build their own stuff um and |
[3050.08 --> 3054.54] they have like their own deployment their own servers um and they're like they you know every |
[3054.54 --> 3060.68] month they'll come back um but the the real goal um for for my team this year is going to be to kind |
[3060.68 --> 3067.78] of like look and see where we can add value um beyond mobile um as we're uh as walmart you know |
[3067.78 --> 3074.32] uh walmart uh e-commerce uh as a whole is is moving to uh new apis and new technologies on the back end |
[3074.32 --> 3082.94] um we're all going to have to move to that stack uh and then also we're expanding our our mandate um |
[3082.94 --> 3089.12] to other countries so right now the mobile team is uh focused primarily on the u.s uh where we have |
[3089.12 --> 3097.76] walmart and sam's club and we also are um uh working on the mobile apps for asda which is the walmart brand |
[3097.76 --> 3103.90] in the uk um and walmart is active in a lot more other countries including you know mexico and canada |
[3103.90 --> 3111.64] and china and brazil and it's a very long list uh so we are um at some point going to expand um |
[3111.64 --> 3117.70] to those so it's really seeing how how much we can scale the node um uh engineering process |
[3117.70 --> 3124.54] uh beyond just you know scaling the the software but also scaling the the the engineering itself |
[3124.54 --> 3130.76] like the the writing of the software itself we're gonna pause the show for just a minute and give a |
[3130.76 --> 3135.10] shout out to our awesome sponsor top towel they've been sponsoring the show for a little bit and we've |
[3135.10 --> 3138.34] had a chance to tell you about some really awesome stuff they're doing i've been working with |
[3138.34 --> 3143.70] brendan their co-founder and cto and i mentioned that you know i wasn't quite sure what to expect |
[3143.70 --> 3147.90] from them and i was but i was excited about what they're doing they're helping developers |
[3147.90 --> 3151.96] who want to freelance with some really awesome companies find ways to do that |
[3151.96 --> 3156.34] and it's their mission these guys are the real deal they're engineers themselves from top to bottom |
[3156.34 --> 3160.92] they're not technical recruiters trying to pimp developers so if that's what you think then you've |
[3160.92 --> 3166.12] got you've got them completely pegged wrong they're a network of elite engineers all around the world who |
[3166.12 --> 3171.04] work with some really awesome clients and for those of you out there who are freelancing or or would |
[3171.04 --> 3175.18] like to freelance you've got to check out top top you can work on special projects with companies |
[3175.18 --> 3181.32] like airbnb artsy audio and many others you can work remotely you can go to andrew's favorite place |
[3181.32 --> 3187.32] which is on a beach or anywhere in the world it's there there no office is required and to get |
[3187.32 --> 3192.42] started head to top.com slash developer click join the best and because they want to work with only |
[3192.42 --> 3197.28] the best senior engineers out there they've got a well thought out four-stage screening process that |
[3197.28 --> 3202.42] begins with a personal phone call via skype to kind of get to know who you are and introduce you to |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.