Leveraging Procedural Knowledge

Video in TIB AV-Portal: Leveraging Procedural Knowledge

Formal Metadata

Leveraging Procedural Knowledge
Title of Series
Part Number
Number of Parts
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Release Date

Content Metadata

Subject Area
On the road to senior developer, one has to learn multiple languages. This often seems like a series of massive obstacles wherein each new language resembles a new beginning. However, developers may often underestimate the extent to which procedural knowledge from one language transfers to a new language. In this talk, I will demonstrate that the process from Red Hat Technical Account Manager to Django Girls workshop participant to OpenShift developer was a series of procedural knowledge transfers, wherein the obstacles to learning reduces with each new technology that is learned. I will provide specific examples, from using editors to troubleshooting issues, and conclude with practical recommendations on which language to start with and how to create a coherent plan for transitioning from one language to another.
Computer animation
Programming language Multiplication sign Forcing (mathematics) Software developer Line (geometry) Rule of inference Computer programming Declarative programming Wave packet Neuroinformatik Data management Mathematics Word Process (computing) Integrated development environment Meeting/Interview Hacker (term) Alphabet (computer science) Order (biology) Website Weißes Rauschen Procedural programming Logische Programmiersprache
Group action Information Multiplication sign Execution unit Stress (mechanics) Bit Shape (magazine) Coma Berenices Mereology Rule of inference Computer programming Number Frequency Radical (chemistry) Word Data management Process (computing) Web-Designer Weißes Rauschen Logische Programmiersprache Booting Spacetime
Programming language Group action Software engineering Knowledge base Code State of matter Patch (Unix) Multiplication sign Gender Sheaf (mathematics) Mereology Process (computing) Hooking Meeting/Interview Different (Kate Ryan album) Musical ensemble Procedural programming Office suite Extension (kinesiology) Reading (process)
Satellite Boss Corporation Group action Open source Information Knowledge base State of matter Military base Multiplication sign Interactive television Online help Disk read-and-write head Mereology System call Rule of inference Front and back ends Uniform resource locator Integrated development environment Meeting/Interview Physical system
the book deal with that of the and the and the and end of the and idea of ch now I realize I'm the only thing
standing between you lunch so I'm that but if you have questions more questions alright so today is about
leveraging procedural knowledge which is 3 really long words to say how word and so don't be intimidated by that hard if you're new because everyone's actually new promise and something rumors RL procedural knowledge and and how to implement that 1st you going to you know thyself have a getting to know me really drink from Firehose return to our roots and talk about a managing girls workshop In this talk about next steps that OK so procedural knowledge is actually better defined better understood by understanding declarative knowledge declarative knowledge is Amsterdam is the capital of the Netherlands and J is the 10th letter of the ISO Latin alphabet and it's really hot outside kids were in Texas a melting to them from the Netherlands that's the declarative procedural is how you write like how you drive your car height training for a marathon at which it was never done how you learn how you do so it's facts forces process so why does that matter will there 2 schools of thought 1 is that in order to learn something new the you learn the facts and in practice in practice in practice in practice in practice in practice the and tell it becomes procedural knowledge you don't even need to think about it in more and you don't even maybe remember how you learned that facts and that's totally valid the other school of thought is that it the you learn something and then when you wanna learn something new you remember the environment where he learns that maybe there was some white noise but it's a quiet room with all the curtains walked out and therefore you want lines with the news you recreate an environment anyway something out it's learned more efficiently that way because that's how you on something else in your brain goes and learning something OK FIL if that so the 1st steps to procedural knowledge is actually know yourself and all hi session I am interminable uh a mother of a 10 month old who is right there and you can say hello later or not and and I 1st programs on a TI 99 for a computer where it's maybe you remember it maybe you have no idea what I'm talking about and that makes we should old but I island basic on the manual that came with that computer the only thing you could do was follow the rules that was it there was no hacking there was following the rules for 8 doing nothing you can even take it apart and put it back together and do something new it was that for nothing and so I learned how I learned I practiced and I red and then I did and I found that if I just read the manual and then put it down that i it completely was gone so I I realized I had to go the but this a so myself taught myself HTML and CSS in PHP and Javascript back when I was a developer further went I did the a bill website it was I on Angel Fire I know I'm dating myself these judged it's important for you know how you learn not necessarily in linguistics or languages but how you learn and what you're comfortable with his that's what you will use to apply learning new base the Elliott logic puzzles like math and therefore every time learning language I pick out relationships and that may not work for you and if you ask the question at the end you're you so many other less out and up only got something just like it you
might be a certain no so where for Red Hat this is actually a Red Hat because the Fedora doesn't travel well internationally so I this to the crutches out those in the suitcase really easily started that as a technical support engineer and 6 years ago when I started and half you can't surpass the orange CE within 90 days you got 3 chances for you were fire and lot of stress no good I wanna tell you a little bit about the US Air Force military vs. Red Hat's became I know it doesn't seem related but it is given in Sec I don't want is calling give me a 2nd so the US military boot camp for the United States Air Force is you got a lot and therefore space and it's about 6 weeks in and you exercise a hell of a lot you run like crazy you lot of quarters you change clothes a bunch of hair shaved off it seems like health if you're there may be and your sleep deprived you learn a lot of rules and it seems like the purpose of it is to get you in shape and to charities of gotten maybe and maybe wearing those basic skills but the actual underlying reasons for that group here is so that when someone tells you the jollop you job you don't even ask how high you just jump but the underlying so then we had to red hat and promise session sleep deprivation while they're asleep at her its but there's there's no running definitely and it's it's 90 days it's actually 30 days and then you get 3 chances and the obvious is that you're going to have see the and not confined to a new but the underlying is that every time you answer that phone you will have no idea what they're talking about not enough to completely stay calm what are you trying to do how are you trying to do it what's happening what do you want to happen stay calm gathering information and then hang up the phone and word and whatever they're talking about in a very short period of time and that's what red happy campus so there are 2 layers of things and he basically you have to drink from the fire hose and that's did procedural knowledge I started taking logic I personally need a white noise generated lots of quiet outside of that document to room and logic between commands line the the words and I passed the it unit after the 2nd try you so I did
that for 6 years I was a technical support engineer and I got familiar with and stuff and then I moved to the Netherlands became a technical account manager and while you're doing that you're constantly having a learned lots lots of information really fast in he'll and when I think that's great really bright and then exhibit that by the time of old not like that guy in front of the terminal ends in the Netherlands rely on to scale back at work and the part time but you can be apart from technical account manager so my job became to look for a new job hopefully within that hat so setting workshops in the very 1st Workshop attack jingle girls up in which is where I live grown again if you're American this place and I a lot of data preparation again was using procedural knowledge was using get which I had lots lots of experience from the sky it was using troubleshooting after Google and inspire remembered how much I loved web developments and I went in 1 thank him enough programming anymore I well I don't have time for a all time and in number of things so I put up they act on for roku now . com which I'm very talented of well into the Microsoft Ashish high red hair but it will be and after workshop
and in the tutorial extensions which means that there I uploaded it on OpenShift that would give me the linking separate 20 down and put it back up and 20 it down and just have to wait your own free posting there and make a lot of ugliness states I have the recommended and then next steps from so your next steps might be when you're learning a new language I especially with Django and they change the tutorial work tutorial so they now it goes on to hide from anywhere bands you might you that you might parts practice practice practice if that's what you need I highly the commend community contribution even if you're not coding you can always contribute to the documentation and it's usually the same process as submitting a patch and therefore you've learned a procedure that once you use code will be easy to implement build an outbreak stuff and then for me I'm going to go back to Framingham and their coach on September 19 the promise to sleep deprived from the flat by so it's really next actually is that are not coding in jingle at all in the higher this time with a group of iron went from being a jingle girls workshop participants to Red Hat Software Engineer in of 5 months because I drink from the fire hose approve myself and then I ended up getting fired to a different section of Red Hat that doesn't use gender hook at all they just care that I know at and so they don't care that I learned they don't care the language of pi bond Django it and actually wants to rails they care that island fast and that's what a lot of people care about can fast and then I know myself and therefore I know how to work past so no Ancona OpenStack and and my code on I mean I contribute to the community because it just started on July 6 so I'm still just helping with the docks and a lot of reading and ramping up and that is how I used procedural knowledge to get from the workshop to Red Hat
Software Engineer and now you can to the during questions or would you like to can want the so back in the day of the year um companies were told the into this idea of having knowledge bases air the welcome there were 4 had a chief knowledge officer whose duties were somewhat ill-defined and all that kind of stuff so that but the idea seems URIs
out what do you think of having company-wide or group-wide organization-wide systems for organizing all this shared In intuitive group knowledge that people are the bosses TV rotamer heads right we do that actually and by we I mean Red Hat I'm in the US support side and were starting to integrate engineering actually alot of people on the support side were like you're going engineering let's implement k bases and what we have as the arts which are especially based routing so if I get back all and it's about cluster and I have new nodes reason cluster again all the information as a common learned the basics so that I know what questions to ask the people that actually do know about cluster and my specialty is satellite so when I have went on into the phone and then go over and help people that don't have any experience the satellite answer their questions so we do that I highly recommend it its own actually think that's part of Hardaway open source is all about is here's my knowledge play with it and more it and the other we have time for the questions the microphone can come to you if you prefer not to come to the microphone don't be scared the OK and what the and hi things those and talk and I was gonna ask following on from the 1st question do you think there's all how much value thing there is to knowledge bases that output of descriptive this maybe because of tutorials and things that people come what 3 then like which would you recommend already think needs above I say both actually and we have both we use both the people that come on and they're like I need something very very specific I need to know how to set up a role environment with the cluster using the ends and something very very specific and those might need a person to give the final outcome but we have something to get you close and then we have tutorials and interactive state people never need to come call because it's all the information is there and I I strongly bound as I passionately feel that if the if the knowledge is there and then you can self help and that actually that's more important to teach people which is what this talk about is about actually I can teach you something all the longer you won't by just it and for you actually teach yourself and practice or whatever you need but if fact the I can talk all day right they won't stick so we have 0 short into it anyone else the the to build on that same
question and and your answer me be to proprietary and maybe the audience can help to but my team struggles with how best to share that knowledge with each other and with our future selves and and the tools we chose an overtime hour varying and incentive so does at what advice do you have for how best to share the tutorials the lessons learned the instruction manuals and and not given specific documentation for an application but as the team business rules that change of reaI again yet so when I 1st started with Red Hat we were very like all over like we get information and it's still as I will be completely honest on the back ends and actually there's like a million ways and it's kind of ugly to share information but you have to have a really good search that can network with all of them and that holds and the other thing that we did was we built a portal that was the central location where customers and employees could both go and depending on your permission of course you would be able to dive into more or less information so a customer we wouldn't want to give or or issue that we're working on that has other customers private information on but if there was another employees searching for that same problem we would want them to see that raw information because that might solve their problems and therefore they can help solve this problem so so it's it's a double I would highly recommend an integrated search and then if like integrating all your tools into 1 portal for example is what we did there might be other solutions I'm sure there are but that's what we did thinking of this meant of you have any comments questions snide remarks please feel free to cheat the mount over the to the fear and I will respond and thank you very much so Hugh fj but the mind my my