If this article wasn't AI generated, the writer should worry, cause ChatGPT could definitely have made this.

this article is definitely ai generated

This article is something I'd write in high school when the teacher wants 1000 words for a simple question.

You know every article that contains a phrase such as 'in the vast landscape of programming' or some variant is 100% a Chat Gippity special.

I'm pretty sure the robot that wrote this wanted to give programmers conflicting advice because it didn't want to be manipulated.

Ok, "You can't get good at something you hate". Well, that's my Javascript career out the window :)

I feel like the author must be a programmer of the likes of: if something == true { return true; } else { return false; } and then use a ton of comments to explain every line of code.

At #4, i am now sure that it is not written by a programmer. Programming is a craft and this sounds like an electrician telling me that he will make the electrics in my house in a creative and never seen before way. Please don't. When the next guy takes over, he won't say "oh my, this is brilliant! I've never seen something like this!" he will say "wtf is that bullsh*t. We need to rewrite all of that."

The joy of programming is the key thing. I've been coding since I was 13, in 1983! I love it! I programmed professionaly from 1991 to 2015. I retired when I was 45. I now code for pure unadulterated pleasure, I'm now 53. I will continue coding until the day I die. I still live, breathe and eat coding. It is the sheer joy of programming that keeps me going - I truly love it, I loved it at the beginning, I will love and continue programming till the end of my days.

I put the prompt into chatGPT and it wrote a much better article: Title: 10 Coding Habits That Make You a Bad Programmer Introduction: In the world of software development, writing clean, efficient, and maintainable code is paramount. Good coding habits not only enhance productivity but also improve collaboration and minimize errors. On the flip side, bad coding habits can lead to buggy, hard-to-read code that is difficult to maintain. In this article, we will explore ten coding habits that can make you a bad programmer. If you find yourself guilty of any of these habits, don't worry! Recognizing them is the first step towards improvement. 1. Inconsistent Naming Conventions: One of the most common coding habits that can hinder readability is inconsistent naming conventions. Choosing meaningful and consistent names for variables, functions, and classes is crucial. Using clear and descriptive names improves code comprehension and makes it easier for others (or even yourself) to understand and modify the code in the future. 2. Ignoring Code Documentation: Documentation is often overlooked, but it plays a vital role in maintaining codebases. Bad programmers tend to neglect documenting their code, leaving their colleagues or future maintainers in the dark. Well-documented code helps others understand the purpose, inputs, and outputs of functions, making it easier to debug and enhance the codebase. 3. Writing Lengthy Functions: Long and monolithic functions are a recipe for disaster. Bad programmers often write functions that span multiple pages, making it hard to understand their logic and troubleshoot issues. Breaking down complex functions into smaller, modular ones improves code readability and reusability. Aim for functions that do one thing well and are easy to comprehend. 4. Neglecting Code Comments: Code comments are crucial for explaining non-obvious parts of your code. Bad programmers either omit comments entirely or write uninformative comments that don't add any value. Meaningful comments provide insights into the purpose, intentions, and edge cases of the code, aiding future developers who need to understand or modify it. 5. Not Using Version Control: Version control systems, such as Git, are essential tools for managing source code. Bad programmers often neglect version control, leading to code inconsistencies, conflicts, and difficulty reverting changes. By using version control, you can track code changes, collaborate effectively with teammates, and easily roll back to previous versions if necessary. 6. Lack of Error Handling: A bad programmer often ignores proper error handling, leading to unpredictable program behavior and potential crashes. Error handling is essential for identifying and gracefully recovering from unexpected situations. By incorporating proper error handling techniques, such as try-catch blocks, you can make your code more robust and reliable. 7. Copy-Pasting Code: Copying and pasting code may seem like a time-saver, but it can lead to a maintenance nightmare. Bad programmers tend to duplicate code instead of creating reusable functions or modules. Duplicated code increases the chances of introducing bugs and makes code maintenance more challenging. Instead, strive to write modular and reusable code that can be easily shared across different parts of your project. 8. Ignoring Testing: Writing tests is often considered a hassle, but it is a fundamental part of ensuring code quality. Bad programmers tend to neglect testing, resulting in code that is prone to bugs and difficult to refactor. Adopting a test-driven development approach and writing automated tests can help catch errors early, maintain code integrity, and facilitate future modifications. 9. Poor Performance Optimization: Efficient code is vital for maintaining a responsive and scalable application. Bad programmers often overlook performance optimizations, resulting in sluggish and resource-intensive software. Understanding algorithms, data structures, and profiling tools can help identify bottlenecks and improve the overall performance of your code. 10. Resistance to Learning and Improvement: Perhaps the most detrimental habit of a bad programmer is the resistance to learning and improving their skills. Technology and programming languages

Wow, this article was such a nothing burger

The proverb is: "A jack of all trades is a master of none, but oftentimes better than a master of one." Literally: multidisciplinary knowledge often beats expert single discipline knowledge.

Sorry, this article is total crap. I don't worry about insulting the author as the article was definitely generated by some crappy AI.

"The emotional coder" reminds me of one of my favorite pieces of advice from "How To Write Unmaintainable Code": use emotionally charged variable names to distract the maintenance programmer from the underlying logic, e.g. "marypoppins = (superman + starship) / god"

"In the thrilling world of programming"

If you do copy code from a third party, I recommend putting in a comment with the URL where you got it from so if someone has questions later, they know where to look. Like all written works, code is only copyrightable if it's creative enough. Contrary to popular opinions, there's not 1000 ways to do things. There are infinite combinations of things you can do to create a product with code, but most individual blocks of code are boilerplate algorithms. It's easier to protect a whole product than a particular function.

Regarding the mastering of a language: I have to say that I only started to master languages once I explored more languages because you (or at least I) only start understanding how and why things work once there is some contrast and some language where it's done differently.

Article felt more like a wholesale of cute platitudes but little grip on reality. On the burnout issue, i fully agree that it's not how much you're working on it but how much you WANT to work on it. Have had weeks with a couple hours a day sleep that ended with me totally out of gas and happy, and have had weeks working 9-5 that ended in misery and despair. If you want to figure when you're in one or the other, think overtime. If you're willing to do overtime for free, you're in the former, "in the zone", happy life. If you're not willing to do overtime at ANY rate, you're in the later.

The full quote was "Jack of all trades, master of one, better than a master of none"

It is very motivating to hear your funny and very refreshing explanation ideas, I always find something in common with your point of view. Thank you!

back in 2001 a class mate in probabilistic class in college told me that a guy he met suggested him the best way to program is to learn your favorite language, dominate it and then learn to call other programming languages from your own. In other words, learn C & how to use emscripten to be fullstack dev.

Articles like this show very well what happens when you replace authors with AI text generators.

17:42 🤣🤣🤣 I agree completely with you. That was a wild suggestion from the article

It's like letting your heart navigate while driving - it might lead you to a beautiful place you didn't know existed.

@4:00 According to a Forbes article, the original quote comes from Shakespeare, and in its original form it stated “a jack of all trades is a master of none, but oftentimes better than a master of one.", and it was used as a compliment.

14:00 I love how fast it went from 0 to a 100 in a mater of one sentence

Quite frankly I mainly code because I want to achieve a functionality, the leaning comes as a side effect.

Re: C&P, there is a reason not to use it, at least while learning. If you paraphrase the code, or just rewrite it, that does wonders for retention.

maluco leu serio por meia hora algo que alguem gerou e postou em um segundo. e eu aqui assiti tudo, que brisa.

Jester of all, master of none. Btw, love the backhistory on the expressión.

Love your takes on this

As a baby intern one summer I was asked to do something in a groovy on grails site that qa used to keep track of something. I hadn't heard of MVC yet (or RoR), so being thrown into a spring (this was a decade ago) groovy on grails app was terrifying. I had no idea what beans were, or what Autowired did, I'd never seen DI, or DAO. I was just left to flounder for a month, so I dived all the way into spring source code to try to figure out what was happening there. It didn't help. Hard pass on 8 & 9.

The fact that you knew that little adage trivia, and edified the chat with it, makes you one of the most trustworthy persons I've ever seen online.

finally i understand recursion, thanks to diving in

#9 unfamiliar code Lol “I didn’t understand the cryptography libs, so I decided to implement my own so I could understand the internals. (It stores passwords in reverse)” ✅

on understanding the code, I don't think he really meant knowing how it's implemented. but understanding enough to realize possible bugs. for example understanding that shared_pointers in c++ can cause a cyclic reference and how to avoid that. while it may be an implementation detail that leaks into the interface it's still also an interface detail that you need to understand.

Im speechless about these tech blog creators.

I'm quite relieved I'm not the only one who sees stl as dark magic, not even sure if it was written in the same cpp I write in

Pro tip: explaining your problem to someone else can help you figure out a solution. This is because you have to think about it in a different way to explain it, and that can help you realize a mistake you overlooked, or didn't think of. Edit: I forgot to mention, explaining things is also a good way to learn something. So it's good to figure out the problem, and to learn something.

I 100% agree practice makes perfect. And if you burn out you're gonna hate it. But if you never spend some time doing it you won't get better.

Javascript IS still all about prototype inheritance. There may be some syntactic sugar (classes, extends, etc.), but the language is still working like before and will construct prototype chains under the hood.

14:45 The funny thing is that Picasso was famously quoted saying “a good artist copies, a great artist steals”

The "dive in" shallow loop😅😅

Basic constructor types in C++: The normal ones: Default constructor Parameter constructor The weird ones: Copy constructor Copy assignment Move constructor Move assignment The very weird edge cases: Single parameter constructors (allow for implicit conversion) explicit constructors (used to not allow inplicit conversion on single parameter constructors) Initializer list constructors (allow for constructing the object by just using {.member1=,.member2=...}) + constexpr versions of all of the above Probably some more I forgot about

Comma usage is the giveaway for me. I'm pretty good at writing, but even I don't use commas that egregiously and had to spell check such a word because I need coffee to function. Think: buzzwords, hollow phrasings, and a lack of relevant subtext or jargon. It only makes sense because it merely scratches the balls of what it's discussing.

The article is written by OOP programmer, each section 1st half is creating the class and 2nd half is creating instance of the class with some tweaks.

IMHO engineer who's "jack of all master of none" in programming context very often will write much much better code than "master of one". Thing is you don't need every feature of a programming language to write good code in fact the less you can use yet still be expressive the better. "Master of none" will write code that others can understand with fairly little study and "master of one" will often use esoteric patterns that take weeks/months to study. Now if one is building a framework to be used by multitude of projects then deep language knowledge will come useful however if one just wants to build application then there really should be no need to know all the esoteric little weird patterns of the language.

And this was a MEMBERS-ONLY article?!?!?

The article writer definitely stretched his 10 words per point into 100, like a high school student stretches essays to meet a word count requirement.

As a 10yoe I wouldn't say that looking at a junior coding changes how I think, but it does make mistakes more clear to me in the sense that I can rationalize why something is bad with more clarity.

my first car was a '98 dodge stratus. 100% agree

Programming is like being a mad scientist sometimes!

This was better in quality than most hero's journet novel. What tf is with these segment titles lmfao

Yeah that first one is really wrong, when I was at IBM they made a while point of trying to get people with a lot of experience in a lot of areas and different tools

"Jack of all trades, master of none, often times better, than master of one"

7:00 not me having to learn C++, ROS2, and actually program a robot with it in a month (mech eng here)

13:50 article just completely discredited itself lmao

This is clearly one of the best KZfaq channels ever

That's why I stopped reading medium articles a long time ago...

the repetition in writing was a clue, 4 sealed the deal I do not believe this article writer programs. I kind of agree with the point, but not for plagarism reasons, it's something you had to google, that's a great time to get that sweet sweet new thing to learn high, and most code that's got good seo for copy paste is kind of crap. Browsing api code is fun too, some of it's going to be hyper optimized and you just go naw I'm out, but seeing what the funny library wizard does behind the curtain is a great way to learn some things.

This is even more Ai flavored than the bachelor's thesis I have just read haha

7:10 Agreed, I am learning C right now and 3 days in I definitely don't know shit 😂

i feel like i just watched a slightly newer video where we decided the complete opposite of this on every point

Chat Gippity!

There should be an achievement when an article gets prime to swear w/out a bleep

The original actually goes something along the lines of “a jack of all trades is a master of none. But often times better than a master of one”

JavaScript being so simple to learn and master is big part of why we have so many crappy JavaScript frameworks. And because we have so many people calling themselves programmers having "my way or the highway" personalities they view the whole world through their One And Only True Framework where they've married themselves to the Framework and measure good vs. bad through that viewpoint.

It feels like someone converted C# into natural language given how much of the article is just dead weight.

If i could download a car, I ABSOLUTELY WOULD

As a human, I say "as a human" all the time

1. make cycles 2. don't make cycles 3. use branching 4. don't use branching 5. obey clean code 6. ignore clean code 7. do comment, 8. don't comment 9. love python, js ... 10. hate python, js ...

I think telling people to avoid rushed code is bad advice. There is an unavoidable tradeoff between time and quality. If you are writing safety critical code for an aircraft, you probably follow strict guidelines, choose a safe language, maybe even break out a formal proof system, you and your team should to plenty of testing and so on. If you are sketching out an idea in code, writing a prototype, hacking together a demo for a talk, etc. you don't need that much quality. What I'm saying is "know you project requirements"

For 2/10, I really think liking the project you're working on only moves the bar. You're able to overwork more and for longer, but there is still a limit. I've had projects I loved and spent countless hours on only to be totally unable to muster any motivation for anything at some point, even while still liking it. I'm barely 10 minutes in and not a single line didn't feel ai-generated. Shitty ai too.

Every single point is written as two paragraphs followed by two more paragraphs saying the exact same thing in slightly different wording. Sometimes it even uses the same wording! (e.g. "tomorrow might be too late" at 19:35). I would honestly expect a ChatGPT article to sound less robotic than this.

The full phrase is actually "A Jack of all trades is a master of none, but often times better than a master of one"

The first thing you should read in an article is about the author. If the author is not directly and actively involved in what the article describes, then the whole article is invalid.

If an article can easily be converted to generic dating advice by switching a few words, it's a bot article

Only time two heads is better than one is when your being spit roasted

Imitation is a cardinal sin? I guess the AI that wrote this article has no concept of third party packages and libraries.

Not to ever copy code (when possible) would be like reinventing the wheel every time. If it's open source, fair game? As long as you understand what the code is trying to achieve and it solves your problem, then why rewrite from scratch (my opinion).

If you ask me: #1 yes of course i can handle all the memory management. #2 my code is self explanatory #3 i pushed enough ### out there, no need to tell anyone how my interfaces work. #4 i can do it better than this library #5 i cannot do any better than this library #6 my debug functions can not cause any harm so i leave them in the production branch. #7 if i code weirdly enough, i become irreplaceable #8 I do top down only, nobody will ever notice #9 I do bottom up only, nobody will ever notice #10 "try" works, who needs "catch"?

"A jack of all trades is a master of none, but often times better than a master of one.", was the quote.

I've watched this video several times and I start writing the same comment every time

“Please write an article (500-1000 words) on the topic of "10 Coding Habits to Avoid" that includes controversial points that are likely to evoke a reaction and a response, thus making it viral.”

9:48 The time you enjoy wasting is not wasted time. -Laurence Peter

This article does NOT sound like a programmer writing to other programmers. It sounds like a (maybe) programmer writing to non-programmers, while hoping it might be useful to programmers. All the flowery language is NOT how I've seen programmers talk to each other.

If trying out languages is like tourism, then APL would be signing up for a guided tour of Antarctica

on number 2 i would say that you're going so hard that you can't even read what you're coding, then it's time to catch a nap and restart with a fresh mind and body

If two heads are better than one, ask yourself, Would you rather have a Siamese twin (two heads) or a third arm?

that article is utter shite. I wrote something to get licenses for packages into a csv file today and it was really fun.

My God this was a painful article

I don't think you need to master any language. Just become good enough. With that you can probably do like 80%-90% of required tasks. You can be senior dev without actually mastering a language. If you think of it like a driving. You can be good enough to drive confidently nearly anywhere, but you don't need to be F1 or WRC professional to drive. Beyond certain point there is also no more financial benefits. So sure you can master for sake of your own ambition, but not essential to do the job.

#4 - the writer sounds like someone going for their Ph.D in Comp Sci and plans to be a Teacher #5 - most of the time you can not due to deadlines, I agree though

I suspect the person(?) who wrote that article never programmed a day in their life. Ever. Anything right is a general principal applicable to any skillset/discipline. The other items are just not remotely something a programmer would say.

Articles like this, and their tendency to float on top of whatever soup of garbage search engines tend to serve nowadays, are a big part of what makes the modern internet such dogshit.

06:04 javascript is complex (for compatibility reasons), have you seen spec? I like javascript because it's not complex syntax (unlike c++, rust) and you kinda understand it (like AST but inside brain) and know what to search for

is there any video where he doesn't forget to turn off the notifications ?

I tried to create magic together with my coworker but they reported me to HR

What about: Jack of all trades, master of some

Meanwhile recruiters: Hiring master of all trades.