@om3galul989
usually I do isDone, isNotDone, isItReallyDone and isItReallyNotDone you know just to really be on the safe side.
@dmitriyobidin6049
1:58 Create more functions 3:14 Use more one liners 3:47 Add more checks 4:35 Use recursion 5:57 Write more comments, the more the better 7:12 Add more flexibility to your code 8:17 Use more variables 9:05 Getter shouldn't be a pure function 9:30 Refactor more code
@erejnion
Before I started working my current job, there was a guy in it that... commented everything just with a date and nothing else. And he had a diary where he kept what he wrote each day. And of course, he took that diary when leaving the job.
@Nethan2000
(reading the property changes its value) QUANTUM COMPUTING
@graham1034
Man, I always thought this guy I worked with was an idiot. Turns out he is just so far ahead of me that I couldn't understand. Thanks for this helpful video!
@smurfisevil
I like the anti pattern of using try catch not to handle exception , but allow the application to continue without valid data , just make sure to add a brief TODO stating you will add error handling later.
@ardentdrops
Clickbait title: How to advance in Satan's IT department
@kingscrusher
This is a video you might never see at GOTO conferences or Coding Tech and i find it both absolutely hillarious and really insightful. Thanks so much for your dead-pan humour on all things IT and personal. You are a natural stand up comedian if you want another career. Myself and my brother were laughing so hard... it was almost hurting with this video. Please do some more antipattern videos - maybe doing C++ is a natural anti-pattern :)
@DrunkenUFOPilot
Spaghetti code = well, everyone know what this is. Macaroni code = spaghetti code that's been chopped up into a great number of shorter functions. Rice code = chopped up so much, it's all functions or methods of one line each, if that much. A thousand tiny pieces!
@souleater9189
dog -> canine -> mammal -> animal -> person
@hrlrl9309
You forgot to mention that when someone comes to you with questions, what you do is give them the bare minimum amount of information about the class/function/etc. Something vague in an email like "The Dog() class returns an array of Objects" and stop there. This way they will feel stupid for not being able to figure it out on their own and will have to come back to you again and ask more. You can use this to cement your reputation in their mind that you are superior.
@oicmorez4129
I usually have groups of bools that are past versions of each other, like "isFinished" "wasFinished" "wasWasFinished" and whenever I want to update "isFinished" it passes it's state to "wasFinished", but first "wasFinished" passes the state to "wasWasFinished" it's for debug and some functions that check if the state changed trust me
@jimb032
In c++, abuse structs. Everything is a struct whether it needs to be or not. Organization is important!!!
@Coeurebene1
My proudest internship moment was when was I realized that "a -> b" is the same as "not(a) or b", and refactored about a one page C# algorithm to a SQL statement to drastically improve performances of my now completely unreadable code.
@HapablapPlays
Make anything global - you never know when you'll need it!
@codewithsid2063
The straight face master strikes again. 😎
@__morpheus__6837
The smirk on his face, as he is saying all this...
@matzibeater
A trick you can do in C: instead of writing array[index], use index[array]. Easily slips by at first glance and looks legitimate, but will give everyone trying to seroiusly understand your code a headache.
@josanisme
Summary: Why use anit-patterns? 1. Secure job 2. Revenge Tips: 1. Create tons of functions 2. Use one liner as much as possible 3. Use recursion 4. Good use of comments 5. Adding code you may need but never will 6. Lots of vairables the more the better 7. Start to refactor the code
@abdullahasad4042