This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (28)
- # asami (12)
- # aws (3)
- # babashka (69)
- # babashka-sci-dev (34)
- # beginners (52)
- # biff (3)
- # calva (20)
- # clj-kondo (4)
- # cljsrn (4)
- # clojars (1)
- # clojure (90)
- # clojure-czech (2)
- # clojure-europe (33)
- # clojure-nl (11)
- # clojure-norway (35)
- # clojure-seattle (1)
- # clojure-uk (5)
- # clojurescript (87)
- # cursive (10)
- # datascript (5)
- # datomic (35)
- # defnpodcast (1)
- # emacs (8)
- # events (4)
- # fulcro (1)
- # google-cloud (2)
- # graphql (2)
- # hispano (2)
- # honeysql (5)
- # hoplon (2)
- # hugsql (1)
- # jobs (7)
- # kaocha (9)
- # lsp (102)
- # meander (13)
- # observability (7)
- # off-topic (56)
- # overtone (2)
- # pathom (47)
- # podcasts (1)
- # rdf (30)
- # reagent (16)
- # reitit (1)
- # releases (2)
- # remote-jobs (26)
- # rewrite-clj (10)
- # tools-deps (4)
- # vim (5)
- # vscode (4)
- # xtdb (41)
Hey, CTO at https://flowyour.money/ here 🙂
Flow is a fintech startup focused on building the self-driving money 💶 app.
We’re looking for genuine & smart people to join our team.
By design Flow is a remote company and our team is distributed around the planet: mostly based in the Netherlands, Brazil and Georgia.
Right now Flow can connect to EU bank accounts (we have a PSD2 license) and create automation rules for bank accounts.
It’s a bit like IFTTT for money, but with a more general money-management endgame.
Having just closed a funding round (news pending) we’re actively looking for devs to write functional, data heavy components in ClojureScript.
Combining these with TypeScript to hook things up into a async/await mutating thing of beauty.
This approach is inspired by the https://www.youtube.com/watch?v=IZlt6hH8YiA talk. (if you’re around here: thanks Ben!)
To get seamless polyglot frontend/backend integration, we started building an open-source ClojureScript library: https://github.com/flowyourmoney/malli-ts 📚
Frontend is done in http://Expo.io react-native connecting through GraphQL with our AWS Serverless backend.
We’re using http://serverless-stack.com to have per-developer, live-reloading Lambda development environments.
It got us this far, but for next-level reliability and human/dev scalability, we’re adding http://temporal.io to the mix to integrate all the moving parts that are “modern” banks, services and APIs.
I hope this message gives a hint of all the exciting stuff we’re doing and our unique approach software development.
Other than just tech, the product is on the path to making a big difference. Most people just wing it month to month and do not manage their money. Many have no savings for an emergency… We’re changing this.
I was about ask what is the difference to https://github.com/tiagodalloca/malli-ts, but it seems to redirect now to https://github.com/flowyourmoney/malli-ts 😎. Congrats and good luck with both the company & the lib! happy to help with the latter, ping me if something is needed on the core side of malli.
I tried malli and it has swagger generator. And then from that you can already generate TS objects but it doesn't support fancy schemas (recursive,
:or and so on). But support of these OOP features are dependent on the language and the generator.
So I don't see very much value in the malli-ts project because you could set up the generation and have the most important parts for free.
Did I miss something?
That’s right. We also want to generate the GraphQL schema from malli and have a single source of truth for services and databases
Edit: I misread
Malli=>Swagger=>Ts seems like a very roundabout way of generating Ts. We include the schema in a doc comment. The lib is just getting started and still quite small, but it works.
One can also define schemas for clojurescript defined functions. That way any exported cljs function can be called from Ts with a malli typed schema.
That's pretty nice if you can extract
crypto.Hash from clojurescript source.
Yes we could go further with the clojure analyzer, but then you’d not automatically get malli’s schemas for args/return values
Been down this path and it doesn't scale as well as you'd hope. Cljs on lambda was sufficiently dev-unfriendly that I did a whole Clojure-eXchange talk on it. Schema-first development (particularly with Pact broker) also turns out less well than you'd hope, with plenty of foot guns.
Curious what foot guns you experienced by setting up a common language and service contracts? (schemas)
@U6Y160CR4 Interesting! May I have a pointer to that talk? Perhaps my google-fu is failing me…
I did a follow-up 'lightning' talk on the same subject in 2018, I seem to remember being more explicit on the cljs problems in this one. https://skillsmatter.com/skillscasts/12778-lightning-talk-fullstack-clojure-in-the-movie-business
Hi all. We are looking for some remote, part-time (for now, possibly full time soon) help building a Datomic-backed GraphQL API in Clojure on AWS. DM me if you are interested and we can discuss details.
Persuaded my #$%^ MBPro to accept electricity and managed to refresh the AskHN jobs listing. I think I see a couple of new ones searching the fill listing for "clojure or cljs or scheme or lisp". FYI