Since last week I have been working on improvements in a login feature.
I have crashed this feature so many times in the past one month , now I am scared to make any further changes.
I realise that management has a very high level of intolerance for crash in software. They are ok if you deliver one line of code with 20 bugs. But 200 lines of quality code with 2 crashes will make them shiver.
I think learning functional testing is more important and more difficult than learning to code.
If I can write very good functional tests I would never be scared that my code is not working.
This is the next level of programming that I want to achieve now.
I have seen this level in senior programmers of Avaya, for every feature they write they create automation tests which ensure that their feature works as expected.
I have crashed this feature so many times in the past one month , now I am scared to make any further changes.
I realise that management has a very high level of intolerance for crash in software. They are ok if you deliver one line of code with 20 bugs. But 200 lines of quality code with 2 crashes will make them shiver.
I think learning functional testing is more important and more difficult than learning to code.
If I can write very good functional tests I would never be scared that my code is not working.
This is the next level of programming that I want to achieve now.
I have seen this level in senior programmers of Avaya, for every feature they write they create automation tests which ensure that their feature works as expected.
How is the learning journey going? Do share your thoughts on this and more.
ReplyDelete