GitHub Git Merge 2016, 16 Nov 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: The Coding Chef: Optimizing Tools & Workflows, Juan Pablo Buritica - Git Merge 2016

Description

Public recipes are the original open source, and for hundreds of years cooks have not only shared their source but also built incredible schools in their kitchens. Cooks of all levels face the constant pressure of staying relevant, and just like the best engineers, they do this by doggedly practicing the basics while experimenting on the bleeding edge. In this talk, we’ll learn to stay relevant by looking at the surprising parallels between modern kitchens and effective engineering teams.

Juan Pablo Buritica is the VP of Engineering at ride.com where he leads a distributed team throughout the US and Latin America that is working to reinvent how people commute to work and take 1 million cars of the road. Juan Pablo has built effective software engineering organizations by emphasizing Open Source software values, technical excellence, trust and empathy. He has organized five software engineering conferences, spoken at multiple events, and led the growth of Colombia’s JavaScript community, the largest Spanish-speaking JS community in the world with more than 3,000 members.

About Git Merge:
Git Merge is the pre-eminent Git-focused conference: a full-day offering technical content, user case studies and training workshops for Git users of all levels.

Visit: http://git-merge.com/

A

All right, so um we've talked today a lot about a particularly one tool which is good right um and and I've been a programmer for about eight years. I think professional programming I've been getting paid to write code for about eight years, but about six years six years ago, when I was when I had just moved to New, York and I was running a small team in a start-up. A lot of people constantly say how have you learned so much about programming if you've only been doing this for so little at the time?

A

I didn't understand why? But today, I I've kind of understood that the training that I had before becoming a programmer was more useful for me to to to to get better at learning than anything else. So before I was a programmer. I was a chef at a restaurant in Fort, Lauderdale, Florida and I worked in hotels and I. I worked in a few restaurants in Australia and I. I was always on my computer as well.

A

So the idea behind closing the day with with the talk- that's not specifically about get, but it talks about how we can learn to optimize our tools or flick or work clothes and become better engineers was was very interesting. So I'd like to thank the organizers for having me to close the session um to me, professional software development means tight deadlines.

A

Neverending backlogs continues: delivery, complex, Team, Dynamics, demanding technical skills for eleven dollars an hour, not really that's what professional cooking means.

A

The reality is that they're, both a mix of art and science right you, you have to sometimes use math. Sometimes no, sometimes you hit limits of physics with how fast your internet can be.

A

You need to learn about heat, sometimes with your computers that there's there's a lot of science behind what we do in both the kitchen and our engineering. So what can we learn from a 300 year old profession? As we start, this new sort of a era I think software engineering, as a term has been. I think it was coined like 50 years ago of them are wrong. So say it's a 50 45 year old profession.

A

The idea behind this talk is: can we learn to remain relevant professionals? Can we learn to improve ourselves, improve our product work better with others in add values to our organizations, learning from how other people have done it before us and not necessarily in the same area? But there's there's some really good analogies. um How many times have we heard this question?

A

Many right? This is something I would hear. Every five minutes in the kitchen right service starts: 5pm customers walking, okay, when's my meat going to be ready. When's, my chicken gotta be ready in software. We don't really know, but this is not a question that I can say in the kitchen, I can't say: maybe three months not really software we've come up with random scales story points, t-shirt sizes we might as well be using chicken breeds I think this would take a silky to complete. This is a silky. Chicken means nothing right.

A

We haven't built enough software to know how long software takes to build, and it's as individuals as an industry as humans. Right.

A

When will the chicken be ready, I've cooked enough chicken to know how long it takes right, but I have never cooked the chicken with a flamethrower I've? Never yet! So, if you ask me, how long is it going to take for you to cook the chicken with a flamethrower I'm not going to know.

A

So when, when will it be ready, I think I'd like to invite you to write more software. So, as you get better at writing it and more familiar with doing the same tasks. You'll become better at estimating, because I believe that, in like working in kitchens I believe that estimating is something achievable eventually and we can probably steal a little bit on how kitchens became so organized that doing it really really really well.

A

So we must build more software, so we can reduce uncertainty and there was. There was an interesting question and the talk before which was like how you what data do you have on like beyond anecdotal or excel experience on the velocity? There's only one talk that I've ever seen. That is, that has a very scientific approach towards how software is built and it's by Greg Wilson. It's called what we really know about software and why he wrote a book which is called making software and it's what really works and why we believe it.

A

It's the only very scientific approach about building software that I've ever seen in we pride ourselves for being engineers, but we don't really measure how long, how much we're optimizing our velocity. How much time are we spending in support? How much time are we spending in features in maintenance? We have to become more scientific, even cooks know more about their trade than we do.

A

We have to document it practice. It teach it share. This has been done in kitchens for a while.

A

So, first of all, we have to start with the basics, the essential gear right. On one end, we have a knife, chef's knife, the classic, the basic tool and our editor right. We can't write code without an editor.

A

We have an editor or type consider the knife. We have a the command-line interface or, in some cases, other interfaces we have source control today. We're talking about get right get to me is like seasoning. It's always in the background. It has to be done right. You can always tell when source control doesn't work. You can always feel it, but it's used why? It's always there. It's supposed not to be in your way it's supposed to enhance your work, dependency management and build and test the year.

A

These are the things that we use as engineers every day. We need to get better app. We do sharpen our tools. Have you ever noticed the difference between a sharp knife and a dull knife? Do you know that it's better to get to cut yourself with a sharp knife?

A

Then wait a dull knife, because it hurts less I've learned that so I'd like to invite you to configure and tweet your editor, one of the first things that you're doing either culinary school or coming into a kitchen as an intern, is that you spend a lot of time learning how to cut things. You learn how to turn a potato turn a carrot. You get pounds and pounds of onions and you have to peel them and prepare them. We don't do that as engineers right. We don't start writing three months.

A

Just write code go write code just learn to we don't do that. Learn your shortcuts be more effective, be more efficient, be faster, maintain your dot files. We saw that 20 tricks talk right. He would be a great chef.

A

We've seen this this fight right, it happens in kitchens to the classic. The vein versus Emacs is the santoku, which is the second one to the chef's knife, which is the last one. It's always, though, the santoku is better know. The chef's name is better, doesn't matter it's my personal opinion. I use it better. I've learned how to use both so get really good at using one then force yourself to learn a new one and get good at it aim to become a well-rounded program practice your basic skills.

A

This was me writing JavaScript eight years ago, probably today too, because I'm now a manager. This was me probably four years ago, I've written four years of JavaScript was really good at it practice your skills. How long did it take this person to learn to do this learn different ways of doing the same? This is a mandolin I. Can slice with Amanda Lee nutcase sliced with the knife? I can slice with many things all roads lead to the same destination, but I can I can learn better experiment right?

A

Has anyone ever seen this before this is I've got his name? I wrote it down before, so this is a chef from Blue Hill dan barber. This egg is red because he fed chickens, red peppers and the only meal, so the yolk is actually read and it's fantastic and it's an experiment. It was wonderful and if you go to Blue Hill, sometimes you'll get the red yolk egg learn from others. The original open source, a recipe grandma's recipe. Take this. Do this this its forked, it submerged its shared its path. Sometimes it's closed source.

A

We don't share right. Sometimes it isn't where we didn't invent this right. Engineers didn't invent this sort of stuff. Open sources comes from the kitchen reinvent the wheel.

A

Sourdough bread is one of the basic things we find everywhere, but taking the grain of wheat and turning it into bread is one of the most fantastic things that we can ever learn. It's a basic thing. You can buy bread everywhere, but through learning how to do it, you learn a lot of things. You learn how to why fermentation works. Why the air inside the bread is really important? Why how you taste things? Why that air?

A

That's trapped in bubbles is what gives you like white bread, fantastic and it's not crackers, because all the gas that is released to the back of your nose gives it a lot of flavor learn those things reinvent the wheel when you're going to build stuff use, others right, don't write your own crypto. We've all learned that, but learn how to write now. There's the service is when you're actually sitting people down right.

A

You have different faces justice in engineering there's different faces on on on on a restaurant right, you prep, you do service, and then you go home so before service. This is mostly aimed at the managers, but sometimes we have to do it to explain the menu. What are we doing where's their goal? What are we trying to achieve? What are we selling source? Your ingredients?

A

What libraries am I using?

A

What frameworks? Why right there's a concept in the kitchens which is the prep cook, the prep, the prep cook, which you usually start? There is someone who takes pounds and pounds of onions and potatoes and just all they do is prep right. This is probably a project manager. They take issues they clean them be. This is this is something that sometimes all engineers should do right. We all should learn how to manage our own products, products and projects. Even if we don't do it every day, we need to know how to prep right.

A

Prepping is very, very important. It's not something we appreciate enough missing, plus is one of the most important concepts that I learned in the kitchen, and that has helped me the most. When I write software, it means putting everything in place right, you've. Seen this, you get everything ready everything chopped, there's so many engineers that I've seen that just start writing code and not really thinking where they're going to go, or they don't have their workstations ready.

A

It's very very important to learn how to do this during service communication is one of the most important tools right. How long are you going to take?

A

Are we going to hit our deadline or not? Why not? Let me know early, why are you blocked? Why are you not blocked? This is extremely important.

A

Establish supporting structures in this is mostly aimed at managers right when you are in service when things are going, but you have people, you have hungry people who are probably the worst people to be serving.

A

You need your those who are in the line of fire nee supporting structures right. That's the support team, who is the first line of defense bill that as a manager clean as you go, one of the biggest differentiator is between a great chef in okay. One is Heather station ends at the end of the service. Do you wipe so refactor your code as you go? If you open a file, leave it cleaner than what it was before? If you saw that someone know it's your job to clean it to inspect your code, these are code.

A

Reviews have someone else, look at your coat and tell you who the hell- or this is a will, come again. Taste, taste, taste or test test test right. Spoon always is food test, your code. Does it work? Does it work? Does it work? Does it work? Does it work learn to serve?

A

Do you know how to build your own? How to serve your own product? Can you ship it one of the biggest advantages that we have and software / kitchens is? You can push updates to your product after it's been served, you can't do that in the kitchen, once it's out its out after service cleanup, always the projects over you have all this to do's and all this tech dead, clean it up.

A

Document not just for yourself, but for those who are going to come after you right. This is a very common thing to do after, like you, you have five pounds of chicken and you just use them, and you don't know when it was caught. You know you write it down. It's important to tell future you. Why beware don't move this line or tell Billy? This is going to break eventually right.

A

Research, this is a fantastic picture. This is an egg cooked at 30-second intervals and how it looks this is extremely important in engineering then teach us. The only reason why we have this fantastic foot today is because other people took the time to teach each other right, though, the intern in the in the kitchen is one of the most valued members, because they are the ones we're going to carry over are our trade right.

A

Hopefully it will not be for eleven dollars an hour in the future.

A

A

Questions about food or engineering.

A

Okay, thank you very much often talk.