I started working with Barry at a pivotal time in our company's history. Reflektive had gone through several years of rapid development, minor pivots, and developer turnover. We brought Barry on to help revitalize our UI, and inject some energy into our demoralized frontend team. I got to see Barry work in many different scenarios - highs, lows, small projects, refactors, overhauls, people management, etc. And in all situations, Barry impressed me and those around him. Barry's naturally got all of the qualities of a player-coach. That is, he can come up with a solution to a problem, big or small, and lead the way on implementing it. It's an underrated skill that goes beyond just delegating - Barry can plan, communicate, delegate, and mentor so that a team can complete a project successfully and efficiently. His ability to straddle the line between architecting and implementing inspires confidence in those around him. I saw the same pattern emerge in many of the projects that he and I worked on together, both small and large. I'm not the only one who recognized these strengths - many of his peers have praised him for them as well. Aside from technical skills, Barry was a personable coworker with a high EQ. As a founder, I was often faced with unique problems, or difficult decisions, that I would discuss with others to get their advice. There are few people whose insights I respect more than Barry. Barry is always willing to lend an ear, and puts a lot of thought into his advice and feedback. Similar to my role, Barry's position as a Director of Engineering at Reflektive often came with it's own unique set of non-technical challenges. Barry was responsible for managing many developers and relationships within the R&D department. Any developer-turned-manager can tell you, people management is a far more complex problem than software engineering. This is another area where Barry's calm and collected personality shone through. He was able to remediate any sort of conflict, whether it was a small difference in opinion on coding conventions, or a larger clash of personalities. And most importantly, he'd often seek advice from others on how to go about it. In those cases, he always took that advice to heart and applied it to his management strategy. Barry's addition to the team was a total game changer at Reflektive. He's a keystone that can support an entire dev shop, whether it's already in place, or has yet to be built. He brought confidence to the engineers around him and to the company at large. He was invaluable at Reflektive - I would jump at the opportunity to work with him again.

Barry was one of the most impactful engineering leaders at Reflektive. Outside of my cofounders, he quickly became my go to guy on the engineering team when I was trying to solve tough problems that required out of the box solutions. I’d hire him again in a heartbeat, and probably will try to at some point in the future.

I started working with Barry at a pivotal time in our company's history. Reflektive had gone through several years of rapid development, minor pivots, and developer turnover. We brought Barry on to help revitalize our UI, and inject some energy into our demoralized frontend team. I got to see Barry work in many different scenarios - highs, lows, small projects, refactors, overhauls, people management, etc. And in all situations, Barry impressed me and those around him. Barry's naturally got all of the qualities of a player-coach. That is, he can come up with a solution to a problem, big or small, and lead the way on implementing it. It's an underrated skill that goes beyond just delegating - Barry can plan, communicate, delegate, and mentor so that a team can complete a project successfully and efficiently. His ability to straddle the line between architecting and implementing inspires confidence in those around him. I saw the same pattern emerge in many of the projects that he and I worked on together, both small and large. I'm not the only one who recognized these strengths - many of his peers have praised him for them as well. Aside from technical skills, Barry was a personable coworker with a high EQ. As a founder, I was often faced with unique problems, or difficult decisions, that I would discuss with others to get their advice. There are few people whose insights I respect more than Barry. Barry is always willing to lend an ear, and puts a lot of thought into his advice and feedback. Similar to my role, Barry's position as a Director of Engineering at Reflektive often came with it's own unique set of non-technical challenges. Barry was responsible for managing many developers and relationships within the R&D department. Any developer-turned-manager can tell you, people management is a far more complex problem than software engineering. This is another area where Barry's calm and collected personality shone through. He was able to remediate any sort of conflict, whether it was a small difference in opinion on coding conventions, or a larger clash of personalities. And most importantly, he'd often seek advice from others on how to go about it. In those cases, he always took that advice to heart and applied it to his management strategy. Barry's addition to the team was a total game changer at Reflektive. He's a keystone that can support an entire dev shop, whether it's already in place, or has yet to be built. He brought confidence to the engineers around him and to the company at large. He was invaluable at Reflektive - I would jump at the opportunity to work with him again.

Barry was one of the most impactful engineering leaders at Reflektive. Outside of my cofounders, he quickly became my go to guy on the engineering team when I was trying to solve tough problems that required out of the box solutions. I’d hire him again in a heartbeat, and probably will try to at some point in the future.

I started working with Barry at a pivotal time in our company's history. Reflektive had gone through several years of rapid development, minor pivots, and developer turnover. We brought Barry on to help revitalize our UI, and inject some energy into our demoralized frontend team. I got to see Barry work in many different scenarios - highs, lows, small projects, refactors, overhauls, people management, etc. And in all situations, Barry impressed me and those around him. Barry's naturally got all of the qualities of a player-coach. That is, he can come up with a solution to a problem, big or small, and lead the way on implementing it. It's an underrated skill that goes beyond just delegating - Barry can plan, communicate, delegate, and mentor so that a team can complete a project successfully and efficiently. His ability to straddle the line between architecting and implementing inspires confidence in those around him. I saw the same pattern emerge in many of the projects that he and I worked on together, both small and large. I'm not the only one who recognized these strengths - many of his peers have praised him for them as well. Aside from technical skills, Barry was a personable coworker with a high EQ. As a founder, I was often faced with unique problems, or difficult decisions, that I would discuss with others to get their advice. There are few people whose insights I respect more than Barry. Barry is always willing to lend an ear, and puts a lot of thought into his advice and feedback. Similar to my role, Barry's position as a Director of Engineering at Reflektive often came with it's own unique set of non-technical challenges. Barry was responsible for managing many developers and relationships within the R&D department. Any developer-turned-manager can tell you, people management is a far more complex problem than software engineering. This is another area where Barry's calm and collected personality shone through. He was able to remediate any sort of conflict, whether it was a small difference in opinion on coding conventions, or a larger clash of personalities. And most importantly, he'd often seek advice from others on how to go about it. In those cases, he always took that advice to heart and applied it to his management strategy. Barry's addition to the team was a total game changer at Reflektive. He's a keystone that can support an entire dev shop, whether it's already in place, or has yet to be built. He brought confidence to the engineers around him and to the company at large. He was invaluable at Reflektive - I would jump at the opportunity to work with him again.

Barry was one of the most impactful engineering leaders at Reflektive. Outside of my cofounders, he quickly became my go to guy on the engineering team when I was trying to solve tough problems that required out of the box solutions. I’d hire him again in a heartbeat, and probably will try to at some point in the future.