today we're talking about Things I Hate About programming yeah look I'll be honest with you I don't have too much experience programming I'm still a newborn child in this field but I've still experienced some problems okay I'm hoping these problems will go away with more experience but based off tweets and videos from more experienced developers and you can't create the button because Bill is on it sounds like these problems are going to get a lot worse so uh one documentation the thing developers both love and hate documentation is kind of like how I feel about caffeine I hate it but I need it to function now obviously I'm not talking about useful documentation that does what it's supposed to do you know making my life easier and making me feel like an absolute genius because they know how dumb and incompetent I am and writes everything down step by step no no no no I love that type of documentation here's some documentations I like oh camel oh camel mentioned let's go rust stripe View and there's a lot more if you're an engineer or an open source contributor that helps with documentation I just want you to know I love you all developers love you we don't appreciate you enough without all of you technology would never be the Advance we'd still be eating rocks now unfortunately not all documentation is good we call those the documentations of Agony and despair documentations that are outdated that leave you with more questions and answers or documentations where it's just the code itself with comments I understand that reading documentation is a skill that you have to develop documentation back then used to be a lot worse I can't imagine what that used to be like but that's like saying we upgraded from getting stabbed to getting punched technically it's better but we can still do better here let me give you an example of a documentation that gives me the pain and the agony Google number 1.1 Google's terrible documentation yes Google you know the tech company that's worth over $2 trillion and has thousands of developers that get paid High salaries the one with fun company perks the ones that rejected my resume take a look at this documentation for their Gmail API let's check out the quick start enable the API seems reasonable configure ooth consent okay authorize credentials for the app all right create an API key we're getting somewhere I think set up the sample okay what's the sample what is this where's the syntax highlighting why do others have it and others don't oh it's an edge case because this is HTML no no no no shut up their interview process literally tests you on problems where you have to handle edge cases I don't want to hear any complaints look I know this isn't a big deal I mean some people use to program a notepad actually I think some people still do but remember this is Google we're talking about now here's the interesting part most of the code here is to sign in and sign out with Google which makes sense to be fair but this is the actual code that uses Gmail you know the whole reason I'm here why didn't they do this in steps and then give me the entire sample code you know Step One enable sign in and sign out step to Gmail and then at the end the entire code that they have here I feel like that makes a lot more sense whatever I'm probably just stupid it's fine number two Jo let's talk about debugging or as I like to call it console.log driven development oh wait some of you don't use JavaScript more like print driven development oh wait you don't use Python either ah more like SE out driven I hate bugs actual bugs and software bugs cuz it's literal proof that you can't code and you did something wrong and debugging is the process of you fixing your terrible code it's not fun debugging always starts slow I don't know about most of you but whenever I code with python or JavaScript I always just log everything out to debug I don't really do break points or anything like that unless it's something really crazy or if it's a language like C++ where you have to compile and build the app or if you really hate yourself assembly but for python or JavaScript or really any small program I just put a log wherever I think it's broken and if that log didn't do anything then I would just Spam them everywhere and it works all right I know it's not just me who does this you probably do it too don't look at me like that we both can't C but sometimes there's errors you don't expect and when that happens you think your programming language would come to save you and give you some helpful error message I mean you'll get an error message but you're going to get blessed by something like this yeah what am I supposed to do number three bug reports if you ever make your project public and you have people using your bad code then you'll probably have the pleasure of dealing with bug reports woo website's broken that's the entire report you ask them what's broken the thing which thing you know the thing that does stuff oh yeah the thing that does stuff that narrows it down to absolutely nothing you know it's like going to the doctor and telling them I don't feel good but you don't tell them any symptoms what are they going to do which is why I always thought it would be amazing if we had a tool that would make bug reporting easier like imagine if you could show a recording of the bug you had and it would record not only the error but also the console logs the network requests every step the user did all the technical details everything and if you didn't know how to explain it it then AI would help you write a useful bug report so developers can actually understand it and fix it well guess what you don't have to imagine it anymore with Jam the sponsor of today's video oh you sneaky if you've ever wasted hours trying to understand a vague bug report you're going to love this one Jam is a browser extension that allows you to create the perfect bug report here's how it works when someone finds a bug they select the Jam browser extension they can take a screenshot record a video or capture an instant replay of what just happened once Jam records everything it'll instantly generate a link to share with your team but Jam does doesn't just record the screen it captures everything a developer actually needs browser and device information console logs Network requests everything you need to fix the bug but it gets better you can use AI to write up the entire bug report so you don't have to as soon as you record a bug AI will write a clear description of the issue and a list of steps to reproduce the bug and since it has all the information a developer needs it can even suggest a potential fix it's like having an expert Qi engineer on your team who speaks perfect developer Jam also integrates with all your tools too jira GitHub linear no [ __ ] slack whatever you use to track bugs so instead of having these types of bug reports you get this perfect bug reports every time so if you want to stop wasting time with vague bug reports you can try Jam for free by clicking the link in the description number 1.2 Google's documentation again I'm not done with Google let's take a look at how to do specific things like sending an email let's check this out now remember I did the JavaScript quick start so let's see how I can send emails with JavaScript wait a minute there's no examples for JavaScript what many programming languages have libraries or utilities that simplify the process of creating and encoding my messages so why don't you share it you know they exist where's the resources oh oh oh my mistake Google the following code examples demonstrate how to create a my message using the Google's apis client libraries for various languages oh of course you'd share the resources for your client libraries for various languages I can't even be that mad about documentation because you know what I wouldn't write documentation to my code either I guess I got to look at the reference say and figure it out myself the usual oh look a video about the Gmail API titled the new Gmail API I wonder when this video was made the new G 10 years ago what you know I would understand if it was a smaller company actually smaller companies do have better documentation than this lobotomized trash so what's going on over there at Google and surprisingly I know it's not just me who's having this problem there's tons of people who complain about Google's documentation it's so bad that people need to create packages to prevent people from suffering and reading that piece of gar number four inconsistent naming all right look let me tell you this I didn't even know this was a problem until I started using different programming languages but mainly when I started reading other people's code I never realized how inconsistent naming is let's start with file names I mean how hard can it be to name a file here take a look at this you see the difference in each of these right Apparently one of these is right I don't know which is right leave a comment on what you think is right and it's not just file names either this also applies for variable names and you know this wouldn't be such a problem but every programming langu language has its own naming preferences why wouldn't they let me search up the naming conventions and coding free code cam okay I know it's a good source let's take a look at this there's four of them camel case snake case Kebab case and Pascal case look at this free code Camp actually talks about this it's not just me now based on the language you're working on and what you're naming the preferred case type can change wow I just don't understand how something so simple like naming could be so hard then again we just love to over complicate things I don't know if there's lore Behind These naming conventions I don't know it if you know it please leave it in the comments because I'm not going to search that up myself I would not be surprised if there isn't any lore behind this and it's just opinion I mean there's a whole debate between tabs and spaces actually that one I do understand I'm more of a tab person if you prefer using spaces you need to go to the mental Asylum I don't know what to number five VM I just hate Vim number six C++ I don't like C++ that's it number seven the coding sloth wait what you know I sure hate this coding sloth guy he just makes YouTube videos on stupid stuff I bet he can't even code and then take a look at his stupid sloth character character this thing's ugly why would anyone watch number eight sloth bites not only do I hate the coding sloth I also hate his stupid newsletter sloth bites it's a newsletter where he shares bite-sized programming information every week to make you a better programmer all you have to do is enter your email and you just get free information you know the content is good but I just hate it because I hate him if you didn't know that was an advertisement go check out sloth bites please number nine other programmers I don't even like myself why would I like other programmers number 1.3 I have problems with Google here's a funny thing the quality of Google's documentation depends on what you're using let's take a look at their ads API you know a service that makes them a lot of money because it's ads wow video tutorials that aren't 10 years old step-by-step instructions libraries and examples look at the languages this supports they support Pearl Pearl why can't they do this for all their API and then take a look at their angular documentation this is Peak it's gorgeous it's beautiful this is what I expect from a$2 trillion yeah so that's some things I hate about programming you know a lot of them are just skill issues there's probably a lot more things I hate but I'm too lazy to edit so bye