https://unsplash.com/photos/XT-o5O458as

As makers, we’re always looking for creative new ways to keep our minds sharp and skills relevant. We live in an age where a vast sea of information is available at our fingertips. In this knowledge economy, information is king. When you take a step back to consider the possibilities this creates for personal and societal growth, it’s really quite inspiring.

But what are the ramifications of such boundless access to information?

The JavaScript community has been in a state of fatigue for some time due to constant changes in tooling, libraries and abstractions that seem to be popping up…


When you think of a good user story, you might imagine clear, succinct definitions of features that address real user needs and provide solid business value. They are the PO’s breakdown and representation of where the business needs to grow to keep customers happy and ensure future success.

While this is very meaningful from a business perspective, I find that writing user stories in this way ensures that they are only meaningful to the business. The focus, terminology and scope is directed at a single audience — those that wrote the stories in the first place.

This often causes issues…


Habitual Testing: Transform Negative Software Testing Culture By Leveraging Your Subconscious

I think we can all agree that testing code is valuable.

Well tested code assures the completion of acceptance criteria, guiding implementation by outlined requirements. It empowers you to extend and refactor with a sense of safety, knowing that existing functionality won’t break as a result of your changes. Over time, your team gains increasing returns as the growing number of tests reduce the likelihood of surprising, hard-to-diagnose bugs appearing and derailing production software, often coming at a cost of significantly more time than it took to write the tests in the first place. Not to mention, this increased quality…


Photo by Andrew Neel on Unsplash

When I was first exposed to Scrum, I fell in love.

The process was straight forward. The team agrees on a prioritized list of tasks to complete in a consistent block of time. A sprint. You meet daily to touch base, ensuring everything is on track. By the time the sprint is complete, some product functionality has been shipped. The client is happy. Finally, you regroup for a retrospective, discussing what went well and what went poorly. Then you start all over again. It just made sense.

I’ve been fortunate enough to come across some great opportunities throughout my career…

Igor Barsi

Breaking the web, one coffee-less commit at a time ☕️

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store