Breaking The Ice With RTC
I recently began working part-time with TechRev as a Jr. Software Engineer while pursuing my Bachelor’s Degree. As my first assignment, I have been tasked to work on IBM’s Rational Team Concert (RTC), a software development team collaboration tool. Actually, my entire job for the past three weeks has been living and breathing RTC—watching countless tutorials and reading threads. My project goal is to create unique tools and features that RTC does not natively support. The components that I will create will allow for a more flexible experience for RTC users and enhance the ability to interact with RTC. After all this research, I have a good grasp on the power of RTC.
RTC provides users with a vast array of features including repository, source code control, integrated bug tracking, a WEB UI and even an Eclipse UI. These interfaces are the real charm of RTC, as they offer an easy way for users to manage their team and collaborate their source control with ease.
As I read and worked on RTC, I was under the impression that this program was similar to GitHub. While RTC does provide some similar functionality as Git, it’s capabilities goes beyond those of GitHub. RTC allows for team members to have roles in their project, it also has “work items” to keep track of team members responsibilities throughout the project's life cycle. In short, RTC is for team/project development, while GitHub is mainly used for open sourcing software. RTC can be used for more than just holding source code, it can be used for any type of team collaboration project.
In this modern times of application development many of the user interfaces are presented through a browser. Testing of an application is often a tedious and repetitive, but necessary, activity. Automation lends a helping hand in the repetitive aspects of testing, but what tool to use?
In my Talent Acquisition (fancy word for recruiting) endeavors, a potential candidate asked the following question: What is the culture of TechRev? Good question candidate, good question. It was a hard question to answer for 3 reasons…
Launching a new company website is a daunting task on any level. There are so many variables – so many things to consider. Outsource or in-house creation? Who writes the content? What framework to use? Where to host? Do we even need a new site?