Writing testable code is a harder target to achieve than just writing tests for the code written. You cannot write comprehensive tests that covers many function each of 200 or more lines and classes that measure 1000s of lines of code (
LOC). Writing testable code is always important if you want to be able to test/unit test your code and be confident that nothing will break.
Tests also help a lot when you re-factor some code or write new features. If all the tests are passing you are quite sure that nothing is breaking. Seeing all tests come out green is a very good sight for us software engineer.
Love it or hate it, the fact is 80% of the web is PHP and its usage has been in an increasing trend since 2010. Be informed that PHP is much better than you think as per Fabien Potencier. As a team, we have worked a lot on PHP this year, specifically on Symfony 2 mainly for our back...
I started my programming career as a software engineer/developer from a dev shop (I can't find the right term for it, call it a dev shop, web agency, software house or web company anything that makes sense to you. Basically a agency/company that takes up projects to survive and grow). It was a smal...
I am always in a hunt for good applications that will simplify how I execute things and ultimately enhance my productivity. In the past year the need to be more productive and efficient has been greater due to added responsibility and a new environment to adapt to. Here I will ...
Git is a free & open source, distributed version control system which can be used for projects of any size and complexity. I have been using git for more than past 2 and half years, you can even see my github and I find git essential for most of the projects I have been involved in. If t...
More posts can be found in the archive.
