Course code: WEB-21
Years with company:
Primary programming language:
Other programming languages:
C, bash, perl, python
Unit test harnesses:
I like listening old songs, watching movies.
Test practice now:
using GTEST framework
arm, x86_64, x86_32
GCC, KPIT proprietary toolchain, Eclipse, cpplint, clang-format
Organization Copyright info
Appropriate Header Guards
namespace enclosed code
Camel-case type names
Class name start with Caps Letter
member starts with m_*
Function too long:
is more than 20 line
is doing multiple thing other than its name ?
is having huge nested if-else chain ?
is coding standards followed?
is code scalable?
is commented code present?
is code optimized ?
is proper breakdown to smaller reusable Classes/Function ?
is it responsibility reflected in name ?
is code readable and maintainable ?
Favorite thing about dev:
It is like making dead/non-living things alive.
I like step by step debugging
I like analysis of bugs, they teach a lot
Least favorite thing about dev:
design of system, class diagram, documentation
it is method where unit tests are written first before start the implementation itself. primarily all tests can be fail, but it will get passing as we write the code.
Why are you attending:
I am curious about what are benefits of TDD ?
I have wasted(actually invested) lots of time in fixing bugs and rework in the code which was written/reviewed by myself.
As per information I read about TDD it will save these things.