It’s common for us developers or technology enthusiasts to encounter technology that we can use right out of the box without really knowing what that thing actually does. It was not long ago when I was first introduced to Redis, this magical thing that solves all sorts of problems.
I was working on a Rails application when I first heard about Redis, but I wasn’t really trying to work with Redis per se, I was more likely trying to make Sidekiq work; a background processor for Ruby that needs Redis in order to work as I had always been expecting things to work, out of the box.
If you are not familiar with background processors on...
Entering a new company is always a challenge, a challenge that not only entails testing your technical knowledge but also how you interact with your co-workers.
Talking with friends and fellow programmers about their experiences when entering a new company, I gave myself the task of delving a little more into a specific topic “What qualities do you consider positive in a co-worker?” And considering his answers, I made my best effort to take the qualities that they mostly emphasized on as positive aspects of a co-worker. These capabilities are named “Soft Skills” according to Sophia Bernazzani.
What qualities do you look for in a co-worker?
As an Android developer who started working with Android 4 years ago, I had to learn Java in order to create native applications. For the first two years, I learned a lot about Java and I started to feel that I was getting good at it. During this period, I heard you could use Kotlin to create Android apps but I always thought “There’s no way Google would deprecate Java, it’s their main language.”
A year passed, and first-class support for Kotlin was announced at Google I/O 2017. In 2018 Kotlin was voted as the second most loved programming language (StackOverflow).
Have you heard the story about the two engineers and the manager who found a Genie lamp? This manager and his team were looking for a laptop with crucial information for delivering an app. While searching their storage room, they stumbled into an old oil lamp that would look cool in the office, so they decided to clean it. After a couple of rubs, a Genie comes out.
The Genie told the three he will grant one wish to each one of them, so the first engineer is quick to say: “I want to be in the Bahamas, living in my dream home and owning a yacht” Puff! He is gone. The second engineer screams: “I’m next! I want to be...
“Why has it become so difficult to hire people in startups? Do you think you could send us more options? When would I have the first list?”
As a Technical Recruitment Leader, these are just some of the questions that I hear practically every day, throughout the years of experience in several companies (Enterprise, Mid Sized Companies, and Startups).
I have realized that one of the most relevant factors, when it comes to attracting talent, is the organizational culture of the company. This, in turn, is part of its “Employer Brand.” Let’s accept it, saying, “I’ll talk to you about X or Y transnational company (that everyone knows...
This blog post aims to address a controversial topic within the QA tester community: test cases. When I first read about this topic, I was wondering whether test cases are actually an asset or a hindrance to the QA testing process. The following paragraphs are meant to help us distinguish between the advantages and disadvantages of different test cases.
On one hand, some people say that it is essential to design a test plan and have the whole list of test cases before starting to test. These people consider test cases an asset. On the other hand, some other people say test cases are actually a hindrance...
As a software engineer, I know how frustrating it can be to work with legacy code, especially when your client has no idea of the level of technical debt you are inheriting, and wants you to deliver bug fixes and new features as soon as possible. If you’re as passionate about software development as I am, you’re supposed to enjoy it, not hate it. That’s why I’m writing this blog post: To share my experience and a key piece of advice about how to deal with it.
The most common issues of working with legacy code are:
- Having no tests at all, or no useful tests.
- Outdated dependencies.
The following video is the core content of the second part of a Desing Thinking workshop imparted by our friend Michael Gharabiklou, Founder/Managing Partner at Quor Studio. You can watch part one here.
On his visit to TangoSource’s México’s Headquarters, our friend Michael Gharabiklou, Founder/Managing Partner at Quor Studio, shared his knowledge about Design Thinking with us.
The following video is the core content of a 3-hour workshop and the first part of a 2-video series. It Includes the Design Thinking process and the importance of empathy in this methodology, among other topics.
What is prop drilling?
“Prop drilling is when a prop is passed to a Component only for the sole purpose of passing it down to a child.”
In React, it is pretty common to find yourself writing a lot of boilerplate code for passing a value to a component, only to pass that component down again to a child, and this can be repeated as many times with many children as needed, until the data you are passing down reaches the component where you need it.
Not only this will cause a considerable amount of extra code written, but it will also affect the architectural design of your component, which will now require to have...