Garden City Ruby 2014

¿Qué necesita tu código, un médico o un farmaceútico?

Pavan Sudarshan, Anandha Krishnan  · 




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

PAVAN SUDARSHAN: Hi. My name is Pavan. ANANDHA KRISHNAN: And I'm Anandha Krishnan. I'm also called Jake. Not Anandha. I know. We work at MavenHive technologies. P. S. : This is probably the only talk where there are two speakers, and we haven't rehearsed who says what, so we'll be stepping on each other's toes, so yeah.

Bear with us. So yeah. Quick disclaimer: Most of what we are going to talk about is actually platform and language independent, or at least, in a sense, learned. But the reason we are talking here in a Ruby Conf is because of the Ruby community. We really think that a lot of things we are going to talk about resonates really well with the community, and we are hoping to, you know, drive a good discussion, conversation, whatever it is, from this audience.

So that's really why we are talking here on this topic. A. K. : And a lot of the points that we're going to talk about kind of naturally apply to Rails and Ruby. And most of these we learned, and we sort of experience in our projects, which are mostly in Ruby and Rails, so.

P. S. : Yeah, so let's start with condition. We have screwed up a lot in our careers. Right, between me and Jake, we have no idea how many mistakes we have made. And on those rare occassions, we have actually learned from it, or at least we would like to think so.

So yeah, this talk is about one such mistake from which we learned, and yeah. A. K. : And, yes, I think most of it, we just put it up front, just based on projects, and you know, as we were talking about what happened with each of us, and things like that.

So yeah, just trying to make it, you know, presentable and that stuff. But we- P. S. : Yeah, like, though we screwed up, we would like to believe that no employers or paranoid androids were hurt in the process of our mistakes, so yeah. OK, about three months back, so why pharamcist and doctors, right? So about three months about I was in this pharmacy buying diapers for my daughter, and in walks this guy - he just goes straight to the pharmacist and he's like, hey, can you give me something for a toothache? There was something very interesting and weird about this, and Jake and I, we carpool.

So the next morning I was just telling Jake, and between the two of us, like, between the two of us, we realized that we have seen people ask for all sorts of medicines in a pharmacy. Right. Headaches, fever, like, like, true story, I even once saw this guy with a lot of cuts on his face from a knife, and yeah.

Insane. Insane, right. So about, when we were talking about this, we thought there was something fundamentally wrong with this. Is there anyone here who thinks that it's totally OK for you to just walk up to a pharmacist and ask for a medicine? Oh yeah, cool.

Yeah, so. Nice. OK. Hold that thought. Yeah, but like. So what we think, yes, a pharmacy potentially has a cure for pretty much any, most ailments that you could think of, and but the important thing is, though, you need to know what ailment you have. Right, there's that small implementation detail, right.

And if it was that easy for you to just go to the right medicine and get it, this world would be filled with only pharmacists and not doctors, right. Yeah, so that's, so that's where the whole analogy starts, and then we'll get to how we connect to what we're going to talk about.

A. K. : Yeah, and that's, that's where we, in a sort of thought that we use this metaphor to drive home that point. Of course, a lot of you might have your opinions about self-medication and the whole thing. So we'll stop it at this, and we will give us, our definition of what we think about these two sort of mindsets actually are and, you know.

So starting off with like doctors, right. They don't treat, rarely, they don't try to treat the symptoms, it's about how you deal with them. So they go about just figuring out what the problem could be, you know, and then probably, you know, a lot of tests, make you run through a few tests or try and figure out what's what, if indeed it is the problem, and then try and, based on that, prescribe a treatment and, of course, make sure that you're OK at the end of it, right.

The symptoms are gone. P. S. : And we didn't take a look through a medical textbook, so we don't know if this is right, but assuming it is, though, this is what worked for us, so. A. K. : And, again, in contrast, a pharmacist's job, we think very different, should be more about understanding the medicines, the medicines themselves.

Probably even figure out what the disease is based on the medicine, right. But definitely they don't really think about, you know, what was the problem originally or what are we prescribing the treatment for. And they usually don't do it. Hopefully they don't do it.

P. S. : Yeah. OK. So now with this context of what we mean by a doctor and a pharmacist and medicines and self-medication, all right. Let's get back to our mistake, which we want to talk about. Right. So our mistake that we want to talk about is a way we have dealt with, or rather we used to deal with bad symptoms on our code bases and on our projects, right.

So you, a lot of times you see these in your code bases. There's the symptom, or there are some issues, right. So we obviously had a lot of those, in every single project we have worked on, and this is about how we dealt with that, right. A. K. : Let's start off with one very simple one, or at least the one which was the most easily expressible.

P. S. : Yeah, as in, Tejas Dinkar, who has already been mentioned several times in different talks, he threatened us to throw off the stage if we took anything more than twenty-nine minutes, fifty-nine seconds. So we had to like really dumbify our, you know, anecdotes.

[ ... ]

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