Presentación
HTML (pincha para descargar)
Vídeo
Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
funny story I'm I've been super nervous all day and a friend of mine gave me the advice that I should come up on stage and beatbox for a minute and that would make me less nervous I'm not gonna do that but I found that telling Santa story to make
someone laugh makes them a lot less nervous and I think I think that happens to be true so just a forewarning just before warning there are a lot of opinions in this slide deck and if you'd like to talk to me about those opinions I will be hopefully in
a light-up dress at the party like broadcasting myself as much as possible so feel free to approach me and talk to me about these things because they are important so JavaScript especially the programming in general that I'm finding JavaScript is falling
more and more into a fanaticism problem we invest in one framework one tool one way of one way of coding and we we use it for everything in anything and it's we're actually starting to see alternatives to our way of doing things as adversaries whether
rather than alternatives whether rather than ways to benefit our lives and our code I definitely see a lot of the when you have a hammer everything is a nail problem we use our favorite tools even when they might not necessarily fit well or maybe something
would be a little bit better or a little bit easier to use not just for ourselves but when we're working on teams we tend to pick our favorite tools maybe at the expense of those were working with and I truly believe fanaticism prevents us from building
the best software we can possibly build we're limiting ourselves to singular frameworks singular tools and we're missing out on all the possibilities that are there I'm not saying we should learn everything I'm saying we should keep our lines
open it's not just that we miss new tools to hold on to what we what we already know the new and shiny effect is something I see very pervasively in j/s I saw this a lot with grunt when gulp came out a lot of people immediately jump to gulp and just started
just thrashing grunt and it was just it was it was quite confusing to me to see two perfectly valid tools but because one was newer it must have been better I didn't quite see it so if you need an example of this kind of fanaticism there's nothing
like waking up the morning of your talk to a blog post saying that the premise of your talk is bunk I was absolutely dumbfounded this morning when I saw a blog post about it and I I definitely liked Isaac's response to this and I hate to read off my slides
but I'm going to read this there's this myth that a single rule or the rejection of one will make software developments simple or easy and that's full and I I happen to really agree with that so today I'm really here to talk about modular I
could text here but keep what I've already said in mind keep keep the problems of fanaticism in mind when I talk about this because it will come up from time to time so one of the things that I find for modular architecture is I get this question a lot
I've spoken about flight which is a front-end framework from Twitter and I get this question all the time when I speak about that framework and I find it's a valid question but asking how is flight like ember how is flight like angular how is flight
like polymer which follower isn't even really you know comparing it doesn't--it's it should not be the basis for selecting a framework or a tool we shouldn't be asking ourselves how are things like each other in the JavaScript ecosystem we
should be asking how will this tool this framework this piece of code make my life better as a developer make my team's life better make my process better these are the kinds of questions I find we're not asking nearly as much but we could be and we
should be and before I say before I get the argument of oh well that means we just shouldn't become attached to anything that's that's entirely not true we should definitely be passionate about the tools we use blog posts documentation pull requests
[ ... ]
Nota: se han omitido las otras 2.000 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.