Figwheel doesn't like the `lein install` approach
Figwheel errored me out with the lein install approach. I want to send http requests from the client, so I chose to use the JS Fetch API. Lambda Island made a fetch ClojureScript wrapper, so I (thought I) installed it, but on an attempted recompile, it says: “No such namespace: lambdaisland/fetch, could not locate lambdaisland_SLASH_fetch.cljs…”.
I should learn the tools to manipulate HTTP payloads using the given control information. I see a lot of http libraries that’ll let me use the browser to interact with a server, but I didn’t understand HTTP itself. Now that I get that it’s “stuff” and “how to send and use the stuff”, I need to find robots that process the stuff and directions for using the stuff. I.e. I have some work to do learning Ring/Jetty for Clojure.
In Clojure, you have boxes of code called namespaces, and there are ways of making Clojure communicate between the boxes. There are at least two boxes: clojure.core and your-project.core. If you have external libraries, more boxes will be added to the project. To talk between these boxes, use fully qualified symbols (your-project.other-namespace/func-name) or use refer to enable just using func-name. Now everywhere “boxes” are mentioned replace it with “namespaces”. Biblio:
CSS document flow
If I understand document flow and three properties’ effects on it, I can determine where elements will land. The display, float, and position properties manipulate elements from their default position in the “document flow”. display affects an elements response to box model properties: margin, border, and padding. It also decides whether elements can sit horizontal to it: “inline” yes, “block” no. float pulls things out of the normal flow and makes the normal things flow around it.
I posit a potentially better goal-achieving system. One thing people generally agree on is, “You get/become what you think”. I know that questions direct focus, so I repeat questions almost as a mantra. I tried to direct my foucs on the goal with the question, “What do I want”, but I’ve found this ineffective as the original goal fades, and the answer transforms to “Relax, watch Naruto, check Twitter, sleep…”, all short-term gratifications that do not progress me to the goal.
Learning to speak http
I think to speak with http servers and get their info, I need to know the anatomy of http requests. This means knowing how to populate a request with params, a body, and headers. Something that surprised me a while back is that an http request has multiple headers. Instead of anthropomorphizing the request, hydraize it. It’s a hydra, or a Cerberus: there are many headers. One header is “Authorization” while another is “Accept-Encoding”.
Coding requires thought, not effort. Thinking is questioning and answering. I'll use question-driven development to create the thinking necessary to code.
When coding, I’m gonna Q&A myself. Coding requires thought not effort. I read in Awaken the Giant Within [page number needed] that thinking is mostly the process of asking and answering questions. I recall a while back that I tried this, where I didn’t expect anything to get done until I first answer a question. Though it’s anecdotal, and I just what I recall from 4Clojure problem, the number of which I don’t remember, I remember it being effective.
Talent beats hard work (Naruto Season Two spoilers)
The prelim Chunin exam after the second exam show that hard work doesn’t beat talent. It pulls on your heart strings, getting you to root for the underdog who puts more effort than others, but I conclude that despite it’s honorable notion (i.e. something that should be done), it only ends one way. Neji nearly breaks Hinata’s heart through chakra attacks(?) (with the “Gentle Fist”). Rock Lee fights Gara in one of the final matches.
I want Brave Clojure meetups to cover a single idea instead of a single chapter
People feel overwhelmed with the meetup’s contents. Each chapter has a dozen-plus new ideas. I think focusing on a chapter gives a false set of cohesion, because there’s so much in the chapter. I think focusing on one idea in the chapter and zeroing in on that one idea for the meetup’d be huge. I.e. let people get the surface of Clojure for the Brave and True on their own time and then we’ll use the meetup to drill deeper into it, asking questions about it.
I want to narrow my focus
I want to drill deeper instead of drilling many shallow holes. With my personality (“enneagram seven”), I find this near impossible, as partway through drilling one hole, I see that another hole seems more promising. After all, how could I know everything about this hole before I started digging it? Now that I dug this hole several feet deep, I now know that a different hole seems more promising. But if the treasure’s always at ten feet or deeper, and I keep on changing holes three feet in, I will never get the treasure.