This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # beginners (155)
- # calva (104)
- # cider (7)
- # clj-kondo (55)
- # cljdoc (2)
- # cljs-dev (19)
- # cljsrn (22)
- # clojure (230)
- # clojure-europe (1)
- # clojure-italy (15)
- # clojure-losangeles (8)
- # clojure-nl (11)
- # clojure-spec (20)
- # clojure-uk (30)
- # clojurescript (10)
- # code-reviews (32)
- # cursive (2)
- # data-science (6)
- # datascript (3)
- # datomic (141)
- # fulcro (1)
- # graphql (6)
- # jobs-discuss (19)
- # luminus (8)
- # off-topic (30)
- # pathom (2)
- # protorepl (8)
- # reagent (15)
- # reitit (3)
- # shadow-cljs (11)
- # tools-deps (1)
- # xtdb (8)
I worked through this book on lenses: https://leanpub.com/lenses great read by Clojure/Ruby/OO guy who tries statically typed FP
@lady3janepl I've messed around with Patchwork, the social network app built on Scuttlebutt. It's really neat, very easy to set up, there's a lot of interesting posts to see once you join a pub or two.
Thanks @bfay ! I’ve read people talk about how identity is tied to a specific machine you’re on - do you know if there is a way to back it up?
iirc your identity is actually just an ssh key, as long as you have the private key on your pc I... think you can log in with that. But the posts that you see are actually downloaded to disk (so you can view offline). I think they would be redownloaded if you logged in on a new PC, at least up to a certain time limit
Are there any particular communities that are active on it? I remember G+ was big among pen and paper RPG players for example
Yeah you can search for posts by tag and there's a lot out there - I found some programming and music related things that I was interested in. There seemed to be a lot of members interested in environmental issues, low-power technology, some movement called "solarpunk" that I hadn't heard of before. It's very decentralized and I don't know if you would find something like an organized group to join, but people seemed very welcoming. Definitely no harm in creating an account and trying it out if you want to
I’m trying to look for smaller communities, since the main internet is increasingly marketing oriented, and I just don’t have time to compete with rock stars (and ads). I’ll give it a try. Thanks!
anyone experience with tuxedo? this notebook looks good: https://www.tuxedocomputers.com/en/Linux-Hardware/Linux-Notebooks/10-14-inch/TUXEDO-InfinityBook-Pro-14-v4-14-non-glare-Full-HD-IPS-aluminium-chassis-bis-Intel-Core-i7-Quad-Core-max-32GB-RAM-max-two-HDD/SSD-max-12h-battery-USB-C-Thunderbolt-3.tuxedo# (configurable up to 64GB memory)
https://getguru.com . We don’t use it as well as we could, but it’s pretty good.
markdown docs in repos for techies, confluence pages for techie-to-non-techie communication
We just had a workshop figuring out pain points for our team (kind of like a retro in a bigger context). Turns out, documentation is our largest one. I work for a company with probably 50 - 100 products that are put together and depend on each other in the wildest ways. So often you have to figure out how some other stuff works, which code belongs to which team, if there is a mailing list where one can ask, etc. Unfortunately every product can document what and how it wants, every product has a product key which is totally not relevant to its product name and the code location and package naming is different too.
We do use confluence and I have to say, it's search is as bad as search can be, I'd guess even altavista was better.
In our brainstorming session we came up with a few ideas that would make it better and I'd even argue with points that are a must have. • Every thing that is distinguishable and unique becomes one name and this one name is used everywhere. No exceptions. It is used in internal and external documentation, it is part of the package naming, it is part of the code location, it is part of the issue tracker, etc. This is something that enables back and forward navigation and cannot be underestimated. • There should be a must implement guideline on structured documentation that is the same for every thing, again no exceptions. • Part of it is every contact known to that thing. • A solution book with how tos.
what I found made a difference was a dedicated product person who was good at communication (a philosophy grad 😄 ) and took the time to organise information
Yea, we have a documentation team for our external documentation and they do a good job. But thats not helpful for internal stuff.
Definitly. I think the main reasons for this are 1. Documentation grows organically 2. It's an afterthought 3. It's not getting paid.