rpazyaquian

12 ms·

1. 91.▲
   by rpazyaquian 10y ago

   Speaking of SICP, which version of it is the best to dive into? I found the online version of it, but it's kinda clunky to click through. Also pretty dry.
2. 92.▲
   by rpazyaquian 10y ago

   "MooSQL"
3. 93.▲
   by rpazyaquian 10y ago

   I gotta admit, this sounds awful. Adding more mental overhead to your everyday habits sounds like it'd just make things worse.
4. 94.▲
   by rpazyaquian 10y ago

   This article helps explain the how, but doesn't really cover the why . Coming from a functional programming perspective (Ruby, Elixir, Clojure [yes I know]), I don't see where macros become useful or anything more than a curiosit
5. 95.▲
   by rpazyaquian 10y ago

   I'm not quite at the point where I can appreciate how useful this is, because I don't really understand concurrency itself. What is a good resource from which to learn about concurrency, and especially Elixir/Erlang's ap
6. 96.▲
   by rpazyaquian 10y ago

   I am a huge fan of Elixir and Phoenix even without OTP, don't get me wrong. It's my go-to framework now, replacing Rails. I just ended up hitting the OTP chapters in Programming Elixir and Programming Phoenix, and just kind of won
7. 97.▲
   by rpazyaquian 10y ago

   I suppose this means that I've been working on the uninteresting problems in web development (basic CRUD stuff for Rails), and none of the fun networking-related problems, or otherwise. That's pretty disappointing.
8. 98.▲
   by rpazyaquian 10y ago

   I wouldn't be surprised if I've just been insulated from thinking about concurrency with Rails/have never worked on a Rails project that had to think about concurrency in any significant way. Which is a little disappointing,
9. 99.▲
   by rpazyaquian 10y ago

   Microservices makes sense, I suppose, but the cases in which distributed services and isolated processes are critical just aren't comment enough in my experience to require sticking specifically to a SOA-like architecture for everythin
10. 100.▲
    by rpazyaquian 10y ago

    I guess I'm just not used to the Erlang/BEAM message-passing/infinite-servers mental model. I'm used to single threaded programs and importing libraries and the like, so I've never had the need to pull off complicat
11. 101.▲
    by rpazyaquian 10y ago

    I understand the need for reliability, i.e. "come back up if you get bad data so it doesn't just die on you", but this seems like something that dates back from when any kind of raised exception would bring the entire system
12. 102.▲
    by rpazyaquian 10y ago

    So, I know that Elixir is powerful and good at functional programming. The one thing I can't quite understand is why we would want to program everything as a composition of individual programs and applications, with supervisors and a