There is the initial hassle of trying to find a decent name, then you should try to find the best writting style, like is camelCase best or using_underscores better?
This is why I took the white board off of my wall, and started using a spiral bound notebook for project planning and design. Also, I stopped abbreviating objects and variables, and began using the most obvious descriptors possible, regardless of length, which ultimately led to more readable code. 🤘
@@benjaminjordan2330 it depends really on the style. I think that in the case of programming "too much of anything hurts". Keep it sleek, readable, document and use comments. You should be fine.
This is like listening to my boss try to describe an app he wants to build. I'm sitting there the entire time just thinking, "I could maybe accomplish 1/3 of what you asked"
I had a project manager/former code describe how we might fix something for five minutes. The programmer supervisor who's German sits through the whole thing thinks for about ten second on how to put it nicely and says "No. I'll figure a way to do it."
contextually I think this is ok. I have some Rust code that goes `match chars.next() { Some(c) => c, Err(_) => return Err(...) }`. But if I were to do more work on my `c` variable I would probably want to give it a better name
"what's in a name?" is an underrated question in design. the naming arguments reflect design thinking that has to happen and often takes way more effort than a whiteboarding session will suggest.
I use chatgpt in my programming. Not to do the actual coding, it is crap at that. More... "I have a variable that is used for x, y and z. What do I name it? Give me ten suggestions."
Oh good lord yes. And then scaling is a terrible nightmare if the code you made wasn't made for hundreds of thousands of rows. Trust me... I went down that road. Always paginate your shit 🤣
@@tisaconundrum Connecting things in code can be challenging, but not necessarily requiring knowledge of everything: Abstraction and Interfaces: Modern programming leverages abstraction and well-defined interfaces. You don't need to know the internal workings of every system you connect with; understanding the interface (functions, arguments, data formats) is often sufficient. Libraries and Frameworks: Existing libraries and frameworks often handle the heavy lifting of connecting systems, providing ready-to-use components and simplifying the process. Standardization: Established standards and protocols across domains (e.g., APIs, data formats) make connecting systems interoperable without needing profound knowledge of each. However, challenges remain: Complexity: When dealing with highly complex systems, understanding their underlying principles can be beneficial for troubleshooting, optimizing integration, or creating more resilient connections. Edge Cases and Compatibility: Unforeseen scenarios or compatibility issues might arise, requiring deeper understanding and debugging skills. Performance Optimization: For performance-critical connections, knowing the internal workings of both systems can help optimize efficiency and resource usage. Ultimately, the difficulty of connecting things in code depends on several factors: Complexity of systems involved: Simpler systems with clear interfaces are easier to connect. Availability of tools and libraries: Pre-built solutions can significantly simplify the process. Desired level of integration: Deeper connections might require more in-depth knowledge. Programmer's experience and familiarity: Expertise and understanding of relevant concepts make connections smoother. Instead of requiring knowledge of everything, the key is to: Understand the interfaces and protocols involved. Leverage existing tools and libraries whenever possible. Be prepared to learn and troubleshoot for potential issues. Seek help from communities and documentation when needed.
This channel is very helpful for every experience and beginner programmers, the every videos are helpful to become good programmer ❤😊, Keep growing love from india.
If you are doing OO and someone names the variable a verb stop working with them. Variables are nouns. Methods are Verbs and enum values are adjectives
Oh man... I was today making variables, and for the second user I was naming them 'second_variable' when I came to name user seconds I was totally dumb folded if I really should name it second_second 💀
@@sshad00ww95 I know. But the variables are seen by the user, I'm making a discord bot and it was a part of a command. Writing second looks more user friendly than a number would
I don't know what your intent I was with this but I am not a fan of that naming convention nor am I a fan of any of the suggestions, I would take some more time to consider it which kind of goes along with the meme but those names wouldn't fly in a coding interview as they seem very beginnerish. Maybe even OOP might be useful here e.g. having a user object with a time_in_seconds attribute
If Naming variable is hard for you then you are a really good programmer. It means you take the time to ensure your code can be understood by anyone without having to explain it.
INT does represent whole number , whole start from 0 and goes up to infinity ,which does not include negative numbers where we can say that INT represent integer number which ranges from (-infinity , +infinity)
I just do "database_users" or "database_posts" for databases... "IInterface" for interfaces, "EEnumerator" for enums, "TType" for types, "CClass" for classes, "FFunction" for functions, "ConstantVariable" for constant variables, "normalVariable" for normal variables, and "temp_temporaryVariable" for temporary variables.
After finished designing solution, the next thing I did was to ask my coworker what is the format of the model name, variable name, and method name. 1) Because I have somewhat a compulsive tendency to have things in uniform; 2) Even if the other person doesn’t develop the model, they would still understand what’s happening.
There needs to be a vscode pluging where you can just put random var names in and later down the line you can run the plugin and chat gpt will write var names in
Naming variables one was extremely relatable.
You could call it a instance, but then we could also call it db_initalized.. or shall we use Hungarian case?? Or snake case?? AUGHHHH
god its just confusing to name variables
@@jeanssradio.7067In my program I simply call it server_db or users_db or logs_db or main_db. Depending on what the database is for
Put a comment after every variable 😂
dbInstance is meh
The most unrealistic part is how fast they agree with each other.
I can't believe there is even more than 1 dev in a room 😮
hahahahaha
Usually waste like 3 hours arguing before you both realize you could’ve made both of the solutions and been testing right now
they still didn't talk about the "Push To Production" part
Planning for our project VS how it ends up 😂
we're all living the same life
@@sexymeal2427😮😢
guys where can I write code? not learn, I just want to make my own code.
@@imzainovs code
@@imzainovs code i believe
Naming variables is my bad part of programming.
There is the initial hassle of trying to find a decent name, then you should try to find the best writting style, like is camelCase best or using_underscores better?
@@iliyasamine6483 underscores by far
Writing useful comments and/or commit messages comes a close second
@@iliyasamine6483i tend to go for for all lowercase no underscores shortest possible, so if i went for db_connect i'd prob call it dbc
Just call it alphabetically
What is it they say? There are only two hard things in computer programming: cache invalidation, naming things, and off by one errors.
You forgot segmentation errors
@@freeloaderuser6793 so there are 5 hard th
Segmentation fault (core dumped)
@@nigerianprince2620 u into structs huh
😂😂
I see what you did there 😂
This is why I took the white board off of my wall, and started using a spiral bound notebook for project planning and design. Also, I stopped abbreviating objects and variables, and began using the most obvious descriptors possible, regardless of length, which ultimately led to more readable code. 🤘
I'm gonna do this when I get deep into coding
Lol yeah I used to think it was cool to make variable names super compact but over the years I have started to make them very obvious and descriptive.
@@benjaminjordan2330 it depends really on the style. I think that in the case of programming "too much of anything hurts". Keep it sleek, readable, document and use comments. You should be fine.
Long ass names are also not readable, they must be as short as possible yet understandable
Based
The worst part is when you have another variable already occupying the name you want to use and you end up with semi-sentence variable names.
This is like listening to my boss try to describe an app he wants to build. I'm sitting there the entire time just thinking, "I could maybe accomplish 1/3 of what you asked"
@@OpenWebDiscourse1/3 of cancer cure is quite good actually
That's probably because it made ~33% sense though, in your defense
Where do you work at
can it blockchain?
I had a project manager/former code describe how we might fix something for five minutes. The programmer supervisor who's German sits through the whole thing thinks for about ten second on how to put it nicely and says "No. I'll figure a way to do it."
go developers: hold my one letter variable name
oh god i hope i wont ever need to maintain your old code
contextually I think this is ok. I have some Rust code that goes `match chars.next() { Some(c) => c, Err(_) => return Err(...) }`. But if I were to do more work on my `c` variable I would probably want to give it a better name
@@izd4it would be fine how you use it, and for example in for loops to keep track of a certain number, but definitely not as ‘actual’ varliaboes
Sounds like Fortran
The main reason I haven't succeeded in learning programming is that I constantly watch videos like this instead of learning, haha)
I hate how relatable your comment is. F*** you dude!! 😭
😂😂😂😂😂
x2
me too fam
I suffer form this everytime 😭
They nailed the idea of the joke, just not the example of the joke
"what's in a name?" is an underrated question in design. the naming arguments reflect design thinking that has to happen and often takes way more effort than a whiteboarding session will suggest.
The Collab we never expected 😮.
“Like 4 hours if we really just sat down and did it” [6 months pass] “Like 4 hours if we really just sat down and did it”
Yea, the "variable-naming crisis" thing is very relatable 😂
Half of my commits are basically for renaming variables because I start to hate the names I gave them 😅
There are 2 things that are hard about computer science
Cache consistency
Naming variables
Off by one errors
There legit dumb I’m smart I’m rich of wow gold loser
I’m a newbie to programming, and naming variables is the absolute worst. Takes half my time
Thank you, KC. Your words resonate with me deeply, man.
I use chatgpt in my programming. Not to do the actual coding, it is crap at that. More...
"I have a variable that is used for x, y and z. What do I name it? Give me ten suggestions."
Rough architecture skit vs. actual coding.
Me struggling to not put swears in the names when other people are going to see it 😅
That whiteboard is extremely accurate lol and the variable names haha
Connecting two seperate things is very difficult. We have to know everything to the core.
Oh good lord yes. And then scaling is a terrible nightmare if the code you made wasn't made for hundreds of thousands of rows. Trust me... I went down that road. Always paginate your shit 🤣
You don't have to know everything to the core.
@@RealSaudiExplorer not if someone else knows it for you
@@tisaconundrum Connecting things in code can be challenging, but not necessarily requiring knowledge of everything:
Abstraction and Interfaces: Modern programming leverages abstraction and well-defined interfaces. You don't need to know the internal workings of every system you connect with; understanding the interface (functions, arguments, data formats) is often sufficient.
Libraries and Frameworks: Existing libraries and frameworks often handle the heavy lifting of connecting systems, providing ready-to-use components and simplifying the process.
Standardization: Established standards and protocols across domains (e.g., APIs, data formats) make connecting systems interoperable without needing profound knowledge of each.
However, challenges remain:
Complexity: When dealing with highly complex systems, understanding their underlying principles can be beneficial for troubleshooting, optimizing integration, or creating more resilient connections.
Edge Cases and Compatibility: Unforeseen scenarios or compatibility issues might arise, requiring deeper understanding and debugging skills.
Performance Optimization: For performance-critical connections, knowing the internal workings of both systems can help optimize efficiency and resource usage.
Ultimately, the difficulty of connecting things in code depends on several factors:
Complexity of systems involved: Simpler systems with clear interfaces are easier to connect.
Availability of tools and libraries: Pre-built solutions can significantly simplify the process.
Desired level of integration: Deeper connections might require more in-depth knowledge.
Programmer's experience and familiarity: Expertise and understanding of relevant concepts make connections smoother.
Instead of requiring knowledge of everything, the key is to:
Understand the interfaces and protocols involved.
Leverage existing tools and libraries whenever possible.
Be prepared to learn and troubleshoot for potential issues.
Seek help from communities and documentation when needed.
That's what software engineers are for, unless you are the software engineer.
I am both horrified and glad that never goes away and its not just me.
Literally how non technical PM’s talk 😂
Pro tip. It's easier to just say PMs
This video is just pain
😂😂 I love these skits
Great collaboration
Love the tech channels collab!
Choosing PR label colors is definitely one of the hardest things I’ve had to do
Nowadays, the hardest part is getting a programming interview/ job and passing the coding interview.
This is applicable to so many domains. So true!
The hardest stage of Programming Selecting a variable name
Naming variables is the hardest part for me
- "I think it's too short"
- "we're gonna be here all day"
🌚
I just randomly pick a cuss word
THIS IS SO GOD DAMN TRUE!! All that shit and i be sitting trying to name some MOST INSIGNIFICANT VARIABLES!!!
Oh my God, it's so amazing to see you with Tiff🥳
Worst is trying to find variable names with SAME length so that all my expressions align 😢
Whattt that's gotta be just you, I just add some spaces to align the equals
We laugh 'cos it's funny ... we cry 'cos it's true.
Glad to hear others go through this
the part about naming variables is just sooo true
This channel is very helpful for every experience and beginner programmers, the every videos are helpful to become good programmer ❤😊,
Keep growing love from india.
A variable cannot be short enough. I never ever heard that complaint
If you are doing OO and someone names the variable a verb stop working with them. Variables are nouns. Methods are Verbs and enum values are adjectives
There is nothing harder than naming variables
Using underscores for variables in Java is a crime.
String User_name = MainReader.readLine();
if (User_name == "Holmes")
{
// rip
@@DiamondSaberYToh god. That inconsistent capitalization too 💀
As a person working in the same field i fully agree with this
Naming variables is like character creation in RPG games
Why is this so true lol. I always hammer my head because of variable naming and always get stuck at it for minutes.
Her : It's gonna be too short.
Him : we are gonna be here all day.
90% of the work is planning and meetings the rest Is actual work, Everytime I come up with a good idea I end up stuck in variable naming
True
Oh man... I was today making variables, and for the second user I was naming them 'second_variable' when I came to name user seconds I was totally dumb folded if I really should name it second_second 💀
Just name them variable2 and second2, i mean i dont know if u cant name them like this cuz of something else, but idk, im still just a beginner.
@@sshad00ww95 I know. But the variables are seen by the user, I'm making a discord bot and it was a part of a command. Writing second looks more user friendly than a number would
@@bankaihampter2802 oh ok then but maybe u can make that if variable is variable2 make that string they see second, idk it is just an idea xd
I don't know what your intent I was with this but I am not a fan of that naming convention nor am I a fan of any of the suggestions, I would take some more time to consider it which kind of goes along with the meme but those names wouldn't fly in a coding interview as they seem very beginnerish. Maybe even OOP might be useful here e.g. having a user object with a time_in_seconds attribute
OOP solves all the problems.
hardest part of programming is not the languages or syntax, but it'd planning out lots of stuff
😂😂😂😂😂naming the variables I swear...ongoing struggleee
Variable names and conflicts be like: hello mother- * board *
The hardest part has always been naming things
The hardest part of programming is actually
.
.
.
.
Talking you way out
Or if you want your idea implemented
Talking your way in.
The guy started the video with “block chain” like really man lol
If Naming variable is hard for you then you are a really good programmer. It means you take the time to ensure your code can be understood by anyone without having to explain it.
That's one thing. But we supposed to design it so that we understand "why the heck did we built this function again?".
The camera movement on the white board is a turn off. Helps with generously confusing people.😢
simple solution, name all variables var1, var2, var3... etc
Or maybe var000001, var000002, etc. to have consistent indentation
@@vaolin1703var010234 is NSFW don’t forget
Just make it a small description Int bigD = 12; or something
And its so important to be good at it. As a new backend developer, Sr devs kill my understanding of the code with 1 and 2 letter variables lol. 😭
INT does represent whole number , whole start from 0 and goes up to infinity ,which does not include negative numbers where we can say that INT represent integer number which ranges from (-infinity , +infinity)
I agree, that is too short!
Context: they are planming the virtual nuke from Castle
Ah yes, the 2 hard problems of computers science. Cache invalidation, naming things, and off by one errors.
this is most relatable video.
Suffering from naming more than solving problems 😂😂😂😂
The hardest part of development is is installing all the necessary files for the work 😂
It's actually selecting the VSCode color theme.
Hardest part: explaining the entire code to your partner
Date/times and timezone offsets. That's just lovely.
"Mal nommer les choses c'est ajouter du malheur au monde"
>> "Wrongly name things is adding sadness to the world"
I just do "database_users" or "database_posts" for databases...
"IInterface" for interfaces,
"EEnumerator" for enums,
"TType" for types,
"CClass" for classes,
"FFunction" for functions,
"ConstantVariable" for constant variables,
"normalVariable" for normal variables,
and "temp_temporaryVariable" for temporary variables.
I think setting up libraries/frameworks with compatible versions and dependencies is the worst.
I agree with variable naming
All kidding aside, naming things is the hardest part of being a programming.
That is soooo real it looks realistic
Naming variables really is one hard multivariate optimization problem.
you forgot about cache invalidation
Be a madman name the variable peepeepoopoo
The 2 things hard in it:
- Cache
- Naming things
- Off by 1 errors
What's that quote?
"The two hardest things in programming are naming variables, cache invalidation, and off-by-one errors"
Naming variables is the most confusing part.
True, naming a variable while keeping many variables in check.
Hardest part is not to get distracted while coding.
The amount of times I keep changing variable names... Lol.
That hits so close
Dare I suggest taking a look at Application Hungarian Notation?
Hardest two problems in programming
0. Cash invalidation.
1. Naming things
2. Off-by-one errors.
😂
This hits home xD
Thank you, the suffering coders go through every day when naming variables goes unnoticed to most of society, coders are people too😂
Center a Div is still the most difficult thing in the world
I love that "ChatGPT" is just casually written there 😂
Ironically, it's better at naming variables than me
After finished designing solution, the next thing I did was to ask my coworker what is the format of the model name, variable name, and method name. 1) Because I have somewhat a compulsive tendency to have things in uniform; 2) Even if the other person doesn’t develop the model, they would still understand what’s happening.
There needs to be a vscode pluging where you can just put random var names in and later down the line you can run the plugin and chat gpt will write var names in
I knew this was gonna happen the moment I saw the title 😂😂
Love it!
(I am only a CS student, but this is actually how it often is -> even naming a variable is very important)