This advice applies to just all software projects. I joined a company and in my first month someone told me, "aah you're only working on low hanging fruits". Boy, it's humility to buy time and understand what's going on, than to turn things upside down the first week.
Nice talk, but I think it's not good to not show the slides when he presents his case stuies. So now I have to scroll back to where the slide is shown and have to remember the lines to understand what he says.
i'm a junior programming in python and i know 30+ modules of python, i think that python is the best programming lenguage for learn how to program and in the lenguage that you can be more productive than others programming lenguages, i live in dominican republic and thanks to python i have learned much things, since networking at automate task, is amazing, i love python because now i can understand how the hacking works!
jokes on you - what's with the elitism. Everyone goes through their own learning curve. What matters is that he likes Python and he's doing something useful with it.
"how did hellen keller's parrents get back at her" well both of her parrents died so... show up? "rearrange the furniture" "making a large number of small improvements would destroy the flowergarden. you're not a flower garden trampler are you?" that started mean, and then it just got meaner. the problem of the commons is that it isn't any one person's flower garden. when it becomes common property, then one person painting a mural becomes graffitti to the previous resident. we get it old man, you don't like change. you don't need to repeat yourself, or express it in a verbose manner. "so you aren't going to take my code and refactor it so it looks a little nicer to you" looks a little nicer can be a sift from unintelligibility to intelligibility, or vice versa. your complaint is simply the reverse. someone else has to read your ugly code which is old. or you have to be dispossessed of authorship and read something new. neither are truely bad. one of them will probably work better than the other. one will likely be easier to read and maintain. take for example new features. if you have a low amount of complexity by reusing mental models, the refactor might be more intelligible than the old code. alternatively if you are going for performance, taking people's mistakes and reducing the error can improve the code base as a whole by the part. when your ego is making you prefer one bit of code to another, and you can't fully recognize and praise other's work, it is time to step away. we all have aesthetic preferences, but our personal preferences of style are not mechanical optimums. "we all have OCD" you said that to python programmers. "when everything is neat and orderly you have more confidence, fair enough?" no. neatness and orderliness is not capacity to solve a problem. imagine not neat vs unneat of the same thing, but a pristine car body without tires, vs a junker going down the road. which is the better car? is a car a vehicle for transportation, or is there an ideal form of a car? is it better to fly a cesna around, or be a member of a cargo cult? function or form. if form, how do you distinguish an identify correct preference and disposition towards one style vs another?
Mr Raymond is a great speaker....
Good ethical suggestions in general. Thank you.
I really appreciate the insight of his experience. I hope to see more such talks. These are not usually available from the world
he says "fair enough" more in this video than i have said in my entire life.
This advice applies to just all software projects. I joined a company and in my first month someone told me, "aah you're only working on low hanging fruits". Boy, it's humility to buy time and understand what's going on, than to turn things upside down the first week.
Funny and interesting as always, great stories. Great speech!
Nice talk, but I think it's not good to not show the slides when he presents his case stuies. So now I have to scroll back to where the slide is shown and have to remember the lines to understand what he says.
Great talk. Thank you for sharing.
I can do print("hello world") in Python when do I start?
You already did it
fair enough
i'm a junior programming in python and i know 30+ modules of python, i think that python is the best programming lenguage for learn how to program and in the lenguage that you can be more productive than others programming lenguages, i live in dominican republic and thanks to python i have learned much things, since networking at automate task, is amazing, i love python because now i can understand how the hacking works!
Eliander Perez Come back to this comment in 3 to 5 years, read it and delete it.
jokes on you - what's with the elitism. Everyone goes through their own learning curve. What matters is that he likes Python and he's doing something useful with it.
@@andyd568 some people have shoved C++ and C so far up their ass that they cant see anything else
good one
Awesome
I have heard this before.
Great talk.
32:45 that's a yikes from me, dawg
37:20 hits keep coming
My python has six eggs...
"how did hellen keller's parrents get back at her"
well both of her parrents died so... show up?
"rearrange the furniture"
"making a large number of small improvements would destroy the flowergarden. you're not a flower garden trampler are you?"
that started mean, and then it just got meaner.
the problem of the commons is that it isn't any one person's flower garden. when it becomes common property, then one person painting a mural becomes graffitti to the previous resident.
we get it old man, you don't like change. you don't need to repeat yourself, or express it in a verbose manner.
"so you aren't going to take my code and refactor it so it looks a little nicer to you"
looks a little nicer can be a sift from unintelligibility to intelligibility, or vice versa. your complaint is simply the reverse. someone else has to read your ugly code which is old. or you have to be dispossessed of authorship and read something new. neither are truely bad. one of them will probably work better than the other. one will likely be easier to read and maintain.
take for example new features. if you have a low amount of complexity by reusing mental models, the refactor might be more intelligible than the old code. alternatively if you are going for performance, taking people's mistakes and reducing the error can improve the code base as a whole by the part.
when your ego is making you prefer one bit of code to another, and you can't fully recognize and praise other's work, it is time to step away. we all have aesthetic preferences, but our personal preferences of style are not mechanical optimums.
"we all have OCD" you said that to python programmers.
"when everything is neat and orderly you have more confidence, fair enough?" no. neatness and orderliness is not capacity to solve a problem. imagine not neat vs unneat of the same thing, but a pristine car body without tires, vs a junker going down the road. which is the better car?
is a car a vehicle for transportation, or is there an ideal form of a car?
is it better to fly a cesna around, or be a member of a cargo cult?
function or form.
if form, how do you distinguish an identify correct preference and disposition towards one style vs another?
Dont turn python into C++