nhaliday + heavyweights + summary   5

Peter Norvig, the meaning of polynomials, debugging as psychotherapy | Quomodocumque
He briefly showed a demo where, given values of a polynomial, a machine can put together a few lines of code that successfully computes the polynomial. But the code looks weird to a human eye. To compute some quadratic, it nests for-loops and adds things up in a funny way that ends up giving the right output. So has it really ”learned” the polynomial? I think in computer science, you typically feel you’ve learned a function if you can accurately predict its value on a given input. For an algebraist like me, a function determines but isn’t determined by the values it takes; to me, there’s something about that quadratic polynomial the machine has failed to grasp. I don’t think there’s a right or wrong answer here, just a cultural difference to be aware of. Relevant: Norvig’s description of “the two cultures” at the end of this long post on natural language processing (which is interesting all the way through!)
mathtariat  org:bleg  nibble  tech  ai  talks  summary  philosophy  lens  comparison  math  cs  tcs  polynomials  nlp  debugging  psychology  cog-psych  complex-systems  deep-learning  analogy  legibility  interpretability  composition-decomposition  coupling-cohesion  apollonian-dionysian  heavyweights 
march 2017 by nhaliday
The Setup / Russ Cox
I swear by the small Apple keyboard (in stores they have one that size with a USB cable too) and the Evoluent mouse.


I run acme full screen as my day to day work environment. It serves the role of editor, terminal, and window system. It's hard to get a feel for it without using it, but this video helps a little.

Rob Pike's sam editor deserves special mention too. From a UI standpoint, it's a graphical version of ed, which you either love or hate, but it does two things better than any other editor I know. First, it is a true multi-file editor. I have used it to edit thousands of files at a time, interactively. Second, and even more important, it works insanely well over low-bandwidth, high-latency connections. I can run sam in Boston to edit files in Sydney over ssh connections where the round trip time would make vi or emacs unusable. Sam runs as two halves: the UI half runs locally and knows about the sections of the file that are on or near the screen, the back end half runs near the files, and the two halves communicate using a well-engineered custom protocol. The original target environment was 1200 bps modem lines in the early 1980s, so it's a little surprising how relevant the design remains, but in fact, it's the same basic design used by any significant JavaScript application on the web today. Finally, sam is the editor of choice for both Ken Thompson and Bjarne Stroustroup. If you can satisfy both of them, you're doing something right.


I use Unison to sync files between my various computers. Dropbox seems to be the hot new thing, but I like that Unison doesn't ever store my files on someone else's computers.


I want to be working on my home desktop, realize what time it is, run out the door to catch my train, open my laptop on the train, continue right where I left off, close the laptop, hop off the train, sit down at work, and have all my state sitting there on the monitor on my desk, all without even thinking about it.
programming  hardware  plan9  rsc  software  recommendations  techtariat  devtools  worse-is-better/the-right-thing  nostalgia  summer-2014  interview  ergo  osx  linux  desktop  consumerism  people  editors  tools  list  google  cloud  os  profile  summary  c(pp)  networking  performance  distributed  config  cracker-prog  heavyweights  unix  workflow 
july 2014 by nhaliday

bundles : meta

related tags

:)  aggregator  ai  analogy  anglo  announcement  aphorism  apollonian-dionysian  art  backup  beauty  big-surf  books  britain  c(pp)  checking  classic  cloud  cog-psych  comparison  complex-systems  composition-decomposition  confidence  config  consumerism  coupling-cohesion  cracker-prog  cs  data  dataviz  debugging  deep-learning  design  desktop  devtools  differential  discipline  distributed  early-modern  editors  elegance  epistemic  ergo  essay  exocortex  explanation  feynman  fiction  finiteness  flux-stasis  form-design  forum  frontend  geometry  giants  google  gowers  gwern  hardware  heavyweights  history  hn  info-foraging  internet  interpretability  interview  latex  learning  legibility  lens  lesswrong  linux  list  long-short-run  longform  math  math.CA  mathtariat  mechanics  meta:prediction  meta:reading  mindful  minimalism  multi  networking  nibble  nlp  nostalgia  notation  notetaking  org:bleg  org:edu  org:junk  os  oss  osx  papers  pdf  people  performance  philosophy  plan9  planning  polynomials  priors-posteriors  profile  programming  project  psychology  questions  quotes  r-lang  rationality  ratty  recommendations  reflection  retention  rsc  scifi-fantasy  sequential  software  spatial  spreading  subculture  summary  summer-2014  talks  tcs  tech  technical-writing  techtariat  the-classics  the-great-west-whale  time  time-series  tools  unix  vcs  virtu  visual-understanding  visuo  vulgar  web  wire-guided  workflow  worrydream  worse-is-better/the-right-thing  writing  yak-shaving 

Copy this bookmark: