cdo256 | 6 years ago | on: Autocomplete as an Interface (2015)
cdo256's comments
cdo256 | 6 years ago | on: Autocomplete as an Interface (2015)
start writing loop, realize I need another variable, go back and initialize the variable, back to where I was, oh this should be brought out into a function, ah this function should is now getting quite large I need to split it, back to where I was, oh that should be an array not a map etc.
I like Visual Studio's 'jump back to where I was' (Ctrl+-) feature because it leaves a trail of bread crumbs across the many files I'm working in of what I've been doing and what's left to be done to implement feature x.
cdo256 | 6 years ago | on: Autocomplete as an Interface (2015)
Both of these could be achieved by somehow decoupling the front-end (as in before semantic analysis) of compilers and making them output the AST in some standardized tree-structured format like XML.
cdo256 | 6 years ago | on: Autocomplete as an Interface (2015)
Once you get familiar with a particular editor then these problems become less acute. What remains is the obscuring of other lines of code which can be fixed by making the autocomplete box only appear when you press tab.
cdo256 | 6 years ago | on: An ant colony has memories its individual members don’t have (2019)
In the second book, her brain is then duplicated across multiple colonies. Because the ant computer isn't as powerful as silicon based computers, one of her instances later realizes that she is a significantly compressed version of herself and that she doesn't have most of the old memories, capabilities or capacity for emotions that her human self had, presumably in large part also due to being transferred between three different substrates (flesh, silicon, ants).
[1] https://www.goodreads.com/book/show/25499718-children-of-tim...
cdo256 | 6 years ago | on: An ant colony has memories its individual members don’t have (2019)
If you're referring to anything your parent mentioned, those tools already exist.