Fork me on GitHub
#off-topic
<
2020-03-02
>
bherrmann00:03:54

FYI: I just finished reading "Accelerate" and I blogged some notes from my take aways from the book..... http://jadn.com/bob/

sogaiu00:03:25

thanks for sharing your thoughts. it does seem surprising that the continunous releasing seems to work better for certain things. was just watching a gdc talk where one of the founders of a game company was saying how much it helped to switch to a cadence-based release.

bherrmann00:03:32

Yea, I would think releasing many times during the day would be a horror show, but I guess you learn not to do things which cause the site to crash... or quickly recover from such flubs... and I guess once you internalize how to do that, you can add real value to the product quickly... once you learn how to ride the unicycle of CD...

1
dominicm07:03:04

I didn't finish accelerate, but I don't understand how CD would make things better. I saw the strong data link. But I didn't really see an explanation.

dominicm07:03:39

If it's possible to achieve the effect one way, it should also be possible through another mechanism with similar attributes.

p-himik07:03:34

@U0502D2GL Not related to the topic, but that link seems to load the whole blog - even if I want to read just one article, the browser still loads almost 19MB.

bherrmann11:03:34

@U2FRKM4TW Thanks for bringing that to my attention... I will address that soon...

bherrmann12:03:58

I wonder if the central theme of "Accelerate" is simply to reduce complexity. Certainly committing to production is simpler than tracking a moving window of when code moves to production... that is ... the entire book's focus is on making it easy to add value to customers... presumably reducing the cognitive load for that task makes adding value a simpler proposition. Or is that an over reach?

fmjrey18:03:21

I did not read the book but automating everything certainly resonates with me. Though when deploy/rollback become very easy and quick, one must preserve from the danger of considering prod to be a test environment.

sogaiu07:03:54

stacking of tags:

(defn my-fn [_]
  "40fff7cc-2e57-42dd-b737-533820ed53e9")

(binding [*data-readers* {'my-tag my-fn}]
  (type (read-string "#uuid #my-tag 1")))

dominicm07:03:25

Aero uses this :)

sogaiu07:03:12

lol, i was hoping someone would say "don't do that" -- i guess i'll be thinking about how to fit it into the tree-sitter grammar after all

alexmiller14:03:43

the fact that this nests and isn't special is more general and you should be glad it works :)

sogaiu14:03:40

i guess i have that to look forward to 🙂

dominicm20:03:46

I seem to recall someone writing a library for refreshing clojure code automatically, Figwheel for clojure essentially.

mauricio.szabo17:03:11

clojure.tools.namespace does this, but not on save.,

mauricio.szabo17:03:41

Some editor plug-ins do it, like proto-repl (and Chlorine also have an option to do it) but it's not widely used

dominicm21:03:43

I wrote a vim thing for it, and also setup require :reload. The latter one stuck. It's only for a specific file. My ideal would be that I would hook eval and run an evaluation after that. Nrepl makes that a little too awkward.

mauricio.szabo00:03:52

Not sure what you meant by the last message... The problem I had with require :reload is that sometimes, when the code was defining a multimethod or protocol, things started to have some bizarre behaviors...

dominicm07:03:23

Yeah. Fortunately I know that is okay in this context.

dominicm07:03:46

What I meant by the last message is that I'd like to change the eval function in my repl (nrepl) to be clojure.core/eval followed by running a particular function. Then I don't need to require automatically.

Michael J Dorian20:03:53

I've had good luck with (require 'namespace :reload). I just make sure to keep all my side effects for initialization in the top namespace that doesn't get reloaded and doesn't depend on any of my other code. I guess that's not very automatic, but it's automatable.

dominicm20:03:50

This thing ran on file change I believe.

vemv03:03:33

Personally I'd never do that... one loses a sense of transactionality, e.g. not reloading code until a set of changed namespaces is deemed consistent. Given the clojure compiler is slow (it works by peforming eval on each form*), taking some care around refresh seems due to me. Else I'll just be constantly breaking my project (due to "transactionality loss"), and firing up (clear). Would seem slower.

dominicm07:03:34

I wouldn't normally do this, but I have a context where I think it makes sense.

mattpend22:03:54

Anyone know of a tool to interact with a web page, perform some manipulations (interact or js injection in page context), and log it out on a schedule? I could put something together pretty quickly with a cron job and a script but it seems like a common enough use case for a decent tool to exist.

hiredman22:03:51

I've used httpunit for that kind of thing, it's ok

👍 1
Eccentric J23:03:14

Could do that with puppeteer but may be overkill.