ess3

I think this is a hard problem to solve for a couple of reasons.

- Skew of supply and demand. There will be always be another musician willing to earn less money because they still get to do their ”dream job”.

- The need for background music. No matter how joyless it feels to produce this stuff, there’s a need for it.

I think companies like Epidemic offers an alternative route for musicians to earn some money on the side of their artistic vision.

Biggest issue which is more a philosophical one is how Spotify is shaping how we consume music.

I wonder if we’ll ever see a computer assisted style in esports, like what exists within chess. Bring your best cheats.

Reminds of a quote about Van Morrison:

There are two types of people. The people that like Van Morrison and the people that have met him

A quote from a jazz theory book comes to mind. Goes something like this:

Jazz is 99% theory 1% magic. The difference between the greats is that they’ve forgotten all the theory

This basically the plot of the movie ”Real Genius”

Very nice! The first brief I give my students when teaching web development is similar - Web design like it’s 1999

I don’t remember where I read this (think it was some published paper) but I was building some audio streaming thing on top of WebRTC and there was an estimate that 60% of people would be able to do p2p.

Actually reimplementing something that’s already exists is a great way to get an understanding of it precisely so you can deal with the questions you mention.

My rule of thumb is that you should always understand at least one level of abstraction down.

As a kid I acquired my parent’s login to the school platform meaning I could call in sick myself. However one day I actually got sick so they had to call it in which means they would’ve seen all previous calls.

So I downloaded the HTML for all pages required for this exact flow and removed the previous sick days. I then changed my etc/hosts file, gave them my computer and prayed that they wouldn’t try to visit any other page than the ones I downloaded.

Worked like a charm. Later I called in sick myself.

Cannot recommend this course enough

My biggest gripe is touch interfaces on stoves. You constantly spill water or other things.

I’m very much teaching the same thing - an eight week introduction to JS (after 6 weeks of HTML/CSS).

My approach was to lead with one week of unplugged programming just introducing the concepts of CS. Then introducing the fundamentals of variables loops etc using a block based language.

The following week we transition to JS doing one week of fundamentals and after that moving on the DOM and events.

So far I think it has worked out pretty well. A key part is to work both bottom up and top down at the same time until things eventually click.

The word safe here is doing a lot of heavy lifting imo. Not necessarily safe as in physical safety but also contractual safety.

An example is pension where companies not under collective agreement tend to not specify pension in contract rather just a blurb about "pension is to be compensated based on the currently applicable company policy". Basically allowing them to do whatever bait and switch they want later. Even if the benefits are good now there's no guarantee that they will stay that way. That's what a collective agreement is supposed to protect, that you can't go below that standard.