This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-30
Channels
- # aws (1)
- # bangalore-clj (1)
- # beginners (73)
- # boot (13)
- # cider (3)
- # clara (19)
- # cljs-dev (33)
- # cljsrn (37)
- # clojure (177)
- # clojure-dev (13)
- # clojure-gamedev (1)
- # clojure-italy (10)
- # clojure-nlp (1)
- # clojure-russia (1)
- # clojure-spec (64)
- # clojure-uk (128)
- # clojurescript (177)
- # core-async (23)
- # cursive (5)
- # datascript (13)
- # datomic (20)
- # devops (49)
- # emacs (13)
- # graphql (5)
- # hoplon (13)
- # keechma (1)
- # leiningen (3)
- # liberator (4)
- # lumo (2)
- # off-topic (11)
- # om (19)
- # om-next (3)
- # onyx (6)
- # re-frame (13)
- # reagent (14)
- # ring-swagger (7)
- # rum (2)
- # spacemacs (7)
- # unrepl (1)
- # untangled (23)
- # vim (8)
- # yada (1)
ops and programming are getting pretty blurred. with IAAS the whole system, including all the (abstracted) physical resources, are my program
seems like AIs are pretty special purpose still. as long as there isn’t enough money in a niche field to make an AI for it programmers should still have work. =)
seems like they were trying to do that before the AI winter and now the success is with machine learning specialized tasks using big volumes of data
spieden: yeah. but the success of ML and related is spectacular. e.g. Watson on Jeopardy.
what type of naming conventions is everyone using for datomic and for that matter namespaces? organization.project.namespace
for the namespace, and :organization.project.entity/attribute
for the db keys? Do you omit the organization for brevity? I've been trying to think about this more since spec and the promotion of namespaced keys everywhere, but there doesn't seem to be many conventions published out there