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.
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.
I just resigned from my job as a software engineer (~9 years of experience) without having another job signed. Best decision I have ever made. The second I did was the second the curiosity and eagerness to learn things came back.
I’m still looking for a lightweight solution (no react etc) that lets me write normal CSS but scoping it to an arbitrary part of my HTML tree. Most of the time I’ll be working in a partial where I know what generic names such as .container refers to And I don’t want to bother with coming up with unique names.
The best I can think of is to use descendant selectors but that increases the specificity and is hard to maintain imo.
Excited to see what the @scope feature draft can bring to this
I’m a teacher mainly for front end development. One of the courses I added this year is called The Ecosystem of the Web.
The brief was that they have to propose a new feature of the web and explain how it would end up being something you can use.
Really fascinating to see what students with very little experience thinks about and suggest. The importance of agency really hit home with me and I’ll try to bring that to the class.
Don’t know too much about the Canadian market but isn’t the convenience of not doing something illegal and it being easily accessible worth paying for. That’s why streaming service’s completely beat out piracy
- 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.