Skip to content

Commit

Permalink
Updated The Hybrids Are Coming A Survival Guide
Browse files Browse the repository at this point in the history
  • Loading branch information
kclark-scottlogic authored and Siteleaf committed Oct 2, 2023
1 parent 573144f commit a361201
Showing 1 changed file with 10 additions and 6 deletions.
16 changes: 10 additions & 6 deletions _drafts/the-hybrids-are-coming-a-survival-guide.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -14,24 +14,28 @@ How does it help the team?

What can be gained from becoming a hybrid?

This blog is a list of reasons why being a dev-test hybrid (the term I have coined, not official) might help you and your team so let's begin.
This blog is a list of reasons why being a *dev-test hybrid* (the term I have coined, not official) might help you and your team so let's begin.

###1, Communication
On a project one of the main things we as a team do is...you guessed it communicate. Being able to have honest conversations can help with collaboration. For example, a tester with coding knowledge can help cut through the tech talk and get right to the point. It can help developers understand what a tester is talking about when they run through scenarios so everyone understands what is happening.
On a project one of the main things we as a team do is...you guessed it...communicate. Being able to have honest conversations can help with collaboration. For example, a tester with coding knowledge can help cut through the tech talk and get right to the point. It can help developers understand what a tester is talking about when they run through scenarios so everyone understands what is happening.

###2, Ability to participate in reviews
Reviews are a key part of the development cycle and for getting tickets across the line. Having developers take part in test reviews and testers review developer code can allow for many different perceptions to come together and can find issues that may have slipped through the cracks. Reviews are also a great way and place to showcase skills and a great way to contribute to the team.
Reviews are a key part of the development cycle and for getting tickets across the line. Having developers take part in test reviews and testers review developer code can allow for many different perceptions to come together and can find issues that may have slipped through the cracks. Resulting in a more robust and optimized code base.

Reviews are also a great way and place to showcase skills and a great way to contribute to the team.

###3, Understanding technologies
Having knowledge of both pools can give a person some perspective. This can link up to the first point as it allows a common language between disciplines. For testers understand the technology can look like not writing tests which are based on wrong assumptions. Having knowledge on technologies can also help on a project to project basis as well as for a tester it can look like a similar issue. For developers understanding the tech can be knowing how tests run and knowing how to update them when they make small changes.

###4, Understanding logic
Knowing what something does is different to knowing why it is doing it. So this point is going to look at how by understanding logic testers and developers can come to an agreement that suits them and helps the project. By understanding logic we can see how a person thinks and when we see how a person thinks we can understand what they do. In the case of code this can be
Knowing what something does is different to knowing why it is doing it. So this point is going to look at how by understanding logic testers and developers can come to an agreement that suits them and helps the project. By understanding logic we can see how a person thinks and when we see how a person thinks we can understand what they are doing. In the case of code this can be if a developer writes a section of code that at first looks intimating but when you look at it through the developers eyes you can see there may be reason to their madness which actually makes sense when solving a problem in a thinking outside the box sort of way.

###5, Narrow down defects
This point is more aimed toward the testers reading this. Having code knowledge is immensely useful as it can help you generate useful details. Viewing the code in a different light can let you see defects in relation to the code. This means you can have better conversations with your developers and hone in on where defects might be coming from with ease. For the developers this will make their lives easier as they

###Conclusion
In conclusion
In conclusion being a dev-test hybrid can only bring good things to you and your team. New skills, Better communication, Better code. All the things you can want and more for your project. As time goes on hybrid testers especially are more and more common and it might be that the manual tester is a thing of the past a few years down the line.

Piqued your interest in the other field have I?

Piqued your interest in the other field have I? Well, there are several ways to upskill if that is what you wish. Talking to your friendly neighborhood developer/tester (often seen roaming around near the coffee machine) is a start, see how they view the world (project). Getting involved in communities of practice and learning from others is great. Also, the internet is a great source of information.
Well, there are several ways to upskill if that is what you wish. Talking to your friendly neighborhood developer/tester (often seen roaming around near the coffee machine) is a great start, let's you see how they view the world I mean project. Getting involved in communities of practice and learning from others is another way. Also, the internet is a great source of information.

0 comments on commit a361201

Please sign in to comment.