Top Insights from the 2016 Google I/O Keynote
The 2016 Google I/O Conference proved Google's commitment to providing solutions that continue to blend technology into users' daily lives. As in recent years, Google presented new technology offerings with the intent of giving developers access and the ability to continue improving products in an open environment. With their visions seemingly driven by artificial intelligence and machine learning, Google's announcements this year showed a continued push for powerful computing and connectivity that is universally accessible.
Addressing the Issue of Diversity in Tech: Overcoming Inclusion Barriers
Our previous post, Addressing the Issue of Diversity in Tech, explained the benefits of diversity in the tech space. The bottom line: businesses gain a competitive advantage by employing diverse teams to create solutions. A study by Harvard Business Review cited in our previous post reads:
Front-End Development for Sitecore
When developing HTML for a site that will be implemented in Sitecore's cutting-edge CMS, it's vital to develop code with extensibility, personalization and responsiveness in mind. This will facilitate the creation of a site that enables both developers and marketers to work effectively.
Addressing the Issue of Diversity in Tech
It's no secret that gender and racial diversity are prominent issues in the tech industry. While women comprise roughly half of the workforce in the U.S., they represent only 20 percent of software developers. Even more astonishingly, only 4 percent of software developers in the U.S. are African-American and 5 percent are Hispanic. Whether it’s a selection bias or an issue of resource availability, the fact remains that the technology industry suffers from a severe lack of diversity.
Slack Time: the Nature of the Beast
As a Project Manager of an Agile team, my role is to not only make sure my team has what they need to reach an established goal, but also manage the timing of the project itself. In order to plan effectively, I try to anticipate the unexpected, but it's inevitable that at least one thing goes awry. Worse, sometimes something I didn't plan for actually happens. "Slack time" falls into the latter category, and I have learned that utilizing slack time as a valuable tool keeps the project flowing during times of imbalance.
Agile isn't Broken
We worked on a project where a senior engineer was convinced that the select system call was broken on Solaris. No amount of persuasion or logic could change his mind (the fact that every other networking application on the box worked fine was irrelevant). He spent weeks writing workarounds, which, for some odd reason, didn't seem to fix the problem. When finally forced to sit down and read the documentation on select, he discovered the problem and corrected it in a matter of minutes. We now use the phrase "select is broken" as a gentle reminder whenever one of us starts blaming the system for a fault that is likely to be our own.