Comment Initial Inheritor with airSlate SignNow

Move esigning understanding

good afternoon good afternoon everyone this is algorithms this is ranges this is all excellent code from the library and the compiler definitely understands it but the question is does anyone else my name is David Saxton I'm an independent consultant developer and instructor I work with C plus plus and with other languages and I'm passionate about writing clean code so this is the topic of my talk today let's begin with a little discussion about the standard Library so the implementation of the STL or the standard library in general and has apis that are extremely well designed thoroughly reviewed the apis are consistent and they are compatible over many different platforms compilers and Hardware platforms they are as efficient as possible and they actually do comply with many or maybe even all of the core guidelines of course EDP guidelines however classes and functions in the library are generally very long the cyclomatic complexity of many of the functions is very high cyclomatic complexity refers to the number of different paths that execution can flow through a function when their complexity is high it makes it more difficult to reason about and more difficult to test header files are very long Chrono has almost 6 000 lines algorithm has over nine thousand they make excessive use of macros and compilation Flags and some of the code is very repetitive so we really have a dilemma here when I speak to people about clean codes and how important it is people say well I write like the library does big functions long-headed files everything works so I need to resolve this problem people tell me we don't need clean code it's not something that we apply to the code that we write today and um I think we need to understand that clean code means different things in different contexts and in most the contexts that we find ourselves writing code clean code is very important so what I'd like to do today is first of all discuss just a little bit um about clean coding context to understand a little bit more about the pressures involved in making something clean and the benefits but immediately following I would like to introduce you to what I consider the basics of best practices for C plus plus programming this is not going to be the main part of the talk because there are many many details and I just want to give an outline so one slide will be enough the main part of the talk will be to develop an application a very small application that I built for this talk which will be developed from step to step I'll take a few wrong turns and clean up what I've done and along the way I expect to be able to learn a few lessons and give a few tips and towards the end we will be able to summarize and I'll be able to summarize those tips...