Don't Obfuscate Your Function Names // Python Tips

#arjancodes #softwaredesign #python

[thomasroberts]

When you're 29, seeing the cutoff age for young + old is 30 hits pretty hard

[andreitimofte]

Great idea making short videos that focus on a small, simple thing. Looking forward to more of these.

[robertbrummayer]

Fullly agree. In the book "Clean Code" Robert. C. Martin calls them intention revealing names. Nice video.

[andreacazzaniga]

people dont realize how difficult it is to be consistently trivial

[arshadshaik]

Nice. What command did you use to change the function definition and function call names at same time?

[IMMORTALmen]

Can you please create a video or a series of videos related to PyQt? Thanks!

Not only about basics, because that's actually a lot of basic stuff here on youtube, but some interesting like multithreading, complex UI interaction between several windows etc.

[BradleyBell]

What hotkeys or extension are you using to edit the function names?

[AntonioAndrade]

What keyboard combination did you use for refactoring?

[redcrafterlppa]

I just realized how similar python and rust are syntactically while being totally different languages

[scleralp]

As a rule, function names should be verbs unless they return a boolean, in which case they should probably have the word "is" in them.

[hisamsowaib]

Can you make a video for your vscode setup, shortcut keys etc.

[kalyanrahman]

Can you tell me the name of the THEME you used in your text editor?

[Lodinn]

I've encountered a similar issue recently, but with database table names. Certainly indicative of a design issue when it's hard to explain in short and simple terms what something does... But figuring it out is the bulk of the work in my case.

Are there "not sure what to call it, will refactor later when it's better understood" moments in your work? How do you approach them?

[qwerty]

An easy way of remember this that I like to use is to treat functions as verbs.

get_prop()
calc_square_root()
defenestrate()

See? Easy

[douglasrossi]

I generally agree when you are doing a process from scratch and there's no other place documenting it, but I think there's an exception, for example, imagine a process that is manually made for years and it is very well documented. When you are automating it and giving it random names, this makes it harder to understand which step from the original document it is about. You can perhaps put a comment on that, but by doing so you give less importance to the document, which perhaps the person that is reading the code should know about, the document may have much more information that is not in code yet. Transitions may be gradual, and can be complex. Just changing names won't help much in this case

Reminds me of my PhD position interview ^^

[fayaz]

I can see that you use Vim in vscode. would you please make a Vim tutorials? like a real world tutorial where we change tabs, copy code from stackoverflow, delete a line & paste & so on...
thanks

[andrewjarman]

More shorts!
Your videos are great but sometimes the bitesize videos (fireship etc) are all you have time for.

[Temo]

Unless you actually want to obfuscate your code against decompilation/copyright violaton ;-). Although not using python (or java) but a fully compiled language would probably be more effictive than.

[kristiantorres]

What is the purpose of while True in the "read_name" function?