Skip to content

Instantly share code, notes, and snippets.

@amrabdelwahab
Last active September 22, 2017 15:42
Show Gist options
  • Save amrabdelwahab/60b18f41b163cb3e085101a3ddab1efc to your computer and use it in GitHub Desktop.
Save amrabdelwahab/60b18f41b163cb3e085101a3ddab1efc to your computer and use it in GitHub Desktop.
Greenfox demo 3

Generic Comments

  • Starting from scratch, draw on paper, think outside the syntax
  • Red, Green, Refactor <= is very important
  • Tania's presentation
  • The "Ahaaaaaa!!" moment
  • Naming conventions, Naming Conventions, Naming Conventions!!!!!!!
  • Explicitness VS Smartness (Too Much Dry makes the skin burns)
  • Why the else
def do_recursion(params):
  if <BASE_CASE>:
    return <BASE>
  do_recursion(different_params)
  
  
do_recursion(entry_point_params)
  • MORE GIFs:D:D
  • Borbola Dobo question: What are modules?
  • Style Guide and Linters

Tibor Kocsis

  • Title is smart
  • Catchy introduction and so on
  • Highlights is a great thing
  • Split: Further refactoring into smaller functions What is otos? Parts is a bad naming convention

Attila Kezer

  • What is a tkinter library? whn you mention a library explain it
  • Where does the label and entry functions come from?
  • l1, t1 definitely not good naming conventions to show on a demo
  • b1

Peter Keler

  • ++ For speaking about fractals and recursion
  • Very Big code example and you should have tried to refactor it further
  • why do you need the else on the recursion,
  • The rectangle line of code does so many responsibilities
  • Very cheerful, good voice tune it was really good

Barni Balazs

  • The definition slide had so much text and looked scary:D
  • Why do you need the else in this draw_fractal
  • Code repition

Zsuzsa Fulop

  • To speak about the "drawings"?
  • Code repetition, why else?
  • Monotune

Zagon Kristof

    • for talking about challenges
  • Interactive asking questions
  • joking, great way of explaining the thought process
  • good mentioning what's a horrible code, good explaining what is a variable
  • start with blacks?

Tania Faklijer

  • Usual girls problem? (SW engineers prefers pc)
  • Starting from scratch, draw on paper, think outside the syntax

Andras Krausz:

  • Presentation Fluency, You stop and waste so much with details. I told you last time, live demoing is not easy
  • first level, second level are definitely not descriptive names
  • Demo was not so readable, terminal was black and small

Istvan:

  • line_play? line_play_double?
  • it was good story to share your learning
  • I don't know if in python this mass assignment is a neat way
  • It was smart but not sure about readability

Zoltan Makadi:

  • Low voice tune and lack of confidence
  • The code format looked weird
  • You kept the dark background
  • Why the else?

Bertok Peter:

  • So fast without any introduction
  • ++ for the highlighting approach and slides
  • LIVE DEMOS ARE A STUNT

Anna Maria Holcsik:

  • Good idea,
  • Clean code
  • come_back_x, come_back_y??

Balazs Prjevara

  • I was wondering where are the gifs:D
  • Recursion for me is just a way to iterate, so we have sequential, conditionals and iterative
  • More confidence my friend

Borbala Dobo:

  • What are the modules? good question
  • A module is a problem that was already solved, so no reason to re write it everytime
  • FLuent presentation, great approach
  • ++ for the way you thought of the problem

Luca Nagy:

  • Dark Background
  • step by step approach is good
  • x, y, a and b??
  • Make the canvas size a variable? So very static numbers are not good

Akos mate:

  • ++ for the gif
  • infinite loop
  • Great presentation about the concept, explaining it slowly

Tamara Szegedi

  • When you watch the video, ask the phsycologist how to eliminate the "aa"
  • Dark Background
  • Change your Tune

Andras Kamocsai

  • Use your music knowledge to explain
  • ++ for using row and column
  • code format looked weird

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment