HN user

tylerdinner

21 karma
Posts1
Comments10
View on HN

They're public servants. That footage should be public property.

Just like "this call may be monitored for blah blah", your actions as a cop should be monitored by the public.

Maybe we should have local citizens watching/reviewing body cam footage 24/7 to make sure cops are doing their job correctly. It's also job creation.

Edit: obviously there are some confidentiality issues, so only certain folks should have that clearance. But it feels like we need a better oversight system, whatever that may be.

I honestly think 90-95% of Frontend Devs are capable of all this. Maybe not 10 years ago when spaghetti code ruled, but if you got your foot in the door as a FE Dev then you have a portfolio containing examples of almost all this 'wildcard' work.

Totally agree. As a Javascript dev I got functional code pushed on me in 2016.

It's definitely good practice for devs to learn some of the pitfalls that FP prevents and solves, but implementing it on a massive scale front-end application just seems impractical.

Having worked on a large streaming service and considering the author's 3 MONTH struggle after his 40 YEARS experience, I'd estimate that a re-write of our codebase there would have taken our 20 devs over a decade.

I don't feel these unavoidable disadvantages are as black and white and you describe. To circumvent the fake title/bait & switch practices, you could allow users to flag videos as misleading, vote them as spam, etc. Put the number of flags next to the video, add the ability to not even see flagged videos.

Further, scripts could be used to report video play statistics to the scrape site. Drawback is users would have to add the script to their own site, but adding analytics scripts is common practice.

"if you can't reliably identify all the intervals within an octave and identify major, minor, diminished and augmented triads, as well as the basic 4-note chords (major 7, minor 7, dominant 7, minor-7-flat-5) by ear..."

I feel this is phrased in a very daunting way. Understanding how the different notes sounds is certainly a building block to soloing/improvisation, but you do NOT need a jazz-pro ear to do that. I certainly can't always recognize 4 note chord types, but while playing I can tell when a flat 3rd would sound tasty in lieu of a major 3rd.

A great exercise I used is playing piano in C major and getting used to using the black keys, which will all be sharp or flat notes in that key. Get used to how a flat 3rd sounds compared to a major, the same with flat 7ths, sharp 5ths, etc...learn how to add those notes in ways that work.

I improved a LOT from a VERY short course by Youtuber Jeff Schneider that teaches this in a structured manner. It's 25 short & tasty blues licks in C major, so every time something 'tasty' is played, it's either a flat/sharp note and/or a fun rhythm, like a triplet. It made so many things click for my lead playing.

I'm in no way affiliated with Jeff but I can't recommend the course enough, best 15$ I've probably ever spent. It's also now been transcribed to all keys, but I think C is probably all you need. https://jeffschneidermusic.com/store/tastiest-blues-licks