Here’s a stat from Google that’ll make you sit up in your chair: 27% of internet users are using voice search on mobile.
Voice search is on the up. And If you’ve read our previous post predicting what may happen in the future of voice technology, you’ll know that we’re pretty excited about the possibilities.
But there are plenty of situations where voice search can create challenges for users, as well as your business. That’s why it’s important to evaluate the risk/benefit relationship voice search presents for your organization and then truly define your product before you dive in.
This pandemic has forced us to experience a period of many changes in our life dynamics. Social distance has impacted almost all areas of our lives, especially how we relate to work. The famous Home office, or telework, which was once considered a privilege or an innovative work model, has now become a reality for many companies, especially in the IT sector.
However, there is a big difference between adopting this work model as a conscious and planned choice – when one is able to exercise social activities in other environments -, and the model forced by the pandemic, one which implies social distance and ends up limiting most of our social interactions to interactions that can only be mediated by technology.
Over the years, innovation has stopped being a buzzword and become a necessity for any company, mainly due to the current context. But even in times when talking about innovation is no longer a differential, a perception that it is a very wide universe with several possibilities still remains. Continue Reading
Innovation matters. It is determinant for organizational growth and consequently to the products that we are building.
Having said that, when it comes down to exploring new opportunities that could lead us to innovation, the way we build and tell these stories can lead us to success (or not). But why isn’t that so easy? Because we are programmed with many behavioral mechanisms that prevent us from acting. To briefly illustrate, one of these behavioral mechanisms is the so-called “negativity bias.” Continue Reading
Hello developer, how are you? Has anyone asked how your day has been today? To be a proficient software engineer, we find ourselves in an ocean of skills that are required for the job: each company has its tech stack, its way of working and its culture. Which skills should you focus on? Which ones should you have?
Have you ever wondered about your company’s cultural practices, if they match the image it gives externally and the candidate profiles it attracts?
As a Talent Acquisition in the technology and innovation market, I realize how hard it is for companies to attract and retain talents. And as I understand that attraction and retention go hand in hand, I bring here some of my insights and research into relevant attraction practices that also influence retention.
Let’s discuss a structure to start new projects or when you need to scale large projects.
We will use React Native as a basis for this architecture, but the concepts can be leveraged in projects using other frameworks.
I believe that almost every Android dev has at least once tried to get a View’s dimension, but it returned 0, nada. This is a very common situation, it is one of those problems that we just Google for a solution and find a workaround that seems to work. We add it to the code without having much idea of what’s going on and that’s it. In this article I’ll explain why this happens and why many of the most used workarounds should be avoided. In the end I’ll give you a very sweet solution.
I recently shared content about Product Thinking during an event and this mindset is changing the way I’m looking at Projects and Products.
There are great articles out there about Product Thinking, like this one, but no canvas that brings together all the main questions Product Thinking focuses on.
With that being said, I took a stab at it and created one (there is a tiny possibility others are looking for something like this but never found it).
One of my biggest concerns as a developer is how a project is structured. Defining a good and clean architecture with helpful names and nice design patterns is very important. It helps you and other developers to easily understand how different components of the code connect to each other and makes our lives easier in the long term. It’s also very important to keep a good documentation about it. Always keep the README.md file updated. It helps new developers a lot.