Live data from Hacker News

Writing System Software [video]

youtube.com

61–70 of 73 posts

Re: Writing System Software [video]

#61
post #10

In case you are interested in providing feedbacks about the next episodes, my current list of potential ideas is: 1. Code snippets: show small self contained functions from random places inside Redis. 2. Redis Sentinel: the first design, the immediate redesign of v2, and how it is internally implemented. 3. The use of goto in Redis. 4. Redis protocol parsing and zero-copying of objects. 5. The odd Redis persistence m…

> language barriers due to the speaker accent (in my case) and the listener ability to understand English without subtitles. It's usually easier for a non-native English speaker (at least below ILR[1] Level 3 or CEFR[2] Level B) to understand English spoken by another non-native, because the pace is slower, idioms and expressions are not used so regularly, etc. Your accent is much easier for non-natives than a strong…

Fully agreed. I tend to find non-native English speakers' accents more understandable than many native British or American accents, ironic as it is. Salvatore's accent is quite easy on the ears.

Same goes for a tendency of many native speakers to indulge in idioms, archaic vocabulary and convoluted syntax just for the heck of it. Non-natives just cut to the chase, which is exactly what you want in a technical discussion.

Re: Writing System Software [video]

#62

Earlier quoted context omitted.

OTOH, smart people often build systems with excessive complexity, leading to maintenance problems. Genius is found in making complex things comprehensible and simple.

I would say that people who build systems with excessive complexity are (almost per definition) not smart. They made appear confident and have a high level of "I am so smart" feel about them. But they are clearly not.

Some people learn the value of simplicity through experience. They start out building over-complex things, and they’re not “not smart,” just inexperienced and misguided.

Re: Writing System Software [video]

#63
post #39

Earlier quoted context omitted.

> language barriers due to the speaker accent (in my case) and the listener ability to understand English without subtitles. It's usually easier for a non-native English speaker (at least below ILR[1] Level 3 or CEFR[2] Level B) to understand English spoken by another non-native, because the pace is slower, idioms and expressions are not used so regularly, etc. Your accent is much easier for non-natives than a strong…

Cool, makes sense, thank you. I just want to talk slower in the next videos, so that it will be easier... at the cost to enlarge the duration a little bit.

Playback speed is adjustable so I wouldn't stress too much about it.

Re: Writing System Software [video]

#64
"This is about system software, so we will see lower level things [...] to show --in real source-code, not in small toy examples-- how things work, why certain things were implemented in a given way. You know, when software starts to become bigger, then the very clean approaches start to fail. You have to face compromises in order to make things work.."

Re: Writing System Software [video]

#66

Having watched similar series in the past, I would highly recommend some extra effort be put into the presentation - recording videos with no attention to lighting or sound makes it really hard to see and hear what's going on. Specifically for me, it's really hard to understand what's being said over the keyboard and reverb. Some basic lighting (so your face isn't in shadows), a separate directional microphone (even…

As someone who has spent a fair amount of time playing with this, post processing audio is a big win. I use audacity and perform the following effects (the order is important):

- Noise reduction

- Compressor with "Make-up gain for 0 db after compressing turned off".

- Equalisation with a curve that starts at -6 db at 20Hz, peaks at 6 db at 150 Hz and then curves down to -30 db at 20000 Hz.

- Normalise with Remove DC offset and normalising at -0.1 db (0.0 db sometimes leads to problems for some reason).

- Amplify if you need it (usually I don't)

The logic here is: Noise reduction, to reduce hiss, key clicks, etc, etc., Compressor to squash the low and high amplitudes (turning off making up the gain also forces it to squash in a certain direction... I forget which at the moment, but it's important), Equalise as a kind of nicer low pass filter that gets rid of the noise reduction artefacts and other noises that make it through, Normalise to bring the amplitude back up that was knocked off by the compress (but in a nicer way than amplify would give you). Finally just fine tuning with amplify.

I usually re-encode in FLAC and then mix it back into my video using my video editing software (I use Kdenlive).

The difference in audio quality is unbelievable. You need to fiddle around a bit with the settings for your voice/environment, but I highly recommend giving it a try.

Re: Writing System Software [video]

#67
post #60

Having watched similar series in the past, I would highly recommend some extra effort be put into the presentation - recording videos with no attention to lighting or sound makes it really hard to see and hear what's going on. Specifically for me, it's really hard to understand what's being said over the keyboard and reverb. Some basic lighting (so your face isn't in shadows), a separate directional microphone (even…

I haven't had any issues with the audio. How are you listening to it?

The voice is reasonably clear but the loud keyboard tapping is a problem. A voice microphone not attached to the keyboard would help that.

Re: Writing System Software [video]

#68

Having watched similar series in the past, I would highly recommend some extra effort be put into the presentation - recording videos with no attention to lighting or sound makes it really hard to see and hear what's going on. Specifically for me, it's really hard to understand what's being said over the keyboard and reverb. Some basic lighting (so your face isn't in shadows), a separate directional microphone (even…

As someone who has spent a fair amount of time playing with this, post processing audio is a big win. I use audacity and perform the following effects (the order is important): - Noise reduction - Compressor with "Make-up gain for 0 db after compressing turned off ". - Equalisation with a curve that starts at -6 db at 20Hz, peaks at 6 db at 150 Hz and then curves down to -30 db at 20000 Hz. - Normalise with Remove DC…

> - Equalisation with a curve that starts at -6 db at 20Hz, peaks at 6 db at 150 Hz and then curves down to -30 db at 20000 Hz.

this seems like a very bad idea, this will give you very dull, boomy sound, for most recording setups. It's a bit too much work to type out everything here, but this is not good advice.

Most of the time the best improvements are to be made with getting a decent microphone and set it up properly (doesn't have to cost much more than $100).

Re: Writing System Software [video]

#69
post #39

Earlier quoted context omitted.

> language barriers due to the speaker accent (in my case) and the listener ability to understand English without subtitles. It's usually easier for a non-native English speaker (at least below ILR[1] Level 3 or CEFR[2] Level B) to understand English spoken by another non-native, because the pace is slower, idioms and expressions are not used so regularly, etc. Your accent is much easier for non-natives than a strong…

Cool, makes sense, thank you. I just want to talk slower in the next videos, so that it will be easier... at the cost to enlarge the duration a little bit.

Don't worry about the language. You are very easy to understand and follow. Great work!!! Also I enjoyed seeing you in video. Best regards A random fan :-)

Re: Writing System Software [video]

#70
post #10

In case you are interested in providing feedbacks about the next episodes, my current list of potential ideas is: 1. Code snippets: show small self contained functions from random places inside Redis. 2. Redis Sentinel: the first design, the immediate redesign of v2, and how it is internally implemented. 3. The use of goto in Redis. 4. Redis protocol parsing and zero-copying of objects. 5. The odd Redis persistence m…

I've always loved your LOAD81 project and would encourage you to return to it and add some new features - so maybe how you made it, what it can be used for, how you can extend it by adding functionality .. ? EDIT: I know its not as sexy as your Redis work, but I think there are a lot of wise nuggets in this project that other developers could learn from.

http://github.com/antirez/load81.git

Post reply on HN