[Disclaimer: I know that the chance of actually finding something via Mastodon post is super low, but I'll try]
Looking for #clojure (#clojurescript) or #guile (#scheme ) #job opportunities.
:clojure: :guix: :lisp:
[Disclaimer: I know that the chance of actually finding something via Mastodon post is super low, but I'll try] Looking for #clojure (#clojurescript) or #guile (#scheme ) #job opportunities. :clojure: :guix: :lisp: 21 comments
@askonomm excuse me. I just don't know what to answer. No disrespect, but it looks like trolling from your side. Why do you code mostly in clojure, not typescript then? @shegeley Not trolling. It's my observation of working with Clojure for the past 5 years, which is that all codebases eventually start to move towards static typing (or schema enforcements in case of Clojure). Grass is always greener on the other side and all that. Also, Clojure makes a hell of a lot more money than TypeScript does. Hence why I code in Clojure. @askonomm I appreciate your experience and work, but schemas (checking data with some patterns in the runtime) and types (static memory cells that checked in compile time*) are 2 very different approaches. And the 2nd on is much less flexible cos it allows not only to check if the data is "string" but also any regexp pattern or it's length etc. In fact the project I work on my current job uses Joi schemas (joi.dev). That is almost same thing as clojure's malli/spec. *crude description @askonomm So, the unpleasant part is: having type system and types for many data entities across the project (that is by definition very stupid entities) and then ALSO having schemas for all that types. So yours data definitions are duplicated in most placed. Meanwhile you could only use schemas. I don't see any problems with describing data with schemas anywhere. That allow to add arbitrary strictness&checking exactly to desired part of your program/system and let other parts more free. @shegeley While it's true that Clojure is a more stable ecosystem, it's also so much smaller, and riddled with abandoned libraries (which you hope are high quality, but it's not always the case). Tooling is quite frankly crap. Front-end debugging tooling for CLJS is a joke in comparison to JS/TS (and to get even something decent, you have to install and set-up a ton of stuff, because Clojure world doesn't care about usable defaults). A lot of critical Clojure stuff is bus factor of 1, etc. @shegeley Where are you located? Lot easier to find work if you are located in the US, less so in EU, and much less if you are in the rest of the world, even if you have US citizenship. @shegeley Oh, I interviewed a Ukranian company a while back. It didn't work out cause I won't work on firdays. I'm not sure that they will hire from rusia but worth a try. I can't remember the name of the company right now, but they sponsored a clojure conference a while ago, so that is a good way to look. @yisraeldov freshcode. Their headquarters is right in the closest Ukrainian city to where I am now. Heard about them. Had an interview a while back. Can't blame them not to prefer russians @shegeley Yeah that was it. But try some other consulting companies like that. Reach out to them again and see if they are interested. @shegeley How about a Guix-related job? I didn't expected to get so much re-posts and favs from so many interesting people. Very thankful for #mastodon community 🙂 :mastodance: Update: I didn't find any job via #mastodon, but felt popular for a little bit with all the reposts and favorites. Nice feeling. |
@shegeley Can we exchange? I wouldn't mind working with TypeScript, a language that helps you write actually correct software without needing to transform it via libraries into some half-baked attempt at a static language like Clojure (+Spec or Malli) is :D
Not to mention the quality of tooling for JS/TS vs Clojure.