mumoc

# ***config/application.rb***

module SpreeDemo
  class Application < Rails::Application
    # more awesome code here...
    
    config.to_prepare do |config|
      # more code here...
      
      config.autoload_paths += %W(#{config.root}/lib/spree/)

mumoc

Abandonment Rate:

Shopping cart abandonment is a term frequently used in the ecommerce world. Shopping cart abandonment (a.k.a cart abandonment) refers to the issue when the digital customer adds the desired product to the virtual shopping cart and leaves the digital property before completing the purchase. The abandonment rate is the ratio of the total number of abandoned shopping carts to the number of total initiated cart transactions. The metric is used to measure the performance of the digital shopping cart. A typical abandonment rate varies from 60-85%.

Abandonment Rate = Total number of abandoned carts / Total number of cart transactions

Acquisition:

mumoc

Some time ago I wrote about estimations and how to calculate the effort of the tasks in an attempt to facilitate the process of thinking and reasoning to transfer effort to time, not to impose a new scheme or format.

Interesting enough one of the comments I received was:

It does not make sense, I think the time and I multiply it by 6 and that's it.

Curiously, there is a lot of uncertainty in this method of calculating effort or time; it makes me wonder how customers can accept that method. But then again, these are estimations and it is valid if that is your particular way of working. As an alternative, I would like to focus on what does each task that I estimate have to do with other tasks, other chores, other best practices and whatever my experience reminds me to be aware of in such task.

If you use the Agile methodology, you will be familiar with the following development lifecycle:

mumoc

A few days ago someone asked me:

Is there a method to share what we know? People approaches me with questions and I find it a bit difficult to make myself understand.

My answer was more or less like this.

There are 2 parts on this interaction, that depend on each other:

1. How they ask
2. How do you answer

mumoc

Config

File Model

app/models/my_app_scope/file.rb

module MyAppScope
  class File < ::Spree::Asset
    has_attached_file :attachment,
                      url: '/spree/products/:id/:basename.:extension',

mumoc

Recently, in a Solidus project, we faced the need to add Files to Products for customers to be able to download.

In general terms, the business logic was:

• A Product can have many Files
• Customers can download Files from purchased Products
• File links cannot be shared
• Files must be administrables

Given the project was using Amazon S3 to store the files and we didn't wanted to modify Solidus a lot, our approach was:

mumoc

De Procesos, "Agile" y Profesionalismo

Jueves 18 de Febrero, 2021 by Mumo Carlos

Acerca de Mí

Soy Mumo Carlos Ingeniero de Software en MagmaLabs

Actualmente coordino los esfuerzos de Producto, Investigación y Desarrollo

mumoc

1. Install Lottie Player:

npm install --save @lottiefiles/lottie-player

2. Require it at app/javascript/packs/application.js

require('@lottiefiles/lottie-player');

mumoc

Coherence and Communication

Some time ago someone asked me:

How do you make your teams have more coherence and communication?

Although it involves many things, in my experience, I have found that cultivating these 4 things helps success:

• Ownership
• Continuity

mumoc

Success

Every now and then during a 1–1 or performance review I like to ask: have you been successful? or are you successful?.

Curious have been the answers, so varied and so similar at the same time, with a common line: self-doubt.

Every time you ask me, Are you a successful person? My answer has been and will continue to be the same: YES.

It is necessary to understand what success is, which, by definition, is: