How to Write Clean, Testable Code
HTML-код
- Опубликовано: 4 авг 2024
- Google Tech Talks
December 15, 2010
Presented by Miško Hevery.
ABSTRACT
The Clean Code Talks are designed to help teams get better at writing clean, well-designed, testable code. Such code is easier to write tests for, more robust, easier to understand and maintain. Having clean code lets you be more productive. It helps you release more often, with more robustness, more confidence, and fewer rollbacks.
Miško Hevery works as an Engineer at Google where he is responsible for coaching Googlers to maintain the high level of automated testing culture. This allows Google to do frequent releases of its web applications with consistent high quality. Previously he worked at Adobe, Sun Microsystems, Intel, and Xerox (to name a few), where he became an expert in building web applications in web related technologies such as Java, JavaScript, Flex and ActionScript. He is well published and very involved in Open Source community and an author of several open source projects, most recently angular.
This Tech Talk was presented at one of the Google NYC Tech Talk series. For more information, or to attend future events at the Google NYC Engineering Office, see www.meetup.com/google-nyc-tech... 
Наука
Good talk on writing testable code. Shame the Q&A section is inaudible. :-(
Great talk. Misko is the man. Got here via a Kent Beck's tweet, btw.
Look like my wishes has been granted and GTT is in HD now :). Thank you,
Very good talk. Well explained and demonstrated.
10x
It would've been better if we'd been able to hear the questions the audience asked. He could've repeated the question before answering it for our benefit.
+Даниел Русев Yeah, that would be a good habit, rarely used , tough
Holy Crap this is straight 🔥 My code dead ass is unstoppable 💪🧑🏽💻🧑🏽💻🧑🏽💻🧑🏽💻🧑🏽💻 THANK YOU FOR THIS 😍😍
Thank you, this made a lot of vague ideas concrete for me. Good example code, great discussion.
great talk
Am I right in thinking that the reason 'new' operators are bad is because you can't change the type of the object from outside?
Please repeat the questions!
Thanx, just removed the NEW from my convert function.
Public Shared Widening Operator CType(m As Meter) As Millimeter
Return Convert(New Millimeter(UnitValue), m)
End Operator
@sharperguy (Disclaimer: I'm no OO guru and could be completely wrong ;p.) New is bad inside of constructors because that hard codes dependencies and is usually a sign that the constructor is doing too much. For example, if you have a User class with something like "new DatabaseConnection();" that's obviously bad as instantiating a database connection is not the business of a User object.
@devent82 Now, Yes in Lion
Go into Google and explain how to properly write code? Cool! For my next act, head in the Lion's mouth. lol ... anyways. .... Great talk even for the non-professional programmer. Now my question.... General engineering project management identifies the concept of "a metric" if you view the code as a project how do you relate the concepts of metric and specs? or are they unrelated?
shwag
After one hour, they give the mic to the audience so the questions can be understood.... They need to improver their presentation better practices if they plan to upload them to youtube!!
WTF is frosting? Oh, right, *icing*.
subtitles are a bit off.
BDB actually is BDD, business driven development.
I thought it was behaviour driven development?
en.wikipedia.org/wiki/Business-driven_development
nl.wikipedia.org/wiki/Behaviour_Driven_Development
Kosteri x hi what about what he's talking about around 43mins, a single threaded test ... app/framework (not sure)
sounds like 'no-jays'?
@@jonnyhotchkiss2667 NodeJs. Also note that Misko is one of the developers of AngularJs
It's crazy how much have changed after 12 years
great talk, but to silent voice and title isnt sinc.
The URL with the code is invalid. :(
That's an oh not a zero. 92Ozrz
I have no idea what's been said here either.
If you are going to tell us it is okay to say "I don't know" three times in the presentation, maybe you should take your own advice and admit that *you* don't know when people ask questions that you can't answer.
On the contrary, it is shameful to say that you DO know Javascript