Going through my bachelors degree in computer science, the more and more i think about where I stand in this entire web of systems it’s more and more into a communication position but I know communication in computer science? o no that never happens it’s all about creating algorithms all day long? Right? Well that was one of my original thoughts when I first heavily got into coding, now after hard learned lessons I am starting to see that some of the most important parts of software and software development has as much to do with communication than in actual code.
Let me explain, their seems to be this train of thought out through this profession that all software projects are delivered late and have to be reworked after first cycle of development, but it does not stop their. The wrong product gets built, schedules are blown programmers are angry and everyone just does not have a clue of what to do with this system that got built from 9 different ways from hell.
What if instead of building the wrong thing, the right requirements where met when the first project was asked to be built? What if the right product actually got built? I know, I know agile, agile will save us all! But will it really? One major part in any software project goes back to the entire communication on the product that is getting built and the processes that are used to create the product, and this can determine the success of the project over to it’s failure.
Coming back to learning more about software requirements, that requires the ability to be able to understand the industry, the product, the persons involved, unspoken words, lets just say it diverges into “communication”.
I always had a passion for the field of STEM (Science, Technology, Engineering, and Math) and I knew I wanted to do something to make a difference in the world. I just didn’t know where to start. I was an immigrant in a new country, grew up in a tough environment, and wasn’t sure how… Read More
