This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-03
Channels
- # beginners (167)
- # boot (22)
- # chestnut (3)
- # cider (9)
- # clojure (107)
- # clojure-berlin (1)
- # clojure-greece (3)
- # clojure-italy (6)
- # clojure-losangeles (6)
- # clojure-russia (8)
- # clojure-spec (71)
- # clojure-uk (42)
- # clojurescript (186)
- # community-development (1)
- # core-async (12)
- # core-typed (1)
- # css (15)
- # cursive (29)
- # data-science (11)
- # datomic (8)
- # defnpodcast (28)
- # duct (2)
- # fulcro (169)
- # graphql (6)
- # hoplon (3)
- # jobs-discuss (1)
- # kekkonen (5)
- # leiningen (11)
- # lumo (7)
- # off-topic (14)
- # om (1)
- # other-languages (14)
- # portkey (7)
- # re-frame (27)
- # reagent (14)
- # remote-jobs (1)
- # ring-swagger (5)
- # rum (15)
- # shadow-cljs (52)
- # spacemacs (59)
- # specter (78)
- # test-check (3)
- # vim (9)
- # yada (23)
Hi there!
Been reading the archive of this channel, it was a bit upsetting to know the struggles some can have for getting a Clojure job due to factors mostly out of their control. I can relate - my Clojure roles have been mostly luck-driven.
I read once that the best startups don't just serve an existing niche, but rather create a whole new market for which they have the monopoly (at least at first).
In case it inspires someone - you can apply that same principle locally?
One could give a serious shot at selling ClojureScript in Javascript groups, or Clojure in functional groups etc. In a way, companies use what developers use, so if you can attract some developers to Clojure, that's a win.
You don't have to have levels of persuasion - Clojure has many advantages that speak for themselves. I would highlight to developers:
- It's the last syntax you'll have to learn: use it for backend, frontend, comm, db
- It's (almost) as dynamic or static as you want (personally I litter my code with
:pre
s and similar)
- You get all this editor goodness (you better have an impressive Emacs to demo!)
- You avoid all this $OTHER_LANG complexity
- Macros (particularly real-world cases)
The key part is that, you being a consultant, can subtly offer yourself in the adoption process. Create a need, satisfy it yourself.
Aside from convincing developers, you can network with founders and such. That's not a mirage at all, if you get yourself out there (or even just online) you'll connect with a few founders a year, fact. Use those opportunities.
If you really are productive with your toolchain, that confidence can translate into sales.
Finally there's always the chance to introduce your boss/team to Clojure, particularly in small/early-stage teams I guess.
Hard to determine the length of a 'sales cycle'. Even if it took 1 whole year of sporadic public talking, blogging etc wouldn't you be glad to have made it? In your city? Actually leading/supervising the development? 🙂
If I happened to be looking for a job today I would definitely follow these lines (might even do it anyway just for fun). Clojure is too beautiful/productive of a language to slowly starve, while brilliant developers are left without a lot of options (particularly outside the USA/UK hotspots), Elixir eats our lunch, etc
✌️