Nov. 29, 2015
Julia likes to get some idea how unit test can be done as a developer, and also in C++. She likes to adventure out and see if she can get ideas how to build up good habit to do unit test.
Notes
from video:
Less
code = More Software
Let
Julia read those sentences and laugh about mistakes she made as well:
1.
Complexity is one of the biggest problems with software if not THE biggest.
2. It is
much easier to create a complicated "solution" than to really solve a
problem.
3. Much
software complexity is accidental not inherent to the problem solved.
4. It
starts in the small, one statement at a time.
5.
Architects and developers need to value Simplicity!
.
Good Abstractions are the key, as are
.
Managing Dependencies (Avoid global variables)
6.
Software needs to be simpler to solve more complex problems.
7.
Simple software requires work and skill but pays off in the long run.
(4:06/5:49)
Quotes by Sir C.A.R.
(Tony) Hoare (quick sort algorithm inventer in 1959/1960)
"Inside
every large problem, there is a small problem trying to get out."
Bad design vs good way:
one way is to make it simple that there are no obviously no deficiencies, and
the other way is
to
make it so complicated that there are no obvious deficiencies.
The first methods is far more difficult
C++ test-driven development
Another
video watched in Sunday evening:
CppCon
2014: Titus Winters "The Philosophy of Google's C++ code"
4k-ish C++ engineers in
Google
CppCon 2015: Bjarne Stroustrup “Writing
Good C++14”
CppCon 2015: Herb Sutter "Writing
Good C++14... By Default" ( Julia rating: A+, Nov. 30, 10:00-11:11pm)
https://www.youtube.com/watch?v=hEx5DNLWGgA
CppCon 2015: Sean Parent "Better
Code: Data Structures"
No comments:
Post a Comment