RT @stevekrouse: @spiralganglion 💕 “The system should do as much as it possibly can to stay alive and produce behaviour. Types are just som…
Notes
Reposted by Steve
Text may be partial · Read original
- @spiralganglion 💕 “The system should do as much as it possibly can to stay alive and produce behaviour. Types are just some feedback.” 💕
- 18/ We will create a world where a single person can know all possible states of their software
- 19/ I will not live in this world. My kids will not live in this world. But maybe their kids will live in a world where nobody asks “have you tried turning it off and on again?”
- 17/ We will have succeeded when A SINGLE MERE MORTAL can come to understand ANY PART OF A LARGE APP THEY WANT TO in an amount of time proportional (not exponential) to the ESSENTIAL COMPLEXITY of that part
- 15/ We must invent an alternative to reading code line by line.
- 16/ We need programming tools that can tell you which parts of the code you NEED TO READ and which parts you can SAFELY IGNORE to understand the piece you are currently investigating
- 13/ What’s the fix? Same as the environment: remove the polluting tech and replace with clean tech.
- 14/ Goto is harmful. So are a lot of other things: statements, side-effects, mutation. Delete those things from programming and invest in their replacements.
- 11/ Our programming languages are too messy and powerful. Anything can happen on any line of code. It’s impossible to tell what affects what with certainty.
- 12/ As @girba says, software has a crisis in the exponential growth of lines of code outpacing our linear reading abilities. We are saddling our children with technical debt as surely as we’re saddling them with environmental carbon debt
- 9/ Contrast this to a building or a bridge which would not suffer if its creators left. Others could figure it out from plans and inspection, and take stewardship
- 10/ Not so in software.
- 7/ You protest, “If this is so, how do things work as well as they do?”
- 8/ People. The knowledge is distributed in the thousands of programmer heads. If all those people died, we’d be blind
- 5/ One cannot simply read all the code. There are millions of lines. It would take lifetimes.
- 6/ Yet there are no alternatives to understanding code than reading it line by line. If you skip a single line, you could misunderstand it entirely
- 4/ There are many who understand teeny weeny pieces. But the whole is uncomprehended because it is INHERENTLY INCOMPREHENSIBLE
- 2/ Pick your favorite piece of software: instagram, docs, email, Twitter, the Tesla autopilot, whatever
- 3/ There is nobody alive who understands how that code works. Not a one.
- 1/ For fun I sometimes like to shock non-programmers about how utterly broken software development is... rant thread 👇
- Software is one of the few places where “legacy” is a bad thing @chadfowler http://youtu.be/YruzQgWdv48 https://x.com/jeremyjkun/status/1083795366795866119
- RT @amasad: Working on a generalized (efficient) checkpointing system for REPLs. Imagine time travel working on basically any language. htt…
Reposted by Steve
Text may be partial · Read original
- @ESYudkowsky @paulg I nominate @neurocy to defend Greek letters in CS papers!
- Going to ROME tomorrow! Anyone there? Any recommendations?
- @spiralganglion I dream of a world where type errors never prevent code from running. A strong type system will merely help your computer communicate to you the potentially undesirable, unforeseen consequences of what you’re asking of it
- @spiralganglion Intriguing! Does designing for misuse == designing for the unexpected uses?
- RT @spiralganglion: Is it possible to make a creative tool, or a learn-to-code tool, that is both strongly typed and allows for creative mi…
Reposted by Steve
Text may be partial · Read original
- RT @naval: 1/ If the primary purpose of school was education, the Internet should obsolete it. But school is mainly about credentialing.
Reposted by Steve
- RT @andrestaltz: When people feel horrified about the amount of tiny libraries in node_modules, I don't sympathize. I think it shows the…
Reposted by Steve
Text may be partial · Read original
- RT @pavel_bazant: Here is my preliminary list of sufficiently alien yet serious systems I intend to study in some depth: Symbolics Genera B…
Reposted by Steve
Text may be partial · Read original
- New #futureofcoding find: @valaatech 💕blurring the line between the front-end and back-end (a la Meteor) 💕visual programming 💕in-browser IDE 💕open source 💕their goal: democratizing programming a la Wikipedia and GitHub
- @spiralganglion @girba We talk about it on the podcast (to be released in the next week or so). I think I originally heard Tudor mention it in a talk online somewhere but I forget which one - sorry!
- RT @jaukia: If you are interested in programming tools and interfaces, I suggest joining the Future of Coding Slack community founded by @s…
Reposted by Steve
Text may be partial · Read original
- @igstan @girba Exactly!
- "We've forgotten what the I in IDE stands for: integrated. Whenever you leave the IDE, the I has failed." - @girba This includes all googling, Stack Overflow, online playgrounds (regex, flexbox, etc), and even online documentation!
- I'm don't know how you do happiness, but I do it very disorderly https://x.com/EvanSandhoefner/status/1083657035130974208
- RT @spiralganglion: Shoutout to @callmevlad — we have identical backstories! • Wanted to do 3D animation & work at Pixar because Maya is fu…
Reposted by Steve
Text may be partial · Read original
- RT @posobin: How different programming languages would be today if touch screens were used as a main source of input from the start, not ph…
Reposted by Steve
Text may be partial · Read original
- About to interview the wonderful @jonathoda! Tweet back if you have any questions or topics you'd like us to discuss