| defmodule Auth do | |
| require Ash.Query | |
| def can_on_instance?(resource, id, action_name, actor, api) do | |
| action = Ash.Resource.Info.action(resource, action_name) | |
| case action.type do | |
| :create -> | |
| false |
As a mechanical keyboard user, you have probably put a great deal of thought and effort into improving your typing habits.
Perhaps you have been looking past [QWERTY][], and towards [Dvorak][], [Colemak][], or [Workman][] to get that extra edge in speed and comfort when spending long sessions with your clack-y friend.
Well, there is an option available that you may not have considered. One that
This week NN Group released a video by Jakob Nielsen in which he attempts to help designers deal with the problem of customers being resistant to their new site/product redesign. The argument goes thusly:
There's slightly more to it than that, he caveats his argument with requiring you to have of course followed their best practices on product design, and allows for a period of customers being able to elect to continue to use the old site, although he says this is obviously only a temporary solution as you don't want to support both.
This is a post to satisfy your curiosity about alternative keyboard layouts, why some people use them, and whether they're for you. It is intended to discuss the topic in broad terms, but I will share my personal preferences towards the end. Due to time constraints and my own limited knowledge, I will focus on layouts optimized for the English language (ANSI variants, with an occasional nod to ISO).
First off, it's important to understand how much debate there is about how we got here: I will not even attempt to settle the issue of who invented the 'first' typewriter layout, because the modern device had many predecessors going back centuries. The usual legend of typewriter evolution holds that American Christopher Latham Sholes debuted the typewriter in 1868 with a 2-row layout that was (nearly) alphabetical. A horizontal stagger between the rows made room for the lever arms attached to each key:
3 5 7 9 N O P Q R S T U V W X Y Z
2 4 6 8 . A B C D E
There are 28 static site generators that support AsciiDoc sourcing.
git log --graph --oneline --decorate ( git fsck --no-reflog | awk '/dangling commit/ {print $3}' )This will show you all the commits at the tips of your commit graph which are no longer referenced from any branch or tag – every lost commit, including every stash commit you’ve ever created, will be somewhere in that graph.
I recently spent some time dealing with nested forms in Phoenix. Nested forms are great when you want to create multiple database records in a single transaction and associate them with each other. I am new to Phoenix and really struggled to find any resources that helped me with my specific problem. I decided to document what I learned in the process in hopes of helping others that are new to Elixir and Phoenix.
Here is my attempt at a one stop shop to learn everything you will need to know about nested forms. If you would like to view the GitHub repo you can check it out here.
Thanks to Heartbeat and Jose for excellent blog posts on nested forms. Also shoutout to Josh for showing me some examples at Ruby
It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
| # ~/.atom/init.coffee | |
| atom.commands.add 'atom-text-editor', 'elixir:pipeline': -> | |
| editor = atom.workspace.getActiveTextEditor() | |
| editor.moveToEndOfLine() | |
| editor.insertNewline() | |
| editor.insertText("|> ") |