paul / blog.theamazingrando.com Goto Github PK

• View objects
  • decorators
  • presenters
  • form objects
• query objects
• command objects

Some changes I'd like to make to the internet, the would only be possible by google because they control a major browser and a major complex website (gmail). Kinda like how they did with SPDY/HTTP2.

• Kill passwords. Similar to how SSH works with server and client certificates, a browser could manage the user's certificates seamlessly, and would "register" with a service by providing my public key, then the service could verify who I am from then on.
• Keep my profile data on my computer, and only provide it to services after asking me. The browser could keep several profiles (personal, work, anonymous), and ask me which to provide.

How to manage errors in ActiveJob

Error classes: "transient", "unretryable", etc...

Einstien's original quote:

It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.

Often simplified to:

Everything should be as simple as it can be, but not simpler.

https://quoteinvestigator.com/2011/05/13/einstein-simple/
https://books.google.com/books?id=prDfAFjet9cC&pg=PA230&lpg=PA230&dq=roger+sessions+einstein+simple&source=bl&ots=Pz4qMxh5is&sig=FLJB2lTfDvIzRU3MKObDNfw0MiY&hl=en&ei=jC_NTdqWLKL00gGdyqHoDQ&sa=X&oi=book_result&ct=result#v=onepage&q=roger sessions einstein simple&f=false

Nothing is set in stone, and no rule should be followed to the letter.

The code you're writing now is almost certainly wrong. Either you did it wrong, or the requirements are going to change, or the product is going to change, or this feature is going to get refactored with another. Knowing that what you're writing is almost certainly going to be incorrect, you should instead strive to make it as easy to change in the future as possible.

useful midpoint between rails monolith and microservices.

a rails app centered around a single feature or component, but has its own ui, background jobs, handles authn & authz, etc...

Rewrite https://github.com/kapost/kapost-wiki/blob/feature/local-environments/docs/general/environments.mkd for a wide audience.

Start with a long procedural controller action (or activejob?). Factor it into helper methods, then smaller service objects, then compose the service objects into a transaction.