viebel

8 ms·

31.
Data-Oriented Programming book: First draft(manning.com)
16 points by viebel 5y ago|7 comments
32.
by viebel 5y ago
Lucidchart
33.
by viebel 5y ago
Here are a few things my editor provided me: 1. A process for writing the manuscript 2. Contacting external reviewers 3. Marketing 4. Feedback on a monthly basis
34.
by viebel 5y ago
Totally agree. Especially in READMEs
35.
by viebel 5y ago
I don't really have a scientific editor at Manning. I have: 1. a TDE (Technical development editor) what behaves more like a project manager and I mentioned them in lesson #47 2. A technical reviewer that makes sure the content is clea
36.
by viebel 5y ago
If I ever write another "things I learned ..." I would definitely include the three items that you mentioned.
37.
by viebel 5y ago
Author here: More challenge than fun!
38.
by viebel 5y ago
Author here: In my book, I used mind maps to let the readers visualize a high level summary of a chapter. Here is an example of such a mind map: https://twitter.com/viebel/status/1469187345580793860
39.
Why Clojure in a single picture (with less than 1000 words)(orgpad.com)
4 points by viebel 5y ago|0 comments
40.
100 things I learned writing my first technical book(dev.to)
1 points by viebel 5y ago|1 comments
41.
Codeq – Semantic Git(blog.datomic.com)
2 points by viebel 5y ago|0 comments
42.
A different spin on Python dataclasses(github.com)
1 points by viebel 5y ago|0 comments
43.
Nextjournal(nextjournal.com)
1 points by viebel 5y ago|0 comments
44.
Rails’ ActiveRecord – The Bad and the Ugly(mauricio.szabo.link)
2 points by viebel 5y ago|0 comments
45.
Clojure Guides: Laziness in Clojure(clojure-doc.github.io)
1 points by viebel 5y ago|0 comments
46.
This is DOP (French)(techblog.deepki.com)
1 points by viebel 5y ago|0 comments
47.
by viebel 5y ago
Could you give some examples?
48.
by viebel 5y ago
That's exactly what I had in mind when I wrote the article. Thank you for formulating it in such a clear way.
49.
by viebel 5y ago
Author here: I totally agree with what you wrote and I am taking it as a compliment.
50.
Immutable.js Is Not Dead(github.com)
1 points by viebel 5y ago|0 comments
51.
Stromae Is Back(vrt.be)
2 points by viebel 5y ago|0 comments
52.
Cue: A new language for data validation(cuelang.org)
203 points by viebel 5y ago|89 comments
53.
Embed Neovim in Chrome, Firefox, Thunderbird and many other pieces of software(github.com)
3 points by viebel 5y ago|0 comments
54.
Are Quanta Real?(iupress.org)
2 points by viebel 5y ago|0 comments
55.
BesoGo: A lightwight JavaScript Go board editor(yewang.github.io)
1 points by viebel 5y ago|0 comments
56.
by viebel 5y ago
This method of debugging is unique to Clojure. It relies on data immutability and a powerful REPL. Are there other languages where such an approach is applicable?
57.
The Clojure debbugging way with scope capture(github.com)
4 points by viebel 5y ago|1 comments
58.
Foundation (TV Series) – Adapted from Asimov(imdb.com)
2 points by viebel 5y ago|0 comments
59.
by viebel 5y ago
I really like this story. The idea that everything is written inside one of the books of this library is mind blowing!
60.
Minds, Machines and Godel [pdf](cambridge.org)
2 points by viebel 5y ago|0 comments

More ›