Posted on Jul 13 Stop pretending you're not. We all Stupid. We make mistakes, we forgor things, we misuse tools, we believe lies. Just accept it, acknowledge it, admit it. We are stupid, soNow that you know that you are stupid, act like one. Write code like a dum dum for another dum dum to read it, because this dum dum will be you in an hour, day, week, months or years to come.Do not assume you will understand your code, you won't. Well, at least not immediately. It will take time, a lot of it, so much that you forgor what you understood in the beginning.This is bad idea, no dum dum will understand, we need to rewrite it. Now I can see what's goin on from the first glance ever years after. You are stupid. You can't optimize, you can't write perfect code. Be stupid and just write what you have to.Feels like code is slow? Don't care, just write it.You think there should be an abstraction? No you don't. You are stupid. Evolved monkeys are very very bad at estimates. Do not force it. Do not rush it. Make it "Just Works™". Once you done, you are stupid. Forget optimization, forget refactoring. Make sure you understand what you've done and make sure you will understand it later.Done? Now is the time to optim.. NO! You are stupid. Write test. Please, do it. Right now. You did? Commit the damn thing.Once you've done writing stupid code for stupid people that runs the stupid business, once you covered it with tests, you can finally optimize and refactor it. But it doesn't mean you should.Is is really slow? How slow it is? Do you know? Make sure you really really know how slow things are before optimizing it, otherwise you wouldn't know if it's any better. And remember, you are stupid, so don't guess, write benchmark or whatever.Do not abstract, unless it's been 20~ish time you've wrote same stuff. Even then you should reconsider it. Most of the times abstractions are simply wrong or change so frequently that you were better of without them.Stop pretending that you are an engineer, architect or whatever. You are not. You are stupid monkey. Do not invent things, other less stupid people did everything for you.I think you get the gist. Do not solve problems that doesn't exist. Do not look for them. There are no problems, just a task you need to do. Do it and nothing else.SOLID? More like STUPID. There's no such thing as clean code, there's no such thing as perfect solution. Only tradeoffs.Don't just apply every code style or programming pattern you've learned. It won't work. If there isn't one, find 3rd-party "default" that is accepted by community.There is no need in Google Approved Best Recommended Style Guide 9000. You will only hurt yourself. Rely on them only if your team already does.You can identify and apply patterns later, just don't force them.Don't try to add singletons, factories, commands, engines, solid, etc, just because you know them and someone told you to do. Your code should work and be readable, and stupid. Most of the patterns will come naturally as you write it, or will be obscenely obvious once you're done. If it's not, than it's not the time to add them.Same thing applies to stupid code. Don't force it's stupidity. KISS (keep it simple, stupid) design pattern doesn't imply that you have to write bad ugly code. Just write naturally as you brain spits ideas on how to complete your task. You can't possibly write good multi-threaded code. Not at the beginning, and maybe not even later.Multi-threaded code is hard. So hard, in fact, that async exists. And it does for a reason. Just remember, that async is actually single-threaded (except for gorutines and alike, they can and will try to use as many cores as you can give them).Your head is empty. Fill it with some knowledge. Read some articles, watch a video, attend a conference, read a book.Don't stop learning, because you are stupid. You can't become smart, but you can be less stupid.Learn every day something new. Repeat what you have learned. Make your brain remember it. But don't just remember.Analyze. Everything that you read, hear or see - analyze.Use your head daily. Do not rely on others. Do not ask others, they are stupid. You are too, but at least using your own brain will make you less so.Never ever trust anyone, not me, not even yourself. As I said, we are stupid and we lie.Sometimes we don't even know when we lie. Some may heard a thing on TV or from parents and believed it's true for the entirety of their lives and now they share it with you. They are your deepest friends, of course they wouldn't lie, right? NO!They may not understand it, but they can and will lie from time to time. We all do.Say no to every stupid idea you, your collegue or your boss has. It is stupid and you know it.Don't be afraid to say no to stupid stuff. Accepting it for sake of "command spirit" or "humility" is just wrong and will make your life misareble.I said stupid ideas. It doesn't mean you must decline every task you've been assigned. Just make sure that it's not stupid.And don't force it. If you have to, you have to. IT is a business, stupid business that stupid humans run. Do the thing if you will lose your job after saying no.Most of the things I wrote actually apply to other things in life. Some may say that some of it not even about programming, but it is.Humans and human interaction is a HUGE part of IT. Humans write code that other Humans use. Humans write articles about programming and stuff. Humans read code, not computer. Computer doesn't read code. It scans it for bits and bytes and stuff.The most problems in the codebase comes from humans. Improve yourself, improve your skills and remember that you are stupid.If I forgor something or you think otherwise, do not fret to comment. I am stupid. I lie.Thanks!Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Ben Halpern - Jul 3 Francesco - Jun 8 codeSTACKr - Jun 7 Manohar Anand - Jun 11 Once suspended, adambright will not be able to comment or publish posts until their suspension is removed. Once unsuspended, adambright will be able to comment and publish posts again. Once unpublished, all posts by adambright will become hidden and only accessible to themselves. If adambright is not suspended, they can still re-publish their posts from their dashboard. Note: Once unpublished, this post will become invisible to the public and only accessible to Adam Bright. They can still re-publish the post if they are not suspended. Thanks for keeping DEV Community safe. Here is what you can do to flag adambright: adambright consistently posts content that violates DEV Community's code of conduct because it is harassing, offensive or spammy. Unflagging adambright will restore default visibility to their posts. DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey. Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2023. We're a place where coders share, stay up-to-date and grow their careers.