Modern testing for modern stacks

We have gotten into the habit of thinking deeper about one topic on a weekly basis. We pick topics based on anything interesting we read - so the topics can range from 'how to express the value of testing' to 'Dieter Rams' design principles' to 'effective remote work habits'. Employees are guided to spend no more than one hour researching the topic online. The emphasis is on coming up with their own ideas and interpretations. We then meet as a group to exchange ideas. I love this habit and consider it one of the more unique benefits you will enjoy at Qxf2.

Topic: Invite your engineers to talk business

13-Jun-2017

This piece that ties code and business goals. It also does a good job of explaining why it is ok to have bugs in early stage software.

References:
https://about.gitlab.com/2017/03/07/your-engineers-need-to-understand-your-business-heres-why/

Our thoughts

Avinash

The dependency on technology is increasing for every business that's the reason why engineers need to be involved more in business talks. In a startup world as a developer or tester, you need to be ok with the technical depth. You may find places where you can do more to improve quality but you need to consider the business angle also and prioritise your work accordingly.

Annapoorani

As the author mentioned every business has become the technology business.Engineering goals are now closer than ever to business goals so understanding that will help companies thrive in the business technology world today. So nowadays it's important that communication and alignment between engineers and business people are very important. As technology gives the direct impact of business, so code quality is important. As we all know to add new features to our existing code, changing the existing features etc....But we shouldn't skimp our code to complete fast or shouldn't take a long time also. Because both will affect your business.

Smitha

I agree with this article. I was thinking if engineers were involved in business discussions in the corporate world too then how would it have been? I agree that both parties should work together in this competitive world. Engineers should elaborate the practical benefits which can become good business requirements.I have seen the tech debt where quality was poor, so you want to clean up every time but you never get there.

Shiva

A nice article that emphasizes code quality in a business perspective, it gives a reason for engineers to participate in business meetings. With better quality a few important business goals can be achieved. It helps in scaling up as it is easy to add or remove a feature with little hassle. Including engineers in business communications helps to come up with attainable business and engineering goals where features can be chosen or ignored at the plannign stages.

Rohan Joshi

It was a good article to read. I liked the phrase Engineering goals are business goals. From my previous company experience, I have seen the technical team was taking part while taking business decisions. I was given information about how ecommerce business models work and how our software is making the life of online seller easier. Which helped me during testing of the product, answering enterprise team queries and API integration queries since we were dependent on ecommerce platforms. If they change any scenario in their product we also had to do some changes. Other things which I agree with author is that he says that if you choose to maintain 100 percent quality code you tend to loose some business. So if your engineer knows the business models, he can add quality features quickly covering all the business scenarios which can happen.

paper cut