DidactMacros
Opinions regarding use of gerunds (e.g. Ordering, Billing, Scheduling) as context names
Hey all.
I’d like to know your thoughts on whether it would be helpful to review the notion of establishing the standard of using gerunds for contexts names.
This comes from the notion of considering a given business as a facility that facilitates the performance of various operations by its interfacers.
Each facilitation would be regarded as contexts comprising interconnected operations, some pretty familiar examples would be cataloguing, carting, ordering, billing, scheduling, registering, etc. This also helps ameliorate the use of explicitness with which contexts and resources are separated as a standard practice.
I know this isn’t groundbreaking or anything, and the shift from the current approach to the suggested one might seem insignificant, but I think the use of gerunds ensures that the operations of the business are the main point of consideration.
Anyway, I’d appreciate your views, I’m currently just working through setting up some holistic steps for implementing some cool web features using the framework and this occurred to me.
The phoenix framework supports pretty rapid development.
Most Liked
cmo
I wouldn’t want to require one or the other. In my experience, sometimes it makes sense to use a gerund and sometimes it doesn’t.
Never heard the word gerund before.
cmo
Not everything is about a business doing something. If the app was a database, would you need to call the part related to storage Storing? I would call it Storage.
sevenseacat
Accounts is another pretty common one
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









