DEV Community: Emanuele 🍕

Instantiation or !Instantiation of Ruby classes?

Emanuele 🍕 — Mon, 04 May 2020 10:34:11 +0000

The other day I was thinking,

should I always aim for the least memory use when I write Rails code or is any effort unimportant, given that behind the few lines of my own code there is always a plethora of framework calls?

We're now discussing the ethics of our RejectPendingOrderJob.

Simply put, an order is created in pending state and automatically rejected in 72 hours unless it has been approved in the meanwhile.

The job is enqueued with every pending order created, will execute in 72 hours and should do nothing unless the order is still pending.

# I believe a single SQL statement can execute this elegantly
def perform(order_id)
  Order.where(id: order_id, state: :pending).update_all(state: :rejected)
end

# The counter proposal involves the instantiation of the class, which I believe is redundant. 
def perform(order_id)
  order = Order.find(order_id)
  order.rejected! unless order.accepted?
end

What is your preference?

Commander Lazy

Emanuele 🍕 — Wed, 11 Mar 2020 11:06:33 +0000

The other day I was thinking,

I spend way too much time going up my terminal history, so I tried to create an alias with the grep command and my life got immediately better:

alias ??='history | grep '

I can now pick and replay the command I need:

~/WorkSpace/ : ?? yarn
   10  yarn dev
   14  yarn install
   16  yarn dev -- -p 5783
   23  yarn build-storybook
   24  yarn run-storybook
   63  yarn
   65  yarn
   87  yarn
   89  yarn
   90  yarn
   96  yarn
  135  yarn add eslint --dev
  136  yarn add @typescript-eslint/parser --save-dev
  144  yarn
  154  rm  admin-client/yarn-error.log
  170  rm -f yarn.lock
  171  rm -f admin-client/yarn.lock
  174  cd admin-client && yarn install
  175  cd .. && yarn install
  183  rm -f yarn.lock
  184  rm -f admin-client/yarn.lock
  187  cd admin-client && yarn install
  188  cd .. && yarn install
  193  co -- yarn.lock
  245  rm -f yarn.lock
  246  rm -f admin-client/yarn.lock
  249  cd admin-client && yarn install
  250  cd .. && yarn install
  255  yarn build
  256  yarn build
  270  yarn build
  294  yarn build
  297  yarn build
  299  yarn build
  300  yarn build
  303  yarn build
  304  yarn build
  305  yarn build
  384  co -- admin-client/yarn.lock
  503  ?? yarn

But then I quickly became tired with the copy-paste routine and looked into hotkeys (I am using iTerm).

It turns out that Settings > Pointer > Bindings could really implement what I needed:

Now I can simply select the command I need, CMD+right click and voilá :)

How to avoid half-assing all things

Emanuele 🍕 — Sat, 07 Mar 2020 12:28:53 +0000

The other day I was thinking,

I do not have a lack of ideas, I do not have a lack of enthusiasm to start a project, but I possess an incredible track record for stashing half-done things at different stages of their lifecycle. I don't think I am alone.

Seven years back for example, after a few culinary posts sent into the obvious void and even an attempt to be on camera immediately destroyed by hate comments, I "realized" the world needed a GitHub for recipes and jumped headfirst into the project. It went well, iterating rapidly from napkin sketch to mockup to production (with a side of social) where it slowly died, maybe because of the engineering effort drying me up or simply because If you build it, they will come is one huge bias of programmers.

This project (and several others) died and it will never serve a purpose, and it's a shame because - possibly - someone, somewhere might be commencing the development of a similar web app, from scratch.

I've thought of selling the app (that idea lasted 12 seconds), I thought of open-sourcing the project (making it yet another unmaintained codebase), but maybe what we need, hear me out, is a convention to transfer a project and retain a fractional interest: a standard agreement and a common tag to find opportunities!

Example: Here is 95% of the thing I've developed over years of sweat and tears,
let me keep 5% as I guide you and bring you up to speed with all what I think you need to know to succeed...

It could be as easy as tagging your next project as or or ...

Oh, by the way #CODE_CODE_PASS on https://algebro.herokuapp.com/pages/about https://gitlab.com/etozzato/algebro