Posts

Showing posts from 2015

My Learning Angular as a Backend Engineer - first time

Recently I wanted to try hot new framework called AngularJS. As someone who's spent years writing backend APIs, I thought - hey, maybe it's time to see whateveryone is talking about (in Frontend)  So I decided to write down some key points and insights from my experience of learnig into AngularJS. Coming from a backend world where everything is neat code and database queries, my first reaction was like "Whoo, what's all this DOM manipulation stuff?!" Before AngularJS, I had used some jQuery and writing tons of JavaScript to update few webpages. But then AngularJS comes along and changes everything we did. Some cool things I found while learning: Two-way data binding is amaaazing! Just add ng-model to an input and boom - my JavaScript object updates automatically. No more manual DOM updates! When I first saw this working I was like "why didn't we have this before?!" Directives are pretty neat. At first they looked sca...

Test-Driven Development

I’ve tried practicing Test Driven Development (TDD) for so many different developments. Test-Driven Development (TDD) has gained popularity among developers as a methodology to improve code quality and design. However, my early experiences with TDD left me feeling overwhelmed and burdened by the tests themselves. Determined to unlock the true potential of TDD, I embarked on a journey to master this development approach. Through numerous struggles and enlightening discoveries, I have gained a deeper understanding of TDD. In this blog post, I will share my insights and the importance of grasping the TDD life-cycle for effective development. The TDD Life-Cycle: Write the test: TDD begins with writing a test that reflects the functionality you wish to implement. This test initially fails, as there is no corresponding implementation code. Run the test (test does not pass): Running the test at this stage will inevitably result in failure, given...

Interviewing Programmers

Hello my dear senior friends in SW engineering , how do  you interview new recruits for programming ?Do you start with phone interview and continue on written tests to face-to-face interview? Eventually it will come down to your experience and gut feeling? Most of times we do it in that way. But we have experienced some best practices of picking "better" programmers! In an environment like work we need more “practical programmers” than just “good coders”. Because most of times our programmers will need to directly work with end user and understand the requirement from business perspective. So we have more responsibility to choose “right” people from interviews. We take advantage of intern programs, we hunt down the smart CS/IT students and individually ask them to apply for an internship with us, because if you wait around to see who sends you a resume, you're already missing out. In one incident tried asking applicant to develop a program, I have used a very genera...