CSSConf US 2014

Reconciliando el frontend con el backend

Jonathan Martin  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

well welcome to my attraction spell so I'm just going to talk kind of briefly about the divide we have between the back end and the front ends and how we can try to bridge that with some of our current tooling so Jonathan Martin I work at the big nerd

ranch in our front end and rails development team at each our front-end course so if you happen to be in that lanta area she couldn't check us out you can also follow me on twitter at nibbler so i'm going to talk about something we deal with every

day that is people and specifically as front-end developers we deal with back-end people so that's great but very often they're a little bit too irrational for our taste because we have a very specific workflow of how we like to work so when we have

to work on a full step team kind of environment we have to pick some different strategies for how we're going to cope with our backend friends the first strategy we could pick as we could just try to survive through it and typically that means anytime

we need to do some PRS or something one developer on it keep them separated don't let them get anywhere near each other kind of like matter and antimatter reacting so that collaboration strategy of steer clear it's pretty much what most people go with

when it comes to tooling deciding what tools to pick if you're going to collaborate with rails in front end it's typically whoever got to the code base first and this is something that's very common and typically makes up the bulk of front-end

back-end teams so the solution we want is we want to be able to thrive we want to be able to take our front-end and back-end and make them thrive together like an Oreo I talked about an Oreo just because we all know that the cookie part of an Oreo is just

the presentation and the sustaining white stuff that's hidden or encapsulated inside for the consumer is the important part at least until the cookie contents are requested by the digestive tract so without a little analogy we want to treat our back-end

fellow members like that Oreo cream so too often we try too hard to mix together the front end and back end and try to get everyone on the same level try to get them all educated the same like an Oreo truffle we don't want to do that we want to keep our

separation of concerns we want to keep the people who are experts in the front end and keep the experts your experts in back end but we need to find a good way to get us interoperating so the first way we can try to do that is by trying to keep the two completely

separate have an entirely separate repo for your front end part of the appt kind of like an iPhone clients the iphone client isn't developed along with the server code it's developed in isolation so you can do the same thing just pretend that your

front end client is a client and have it consumed the back end so that's one way we can do it and this is a really great strategy to take if we have the time and resources to do it but unfortunately a lot of times we don't have either if you're

in a hackathon of some sort this especially comes up where you'd like to split off the two but you have so little time to begin with it you don't have time to split off the to make the separate repose configure all the CSRF tokens and whatnot that

come with a rails based api so unfortunately that's not always our leisure so there are some strategies we can follow in some tooling we can pick from the go to make sure that the front-end developers don't go insane working with back-end developers

and vice versa so thankfully we have some people have already put the other some really cool tools and we can rely on their smarts to get started so one strategy would be to just push through this with a front-end developer just make it work would be kind

[ ... ]

Nota: se han omitido las otras 1.779 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.