This aligns with my experience because the last time I quit coffee I lost the will to live.
2,859 karma · joined July 5, 2016
I am using Elixir’s Livebook to take notes and complete the exercises. It is very helpful to have a live notebook tool while reading it!
- holding in your mind a "thing" (i.e. some code)
- talking about a "thing" (i.e. walking through the code)
The same applies to non-code tasks as well. The ability to segregate the actual "meat" from the discussion is an excellent interface improvement for chatbots.
Given that the very teleology of cloud computing is digital & ephemeral resources, having an actual human face associated with it makes it tangible in a way that is hard to place.
My little brain can briefly understand complex computer systems on a need-to-know basis, with knowledge constantly coming and going based on the demands of the day. I can never fully "understand" my cloud infrastructure. But hey, Kurt's standing there. I like Kurt. I can understand Kurt as he's a human and so am I and he's in the same exact place I am. Let's work hard and make cool stuff, what do ya say Kurt?
A child will eventually collide with reality. Hard. You have one choice:
- have him collide with reality under the watchful eyes of somebody who loves them
- have him collide with reality under the authority of somebody who could care less about him (police, landlord, utilities, etc)
1. The syntax is significantly different than what one may be used to. Fair enough. 2. The paradigm itself is different and thus requires you to learn way of structuring your code in some pretty fundamental ways. This is a much bigger deal than one may initially give it credit for. For example, pattern matching. The mere possibility of defining multiple versions of the same functions based on the number and kind of arguments completely changes how one writes functions.
Instead of:
function hello(x) {
if (x == 2) {
// do x
} else {
// do y
}
}
We can write:
def hello(2) do
# do x
end
def hello(_) do
# do y
end
This was very disruptive to my brain at first as I was not used to reading code in this manner. My brain said "find function, read definition" but it had to learn "find function with proper arity and arguments, read definition". It's hard to put into words, but this made understanding Elixir code feel more difficult at first. However, once I did sink my teeth in , start to maneuver around code bases, and write my own modules it is hard for me to "unsee it" and go back to anything else. I love it! I think the most mind-blowing moment was when I started to pull back the covers in Phoenix and discovered that the framework wasn't some magical black box of FancilyNamedProviders but was just a collection of functions that I could actually read my way through quite simply. I never had to stop and say "wait what did that FacadeOfGoodness do again" but just traced simple functions.
How do you view your day job? As a necessary evil to pay the bills? As a good “real world” counterweight to the arts? I ask in good faith and genuine curiosity as I am likewise drawn to the arts but have over the years come to appreciate how my tech career keeps my feet planted on the ground.
WARNING: personal, non-verifiable theory about to be presented
When coming across modern writers I will often check their biography to see what odd-jobs they have had. I feel that modern man can become so insulated in modern life (e.g. spending an entire career in academia with, say, no hobbies that are grounded in actual life such as fishing, serious gardening, etc) that he can become very disconnected and overly "heady" or "abstract". As such, I often am glad to see when an artist or writer has some terribly mundane and tactile job on their resume. I know that as somebody drawn to the arts I have been incredibly thankful for my unplanned career in software as it has opened my eyes to many naive thoughts I had as to "how the world works".
- Remote: exclusively
- Willing to relocate: n/a
- Résumé/CV: www.linkedin.com/in/linktensen
- Email: christensen@fastmail.com
- Technologies:
Full stack web developer (•_•)
Engineering lead ( •_•)>⌐■-■
Jack of all trades, master of principles (⌐■_■)
PHP, Ruby, Elixir, Javascript, Python. Familiarity with the main frameworks of each. Looking for contract work, but open to full-time opportunities depending on the details.
tldr - prior to the 90s radio stations were largely independent and had local DJs constantly searching out and playing new and original local music as that DJ was incentivized the find the “next big thing”, I.e. a DJ could say “I was the one” who broke Some Big Band on the national scene. However, in the 90s legislation was passed that allowed for the monopolization of radio stations. Many were bought out by large central corps. This resulted in the demise of the local DJ searching for new music, instead replaced by the DJ who is told by those “up top” what to play. Thus we witnessed the death of new and creative acts, replaced by bands that were “formulated” by corp minds.
> "make a song with Johnny Cash singing about X"
That would result in IP/copyright issues, no? I don't really know the legal specifics here, so grant me some slack if I am not using the correct language. But, assuming that input does create a legal problem, does the same apply to these sort of prompts:
> "with a guitar solo by Zakk Wylde"
> "with drum fills like Thomas Stauch"
etc...
Are there similar legal protections around instruments as the voice?
This is bloody brilliant and ranks among the best HN comments I’ve ever encountered. It’s pure poetry and ends with the words “Batman Forever”, a staggering creative achievement.
In my own learning I found this to be the single greatest resource for getting to know the terminal. It has the perfect balance of overview/detail, allowing you to cover an immense amount of ground while feeling like you have a grasp on what's going on when you do something. From there you can then consult reference material as needed.