Mike Schaeffer (@[email protected])

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

HTTP 301 - https://t.co/bWpUvNvMGs

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@JustDeezGuy @kerckhove_ts @ChShersh That was well and good, but a few semesters later, I tried applying the style to write a Java compiler in Lisp for my compilers class. I lasted a few weeks before discovering hash tables, arrays, mutation, etc., breaking down and using them.

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@JustDeezGuy @kerckhove_ts @ChShersh I came to it through Common Lisp. The way Lisp was taught at my school, we were strongly encouraged to use a functional style and functional data structures. In Common Lisp, that means lists only. Mutation was an advanced technique and strongly discouraged early on.

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@allenholub 1) Listen more.
2) Work to develop trust.
3) Try to understand the constraints and goals of the organization.

The developers may 'do the work', but it's done in a context and it takes work to appreciate and understand how to work effectively within that context.

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@calvinfroedge How does the voter trust that the contents of the blockchain are accurate and reflect their intent?

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@_Felipe @magnusmbratteng PG is not designed for arbitrary numbers of largely independent repositories. All of those commands work on whatever the current database it. git does not have that luxury.

[Mike Schaeffer (@[email protected]) @mschaef_ectw]

@sveri80 @samcook_ @ryanwinchester I was going back more than just 'a few' years...