Skip to content

Tag: Code Review

Update Statements on Production

Executing update statements on a production database is always a big challenge. I have seen three different prominent incidents due to update problems. In each one of the incidents, multiple factors lead to the incident. We could have avoided these problems by a couple of preventive actions.  Before Running Update Statements One of the causes for update statement incidents is overconfidence or lack of meaningful process. Engineers…

Leave a Comment

Essential Engineering Principles

Engineering principles make a software company identity. Principles guide engineering teams to deliver business outcomes at scale. They are blueprints to actions and behaviors. Engineering leaders can lean on these principles to establish guidelines for good behaviors and actions. Although engineering principles differ from one organization to another, organizations can apply the following principles. Ship Frequently Delivering value depends on the agility of the team. We deliver…

Leave a Comment

How I Work as a Software Engineer

Learning is very big part of software development because technology advances very rapidly. Swift changes create new knowledge to acquire though we also have a lot to learn anyway. As a result, we constantly try to learn software development through books, articles, posts, conferences and videos. We all want to find out what are the best ways to do our job. Nevertheless, applying theory to practice isn’t…

Leave a Comment

Shoulder Ship It

Pair programming is no new topic and has been widely used in the industry. At first, it might seem like it’s waste of time because two coders work in the same station. However, it provides values like team building and less defective code. Although code reviews provide a degree of control in written code piece, a second person makes sure hopefully nothing is gone off the road.…

Leave a Comment

A guide for Code Reviews

CR Submission Guidelines Keep your CR focussed. If possible send CR per feature. If the feature is big then divide feature into multiple CRs focussed on different aspects. For example, “user history feature” may require database access and user interface. So, you might send a CR covering two aspects. Lastly, send divided feature request ground up e.g. send database access before user interface. Make sure that your…

Leave a Comment