All About Javascript Bind

Ricardo Enrique — Tue, 26 Jan 2021 02:42:38 +0000

The bind() method creates a new function, which when called, assigns its operator this the delivered value, with a sequence of arguments given preceding any given when the function is called.

The value of this is ignored when the function is called with the new operator.

Syntax

fun.bind(thisArg[, arg1[, arg2[, ...]]])

Parameters

thisArg
It is a value that will be sent to the target function when the binding function is called. This value will be ignored if the binding function is constructed using the new operator.
arg1, arg2, ...

They are the arguments that will be sent in addition to those provided to the binding function when the target function is invoked.

The javascript bind function creates a new function (bound function) with the same body (internal call property in ECMAScript 5 terms) as the function to be called (the target function of the bound function) with the this reference associated to the first argument de bind (), which cannot be overwritten. bind () also accepts default parameters that will precede the rest of the specific parameters when the objective function is called. A bound function can also be constructed using the new operator: by doing so, it will act as if the objective function had been constructed instead.

In the latter case, the corresponding parameter for this will be ignored, although the default parameters that will precede the rest will be provided for the emulated function.

The simplest use of bind () is to make a function that, no matter how it is called, always points to the same object with the this reference. A common mistake for newer JavaScript programmers is that they get a reference to a method of an object, then they execute that method from the external reference and expect the reference to this to still point to the original object from which the method was obtained (e.g. when use that method in a callback). Without due care, the original item is commonly lost. Creating a bound function from the function using the original object neatly solves this problem:

this.x = 9;
var module = {
  x: 81,
  getX: function() { return this.x; }
};

module.getX(); // 81

var getX = module.getX;
getX(); // 9, porque en este caso, "this" apunta al objeto global

// Crear una nueva función con 'this' asociado al objeto original 'module'
var boundGetX = getX.bind(module);
boundGetX(); // 81

What is a product manager anyways?

Ricardo Enrique — Tue, 06 Oct 2020 01:03:04 +0000

A couple of years ago, I was working for a well-known company, which I'm going to reserve the name, as a backend developer. In my team, a "functional" team, there were 2 more backend devs, one frontend dev, and 3, yes! 3! product managers. Not that my team managed 3 different products, but for some reason, there were 3 product managers. And at one point I saw myself coding while one of the product managers stood behind me for 3 hours straight. He was standing there watching what I was doing, stressing the heck out of me.

So I began to question: what is it that these guys do that they have so much time in their hands. Why they can stand behind me and watch me code? Don't they have product management things to do?

My perception was those product managers where some weird sort of project managers. They managed JIRA boards, created and assigned tasks, and responsibilities and lead scrum meetings. Yet when I checked the workday organizational chart, they appeared as "product manager". So I began to research what is a product manager, and how this role differentiates whit a project manager.

My first action was to take a course in udemy called: "Product Management 101" which was a very ad-hoc name. The course was very solid and made me realize that there was no need for 3 product managers in my team. At must 1 is enough, and 1 project manager to get product management input and turn it into tasks.

What are product managers supposed to do?

Turns out that the last thing a product manager should be doing is managing Jira or staring at you for 3 hours. Here is a list of capabilities that a product manager should have.

Market Intelligence

At first product managers should gather market intelligence about the product. This includes but is not limited to:

Market Analysis
Profiling market segments
Sizing market segments
Analysing customers
Analysing and monitoring competitors

So, any knowledge that generates a competitive advantage is market intelligence. Product managers are responsible to gather this intelligence.

For example, there was a fun story of a product manager in charge of a company selling home appliances in China. At one point one of their top-selling washing machines started to peak on faulty returns. So the product manager went to investigate and found that all the returns came from a single region. So he decided to go there and see what use the customers were making to the machines. The machine seemed to be working great until people decided to use it to wash freshly cropped potatoes. So he went back to HQ with this intel, and the further versions of this product came with potato washing support!

Product Strategy

Now product strategy defines the objectives and vision of the product. Once the product strategy is ready product managers share it with the rest of the management.

New product development

To me, this is the most fun area in product management. In new product development, product managers get to establish priorities and key objectives. Then roadmapping the product from documentation to release. Lots of discovery and delivery to have a successful product ready to begin its lifecycle.

Lifecycle management

When I first saw that products also have lifecycle management I thought: Ja! that's it, this is where product managers meet JIRA and start to act as project managers, right? wrong.

Turns out product lifecycle management is more than checking how are things going. It involves:

Positioning and communication * Benefit trees
Pricing and discounts
Support to sales
Growth
Product support
Obsolescence

So the way that I understand it, is that product managers, as the name implies, manages the product. And their communication should be to the project managers and engineering analysts. These teams of specialists bring products to life and worry about project management.

Conlusion

Ideally, a good product manager is not a project manager but does communicates effectively with them. Together with the development teams they achieve great products and conquer the markets.

DEV Community: Ricardo Enrique