It is with unbelievable excitement that we are officially announcing the opening of our third global branch with a Dell EMC Dojo in Bangalore! By sharing our DevOps and Xtreme programming culture, including but not exclusive to the practices of pair programming, test driven development and lean product development at scale, we have the deepest confidence that Bangalore is the geographical mecca that sets the tone of Digital Transformation we hope for in the larger company.
So what does this mean beyond the logistical rollercoaster that comes with opening a new office? Well, I’m glad you asked!
We are Hiring! Over the next few weeks, we will be rapidly and qualitatively (only because how else would we operate?) looking for and interviewing developers and product managers interested in becoming a part of this exciting new Dojo from its inception. So, if you know of anyone in the area that may be interested, please point them in the direction of Sarv Saravanan (email@example.com) who will be handling the process on the ground.
Otherwise, stay tuned on our team’s impending growth, engagement (both here and in India), and overall adventure!
I work on a team where we practice ‘pairing’ and pair programming every day. Before joining this team I had only a passing experience with pair programming. And now, after many months of pairing, I have a much better understanding of why we pair.
Pair Programming Explained Pair programming is a technique in which 2 programmers work as a pair at one workstation. One, the driver writes code and focuses on the tactical aspects of syntax and task completion. Two, the observer considers the strategic direction of the code they’re writing together. In our case, each developer has their own monitor, keyboard and mouse but is connected to one IDE. The two programmers switch roles often.
The opinions and interests expressed on Dell EMC employee blogs are the employees' own and do not necessarily represent Dell EMC's positions, strategies or views. Dell EMC makes no representation or warranties about employee blogs or the accuracy or reliability of such blogs. When you access employee blogs, even though they may contain the Dell EMC logo and content regarding Dell EMC products and services, employee blogs are independent of Dell EMC and Dell EMC does not control their content or operation. In addition, a link to a blog does not mean that EMC endorses that blog or has responsibility for its content or use.