This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 100-days-of-code (3)
- # announcements (7)
- # beginners (147)
- # cider (22)
- # cljdoc (24)
- # cljs-dev (71)
- # cljsrn (8)
- # clojars (3)
- # clojure (45)
- # clojure-conj (11)
- # clojure-dev (1)
- # clojure-italy (21)
- # clojure-nl (2)
- # clojure-spec (76)
- # clojure-sweden (2)
- # clojure-uk (100)
- # clojurebridge (3)
- # clojurescript (15)
- # cursive (7)
- # data-science (2)
- # datomic (7)
- # emacs (9)
- # events (2)
- # figwheel-main (4)
- # fulcro (117)
- # jobs (2)
- # jobs-discuss (21)
- # leiningen (184)
- # nyc (4)
- # off-topic (50)
- # planck (6)
- # re-frame (14)
- # reagent (25)
- # ring-swagger (5)
- # shadow-cljs (96)
- # spacemacs (5)
- # sql (26)
- # tools-deps (12)
- # uncomplicate (1)
- # yada (3)
but racket itself doesn't seem all that compelling to me (though the define-syntax style macros seem pretty sweet)
Good idea but web dev can be its own beast as well but if they’re set on web dev that’s a great choice
one of my college acquaintances got a web dev challenge from a prospective employer this weekend
and if they have an issue then they can just click the share button to ask you questions
I’m not sure types would be good for beginners who don’t come from a tech background personally but it may depend on the type of person the beginner is.
How are you connecting to postfix? If it's with a mail app instead of just
telnet or whatever it may be that the app is actually using the SMTP secure port (587)?
I'm currently having issues trying to get
ufw to play nice with Docker in a v6 environment...
Lin Clark is killing it with these WASM status updates: https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future/
I’m curious to learn for those that use Clojure professionally, how large are your teams, what % between junior/senior and how do you split up work into workable chunks?
Some times it feels thats it’s hard to figure out how to split work for 3-4 people, especially on a new project. A lot of stepping on toes etc, no clear way to segment off chunks to be worked on independently.
Here at Yieldbot, we have about 15 people on the tech side now. About half of them use Clojure much. Almost all are senior.
Haven't had the problem with stepping on toes. Maybe you can describe the project(s) with which this is a challenge?
Fairly straightforward web app I’d say. Not terribly complex domain but not too simple either. We are on a 1 month toy project with Clojure to see how it would work. It might be that we are still too much into groundwork rather than feature work, and groundwork/architecture is hard to split up.
I suspect (I’m fairly new to the team) that there are some culture/process issues that are holding us back.
pair programming into a shared vision can do wonders when the work is largely entertwined
It feels frustrating because we all have quite a lot of experience (about 10-15 years each) but for some reason things are going very slow, knowledge sharing is low... or perhaps I just got used to working alone for some time now that the team overheads feel huge to me?
There is already a sort of split between frontend and backend which feels absurd to me, but half the people have already expressed they don’t want to be full stack which is understandable, I guess?
(This has nothing to do with Clojure at this point, these are all issues with our current Node codebase)
A few of us took to Clojure and are trying to see if the nature of the language would make for a better way of working, but in hindsight it feels putting the cart before the horse.
Anyway, sorry for ranting. If anyone has some insight or experience with this kind of thing, I’d appreciate a DM.
The team I just left started as 3 people, grew to about 9 over a couple of years on a very large project. All quite experienced folks until near the end. We didn't have much trouble with toe-stepping, even at the beginning of the project when we were still experimenting and exploring what directions we would take. Maybe the trouble is that it's too many people for a little toy project? Our project was pretty big & complex, so there were a lot of parts to split off. One thing that I think is helpful is to start with a moderately full-featured template like Luminus, and then the basic groundwork is in place from the very beginning. Those seem likely to be some of the toe-steppiest parts, since lack of basic infrastructure is often blocking for other folks. Luminus has enough knobs that you can generally get something that fits your preferences reasonably well (at least within the bounds of typical web project structure).
We also each independently created throwaway versions, only a few days' effort each, and then those served as bases for discussion until we reached consensus on one of those versions to converge on.