The point here is that, it's important to clarify what you mean by "untested code". Some companies release untested code all the time to production by hide their usage behind feature flags. They admit that the code has not been tested.
Code that we release behind feature flags has been tested, the only reason something goes out on a flag is when we don't want to release it to everyone yet, for product reasons, not technical ones.
Again going back to "untested", when code gets merged, no one ever says "well taht was untested". But what does tested mean? Of course it means that everyone who is accountable for the code believes it was tested. It's subjective, so there can be no other answer.
Processing is what ignited my passion for programming and Quil has become my favorite way of writing it. It is amazing that you can re-evaluate the draw/update function in a running sketch and immediately see the changes, without having to reload the whole thing. And on top of it you have the beauty of the whole Clojure Stdlib with its immutable datastructures.
I just learned that there is now a tweak mode in Processing that lets you tweak certain parameters in the code (via draggable values, etc.) while the sketch is running, which is pretty awesome for experimenting with values. However, you still have to reload the whole sketch when you want to change other parts of the code, you can’t just eval a function in the editor and get immediate feedback like in Quil.
If you mean translating from the JavaScript, yes. Quil wraps Processing. Quil did not wrap the vector library (P5.Vector) but most of vector operations are pretty easy to write in base clojure or you can use clojure.matrix. The fun(ctional)-mode lines up with passing initial state through the functions, which clojure makes easy.
I read it as “Statement of Work” which is description of the work to be performed/delivered, although often much more general than a full technical specification, sometimes in a comedically tragic way.
I’m not sure a job interview is necessarily a good indicator of a person’s status/progress any more than a title. It can be just as human and subjective.
I would hope there are other ways to assess your gaps.
For Clojure - a good start might be something like solving a few of the advent of code puzzles with the simple but powerful map/reduce functions. You won’t need the whole language and you will be writing functional programs.
The experience of that alone might help you find the next book that works for you.
I liked “Remains of the Day” - the subtlety in the tone seems to be intentional given the theme, and tempts the reader to miss the point that lies between the lines - the same theme as the book itself is wrapped around and the main character doesn’t see. I think it is well done.
Batavia’s Graveyard - A brutal history of a shipwreck and subsequent mutiny that occurred off the coast of Australia in 1629 when Dutch traders were exploring a new route to the East Indies. Much better than expected from the cover.
Gates of Fire - Historical fiction that tells the story of the Spartan 300 and the battle of Thermopylae. Lived up to it’s high recommendation.
A People’s Tragedy: The Russian Revolution: 1891-1924 - still working my way through this detailed tome, but enjoying the style of the author.
I've found the best way for me to jump into something is to leave vim open to the very project I'm on--even if I'm midtask. I wouldn't want to close all the windows, as that would make it harder to start the next day.
