Fork me on GitHub
#off-topic
<
2019-01-11
>
emccue00:01:11

Hypothetically

emccue00:01:29

Let's say I just started a new job and

emccue00:01:40

Also hypothetically

emccue00:01:57

I am maybe probably not at all qualified

emccue00:01:51

How would I go about learning how to work with and construct real world graphs (as in graph dbs)

val_waeselynck06:01:39

The question is a bit vague for me. Do you need to learn to use a graph database? To build one? A theoretical understanding of basic graph notions? A practical knowledge of common graph algorithms and data structures for use in application code?

5
eggsyntax14:01:43

This book, which is fantastic in general, has a terrific section on graph algorithms: http://www.algorist.com/

emccue00:01:11

And what kind of algorithms are helpful in that space

john13:01:16

Welp... Kanaka did it. He went and built a lisp (mal, similar to clojure) on raw wasm: https://github.com/kanaka/mal/tree/76adfab958e24e75df358ee0c9013476dc03e95a/wasm

👍 10
john13:01:26

Gonna be studying that one for a while 🙂

Daniel Hines14:01:29

What does “contrib” mean, in the context of a project, language, or codebase?

danielstockton14:01:09

Contributed by the community, usually

danielstockton14:01:34

Community supported extensions to the core language

seancorfield18:01:42

In Clojure, Contrib often refers to the set of libraries under the clojure org on GitHub, that aren't part of the core download. These have a different management/process to "regular" GitHub Clojure libraries because they're under the same Contributor License Agreement as Clojure itself.

Nick Stares15:01:30

I saw a tweet recently (I think by stu halloway?) that listed vocabulary words helpful for understanding Clojure design decisions. Somehow I can't find it again! Does anyone know what I'm talking about or have a link?

Eccentric J16:01:50

We’re going to put out some job listing soon to expand our team at work. However, I’m debating what to put up. We’re moving towards Clojure in our newer services hosted on a cloud platform but there’s still a monolithic python-django app we need to maintain until we can replace it completely. Would it be better to look for a senior Clojure dev who has some experience in other languages since it focuses on where we want to go or a senior dev with more of a general Java\Python background with an interest in Clojure to help support our legacy system?

helios16:01:50

what's the current composition of the team? Regarding their clojure expertise. I think it's good if you hire somebody with senior clojure experience that can spearhead the transition and help you pick sane things

Eccentric J16:01:01

Just me currently. I think I’m still a beginner with Clojure, especially in a production context.

mattly17:01:52

Yeah you probably want a strong Clojure person with a mix of experience. Very few people have Clojure as their first language

ustunozgur19:01:27

Anyone remember Rich Hickey's codeq project? What happened to that idea? I wrote an article to spark some discussion: https://medium.com/@ustunozgur/the-nosql-database-every-software-developer-uses-10c841278a13

alexmiller20:01:09

still very much alive :)

alexmiller20:01:33

I expect at some point you’ll see form of codeq2

alexmiller20:01:46

but it may be an arbitrarily long time :)

ustunozgur20:01:00

nice to hear 🙂