Відео

Good advice!! I would summarize the video at the end just like the thumbnail, learning is based on repetition after all :D

Could you pls do videos on software design patterns usning Go! Just love the content on object oriented concepts, you made it looks so simple.

noise just at the point where you stitch it. look into it?

Very well-made video! I will say though I kind of disagree with the idea you have of not needing to maintain conditionals in your head above core logic just because you inverted if statements (1:18). In your example it is rather trivial so that logic holds up, however, with more complex projects that may not be the case.

#4 whitespace isn't a bad thing. Put your braces on a new line.

Yandere Dev should watch this

i was inexperienced and i was force to use deep nesting else i couldnt get the right result, the senior was lets refactor, we did 1on1 pair programing he moved around stuff but still deep nesting

thanks for not saying "write comments" the stupidest thing ever

HHKB. Love it.

the first 2 minutes are fine

No #3, isn't this short letter variable is what advocated by Go dev 😂

Avoid code duplication is THE NO.1 law in programming

I have a question, should your function definitions be at the bottom of your code or at the end or anywhere in between, close to where it's used? I find myself using two types of functions, one type which I use for reusability of code and the other type is just so I can organize the code and name it, so that I can collapse that code when I am not working on it. How I do it is that I put the reusable code at the end and the ones for collapsing code in between the code. It this a fine practice? I am talking about JS here, as it supports hoisting.

There are a lot of Videos, on general readable code, but I would like to see one, which gives you tips, for structuring a whole Project, at what point to use Classes or what valid to put in Arguments or write a whole new Function for etc. Good Video tho :)

The irony of this video title and how difficult it is to follow what the hell is happening on screen because of all the transitions and effects.

best

1:46 All fine and good until you run into an auth error and can't figure out if it's an authentication or authorization problem. Don't do this!

Law zero of readable code is to comment abundantly and always keep in mind that the reader might be... future yourself. I don't know about Python, but Perl, Java and C can be deceptive... Blocks of code? Tell me about looking for a bug in a regular expression just 6 months later in a function called from pretty much everywhere in hundreds of lines of code (i.e. a small program). Also, do abuse functions/procedures and merge them to the main code (with lots of comments!) only at the very end when they're called only once (just get the xref to get the list). The thing about code being unique but called from multiple locations is a well known paradigm of "proper" databases: each piece of information is semantically unique, otherwise you'll pay that in code and data size, and each chunk of data is identified uniquely. These are base rules, but everything else derives from that, you'll think of me when you need recursivity and callbacks: pointers on lambdas are a thing...

As a self-taught toad that jumps on the fly-laden keyboard, I feel vindicated. I did this habitually because I thought I was _bad_ at coding and other coders would ridicule me. _WHO'S LAUGHING NOW!? HA HA HA HA HA! WHO'S LAUGHING NOW!?!??!?_

I cannot stress how useful having a test to document code is. I have 10 years of experience as a developer. I can't count the number of times I've been confused as to why a piece of code seems to be going out of its way to do things a certain way but there are no comments or external documentation to explain why and the person in the git blame hasn't worked for the company in 5 years. This goes one of two ways: 1. I find a unit test that explicitly tests that part of the code and all is clear. 2. I start ripping things out and fooling around with it to see how it breaks. The ✨I ✨add the unit test. The second takes *a lot* longer

One thing I tend to prefer in my code is avoiding the ! operator in if statements. Sometimes it can be missed by someone who is going through the code quickly and therefore I tend to try and make all my boolean variables describe what the condition is. Of course don't go out of your way. Sometimes a quick ! is better than an extra line of code to flip/rename a boolean.

Dont forget return statements 😂

Which language is that?

Calculate taxes should rely on polymorphism. This is a concept which I believe is no longer being taught or even understood or valued.

Writing readable code is an art and a great skill. I also think there is a lot more that could be covered here.

My first rule - keep the braces in line with each other so that the opening and closing brace is in the same column. That makes understanding the code a lot easier than if you need to chase the opening brace somewhere to the far right off screen for some odd reason. Also always brace the code that's controlled by a conditional statement.

If a piece of code isn’t significant, I feel like it isn’t a good idea to give it its own method. Comments exist for this exact purpose.

it's more about clean code trash ... and really you can't read or understand this code ... you can't be a developer if so .... the only reasons to change is: performance and business change ... otherwise it's bullshit refactor protected by clean coders and agile ....

It is useful to actually run your code. Even better if you have test cases that help you validate your refactors. In the first example you had a variable named total that I think might have been missing a definition. And then when you extracted that function you lost total all together as it was now a local.

Please correct me if I am wrong. The inverting looks good but I don't think it is that simple. In the given example, multiple conditions are needed to be checked to execute the nested code. If you are going to make it linear, you will have to use logical operators like &&, || to make sure that the condition remains same. For example: at 0:39, "user not authorized" will be logged if ( ! isMaintainancePeriod && isAuthenticatedUser && ! isAuthorizedUser ). On the other hand, at 1:21, "user not authorized" will be logged just by ( ! isAuthorizedUser ). Here, we have not made sure that isMaintainancePeriod is false and isAuthenticatedUser is true.

I've once seen a variable called qr_t_us_135_uss_t. The variabke name meant "Query result, Table, Users, Using Columns 1, 3 and 5, which are of type unsigned int, string, and string, and the whole variable is temporary". The codebase was a mess

For any complex system: "Bug free code" in itself cannot be guaranteed. Your title is very misleading. Unit Tests is not all. Your advice is misleading. Tests is the requirements we put on the system. They guarantee that those requirements are always upheld. They do not, however, ensure that your code is bug free, as you could have overlooked or forgot that further requirements also existed. As long as your thinking is not bug free, there can exist no such thing as bug free code in general. This is basis knowledge an any CS course. You should know this already.

Right, and advice like this is what makes modern software so slow. 😢 almost makes me wanna leave the industry.

I've seen untold amounts of this type of stuff in plenty of "professional" code. That last one is pretty funny too. Take a second to look at the JavaScript that Facebook serves to your browser. Not a single variable is more than 2 characters long. I'm assuming places like Facebook hire professional experienced developers. That being the case, it might stand to argue that the "professional" way to do it is to make sure nobody but you can read your code 😂

Comments, comments, comments. Tell others what you were thinking when you wrote the code.

GetUsers with for loop? You will have N database requests, what if you want to get 1000, but app is used by 1000 users at the same moment? You kill the database. You should use SELECT ... FROM ... WHERE Id IN (...ListOfIds...) Implementation of GetUsers is wrong, and because of that, whole code duplication example is wrong.

Your 'calculateTaxes' is not a function. So from the point of view of the main code, it becomes a blackbox that can be full of surprises. So it doesn't make anything clearer to have it.

Don't we want to return (exit function) in first law example, inside if statements?

You changed the functionality in the first example. The guard clauses don't return or break execution of the function so you will execute the logic always, not conditionally. I do agree with the radical application of the single responsibility principle where we extract every responsibility and level of abstraction into its own function. Also see the talk Writing Quality Code In Erlang for a great example. Language can really help to make code readable as well. For example in Clojure makes simplicity easy by providing great abstractions so that lots of boiler plate you have in other languages just disappears. E.g. the seq abstraction and extending it to java classes so that we have a few abstractions operating on hundreds of data structures.

This always made me really confused. If most of my methods connect to a database should I be doing integration tests instead of unit tests?

Pushing its limits? What are you yapping about bro

Your code theme is very beautiful. Can you tell me? Thanks

if you have used vscode your video would be shorter and more useful, for now I put a dislike for vim.

or just code rust, bc it forces you to code like that lol

All fancy and dandy, except for the fact that after applying the first two rules (which mind you, are very valid) the final code is not behaving as one in the beginning since the feature logic is used even if all the checks fails.

no 3 so far is my experiences is something i have a hard time to tolerate with some of my college buddy asking me a help sometimes , but the whole code they handed somehow have a confusing naming convention (usually single aphabets), i only looked at the code and said "i suggest you need to change the name of the variables so i can manage those easily" using single alphabets only for a loop it's fine, but for the whole code? no, please

I understand that in go an executable is generated when compiling the application, my question is what is the sense of putting that application in docker?

Sorry bro, I only made it 2 minutes in. The doo-doo-doo-doos in the background are killing me.

Watching this video I remembered collaborating with some friends on a school coding project years ago. One of my friends had a proclivity for writing very messy code, using variable names like "habbababa". I asked her on that occasion why on earth she would name a variable like that - and reportedly, "habbababa" sounded "kind of cute". I still find it hilarious up to this day.

Even if all imaginable checks are performed, there is no theory, nor metric, nor tool, and particularly no "laws", that can tell us how many important bugs remain. We must test - experiment in an exploratory way - in order to have a chance of finding them. No one can know in advance where the unanticipated bugs will be and therefore what scripts to write. Not denying the value and importance of unit tests, but there are not a silver bullet against bugs in the code as you suggest by the title of your video.