Closed marianoguerra closed 4 years ago
🎥 2 Minute Week for 2020-07-06 by Robert Butler 🧵conversation
Here is my first 2-minute week video for uCISC, my CISC instruction set designed for homebrew computers. It's a little strange because this is a bit more than a week of work since this is my first one, but hopefully it gets it started and I can post every week now on smaller increments of progress.
🎥 Week 28 - Future of Coding demo by Steve Peak 🧵conversation
Here is Storyscript’s first 2 minute demo — This demo showcases one of many aspects of our editing experience. Topics: NLP, ML, no-code. Goal: Dialog-based development by understanding intent into a program and understanding ambiguity through holes.
Quote from Program Synthesis by Microsoft research team
this problem has been considered the holy grail of Computer Science.
🎥 Future Of Coding, Week 12 by Chris Maughan 🧵conversation
I integrated the synthesizer and graphics this week. It is nice to have the graphics code up and running again, even if I will be changing it when I get chance.
💻 codeBERT: automatically review Python code documentation (docstring) via Maeliza 🧵conversation
This is all part of a longer-term ambition: automatically document any source code. This is our plan: ✔ automate source code mining with tree-hugger ✔ masked language model trained on source code (Python) with codeBERT MLM ▶ fined tuned language model to analyse docstring vs function definition (Python) - and improve it ⏺ extend model to different languages
💻 Monospace or proportional fonts, which are better for coding? I'd say, why not use both? via Felix Kohlgrüber 🧵conversation
It's a simple text editor that uses different fonts depending on the type of syntactic element (e.g. comments use sans-serif, punctuation uses monospace). The experiment is online so that you play around with it and I've even managed to write some text about the experiment this time.
📝 Micro-Versioning Tool to Support Experimentation in Exploratory Programming via yoshiki 🧵conversation
Recently discovered this prototype of micro-versioning:
Experimentation plays an essential role in exploratory programming, and programmers apply version control operations when switching the part of the source code back to the past state during experimentation. However, these operations, which we refer to as micro-versioning, are not well supported in current programming environments. We first examined previous studies to clarify the requirements for a micro-versioning tool. We then developed a micro-versioning tool that displays visual cues representing possible micro-versioning operations in a textual code editor. Our tool includes a history model that generates meaningful candidates by combining a regional undo model and tree-structured undo model. The history model uses code executions as a delimiter to segment text edit operations into meaning groups.
📝 https://github.com/kiselgra/cm-fop via S.M Mukarram Nainar 🧵conversation
This reminds me of your code organization scheme, with the feature splicing and stuff, though their focus is more on outputs than inputs—they ended up with this by optimizing for exploratory programming with heterogenous outputs, not readability/understandablity. I think it goes to show how much overlap there is between those goals—maintaining understanding of a codebase is a key part of enabling exploration. I'd never heard of feature-oriented programming before, but it's neat
❓ Harry Brundage 🧵conversation
Is anyone aware of a good meta-analysis on why node and link based programming has only found limited success?
💭 Bret Victor's Quote via Mariano Guerra 🧵conversation
Interface matters to me more than anything else, and it always has. I just never realized that. I've spent a lot of time over the years desperately trying to think of a "thing" to change the world. I now know why the search was fruitless -- things don't change the world. People change the world by using things. The focus must be on the "using", not the "thing". Now that I'm looking through the right end of the binoculars, I can see a lot more clearly, and there are projects and possibilities that genuinely interest me deeply.
When you are beyond the prototyping stage and start to put together an early version of something you intend to use yourself extensively and probably also give to a small number of people to try out, what are the measures you take and practices you follow to make that a great experience? For instance, what do you do to make sure data isn‘t reset or lost between updates or can be migrated easily?
📝 As We May Code via Stefan Lesser 🧵conversation
What if, instead of lowering source code down for the purpose of execution, we raised source code for the purpose of understanding?
What if we took the lessons of the semantic web and applied them to source code?
One way to categorize FoC projects is to consider the following spectrum. (Go with me here — resist the urge to treat this as a multidimensional space.)
In the center, we have projects that resemble typical programming languages. These tools are designed with particular semantics that the programmer will employ to structure their problem solving. They are general purpose. They don't have much regard for the particular kinds of problems being solved. This is your Java, Clojure, Vulkan, brainfuck, etc.
Off to one side, you have programming tools that have both tightly defined semantics and a focus on solving particular kinds of problems. These are specialized. This is Excel, Notion, Max/MSP, OpenGL, bash, etc.
Off to the other side, we have programming tools that, while they still have semantics, don't expect you to work entirely within those semantics. They have even less regard for the problem domain. These are tools that expect you to first build some new tools from or within them, then solve your problem with those tools. This is Racket, and arguably REST, RDF, stored procedures in a DB, and other things.
Now my question: are you building an FoC project that falls into the latter category? If so, talk about that a bit. What's the rationale?
🎥 "Evidence-Oriented Programming" by Andreas Stefik via Xandor Schiefer 🧵conversation
🎥 UIKonf 2019 - Julia Roggatz - Muse Prototype Challenges via Garth Goldwater 🧵conversation
This video has it all: a really cool app, a discussion of interface philosophy and decisions, and engineering roadblocks at the edge of performance
❓ Tor 🧵conversation
What are some good resources around the power imbalance in the interaction of software and users? For example, the disregard for consent in a dialog box where the option “No” is replaced with “Not now”.
📝 Rebol Concepts via Garth Goldwater 🧵conversation
finally found a blog post about rebol/red that communicates some of what I suspected was interesting about it: http://www.codeconscious.com/rebol/articles/rebol-concepts.html. in particular: the body of a function and its argument list are just data structures. so you can use them as first-class citzens as you like. please let me know if any of you know of any other languages with this level of flexibility!
This issue collects resources for the newsletter of the year/month/week that should be in the title
If you want to contribute open the issue and paste a resource you think is worth sharing in the newsletter and comment on the issue of the week.
Use markdown for formatting, ideally a contribution should have a title a link and optionally a description.
Add emojis to signal videos 🎥 article 📝 demo 🎮 thread 🧵 audio 🎧 twitter 🐦 idea 🧠 podcast 🎙️
Use comment reactions on issue comments to up vote/down vote/whatever each submission the reactions that have a clear sense of positive/negative will be considered to rank the submissions of the week.