I just discovered this great video where Brian #Kernighan tells the story of how the #Unix command #grep came into existence. This story includes notable mentions of Ken Thompson and Dennis Ritchie.

https://www.youtube.com/watch?v=NTfOnGZUZDk

#VintageComputing

"Everyone knows that #debugging is twice as hard as writing a #program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" - Brian #Kernighan

#software #development

Coding wise words: are you smart enough for your own code?

(taken from Timothy Appnel's recent blogpost "The Zen of Ansible")

#coding #zen #kernighan #ansible #python #redhat #opensource

How much is a good #layout worth?

“Our #studies support the claim that #knowledge of #programming plans and the #rules of programming discourse can have a significant impact on program comprehension. In their #book called [The] Elements of [Programming] Style, #Kernighan and #Plauger also identify what we would call discourse #rules.”

By popular demand, I have scanned my copy of Draft #1 of #Kernighan and #Ritchie's C Programming Language book. Here: https://drive.google.com/drive/folders/1OvgKikM8vpZGxNzCjt4BM1ggBX0dlr-y #ComputerHistory #UNIX #CLang

@aka_pugs
Cool artifact. I've really enjoyed Brian Kernighan's videos on the Computerphile YouTube channel. Here's a playlist:
https://www.youtube.com/playlist?list=PLzH6n4zXuckqZ90zLyy36qjO5YIn1RulG

#Computerphile #Kernighan #TechHistory

@PeterSommerlad @derkern @szczezuja I literally have a copy of #Kernighan's "UNIX: A History and a Memoir" sitting on my desk in my to-read stack, one which sadly seems to be growing faster than it is shrinking! Thanks for sharing; those are names I recognize (and interesting being drafted to do programming!)

I was stuck when I visited the computing history museum at #BletchleyPark how different computing hardware was in US vs. Europe until the 90s. A lot of stuff there I'd never heard of.

Still handing out the advice that Brian W. #Kernighan put out in 1974 about preparing documents and line feeds:

»
Most documents go through several versions (always more than you expected) before they are finally finished. Accordingly, you should do whatever possible to make the job of changing them easy.

First, when you do the purely mechanical operations of typing, type so subsequent editing will be easy. Start each sentence on a new line. Make lines short, and break lines at natural places, such as after commas and semicolons, rather than randomly. Since most people change documents by rewriting phrases and adding, deleting and rearranging sentences, these precautions simplify any editing you have to do later.
«
~ BWK, UNIX for Beginners, 1974

It's so incredibly useful, especially when working with version control that's using line-based diffs (such as #git).

#UNIX #Markup #Markdown #LaTeX #TeX

Coffee with Kernighan

https://hackaday.com/2022/08/24/coffee-with-kernighan/

#computerhacks #computerphile #Kernighan #unicode #awk

@celia@fosstodon.org A recommended reading in that regard would be "The #UNIX Programming Environment" by #Kernighan/#Pike. That stuff is from 1983 (so much for longevity) and it is still... enlightening.

@dataKnightmare

Brian #Kernighan is going to talk at Turin during the Festival della Tecnologia.

https://www.festivaltecnologia.it/sessioni/milioni-miliardi-fantastiliardi-come-difendersi-un-mondo-pieno-di-numeri

Brian Kernighan explains
Where GREP Came From
https://www.youtube.com/watch?v=NTfOnGZUZDk
#grep #Kernighan

#aérospatiale #espace #Apollo

Le code source des programmes de guidage du module de commande et du LEM d'#Apollo11 est disponible sur #Github.

C'est juste pour regarder parce que c'est de l'assembleur dont la #NASA a benné les docs.

(oui #Kernighan, #Ritchie et #Thompson ne bossaient pas pour la NASA mais pour Bell Labs et, de plus, le PDP-7 ne rentrait ni dans le LEM ni dans le MC)

➡https://github.com/chrislgarry/Apollo-11