Closed marianoguerra closed 4 years ago
π¬ Steve Dekorte π§΅Conversation
If you feel (as Iβm guessing most of us here do) that software development hasnβt progressed very much in the last several decades, can you share any thoughts/theories you might have on why that has happened?
π¬ Ivan Reese π§΅Conversation
If you instead want to share thoughts about how software dev has made good progress in the past few decades, join my thread.
π¬ Jamie Brandon π§΅Conversation
... Specialization and economies of scale have been some of our main tools for progress. Maybe the future where programming only happens in thousand-person teams is the one where software works better? ...
π¦ Minimum viable browser quine. Via Christopher Galtenberg π§΅Conversation
π¬ Paul Butler π§΅Conversation
What are people's thoughts on the future of no-code platforms with regards to open source? These days as a developer I see that languages where the only compiler is proprietary are increasingly niche, while widely adopted languages have an open source stack. Will the same thing happen with no-code platforms, or are the dynamics different?
π¬ Jamie Brandon π§΅Conversation
What are people's thoughts on funding?
π¦ Penrose: from mathematical notation to beautiful diagrams. Via Chris Knott π§΅Conversation
Weβve been building a new tool called Penrose, which takes a big step toward automatically visualizing mathematics. You just type math notation & Penrose magically comes up with a visualization for you.
π’ 16th AAAI Conference on Artificial Intelligence and Interactive Digital Entertainment. Via Chris Martens π§΅Conversation
Please send us your games, weird art, and interactive widgets that are informed in some way by AI, by Friday, June 12!
Please consider submitting especially if you are not working in academia and/or if you are working with an arts/humanities focus. This track is a huge part of what makes AIIDE special, that we value many different forms of contribution.
β Will Crichton π§΅Conversation
Iβm researching the influence of working memory in program comprehension. Question for the community:
When youβre reading or writing a program, are there specific tasks/examples/etc. where you found it hard to remember things? Maybe you were flipping back and forth between documents, or you kept looking back to the definition of something.
π Soutei, a Logic-Based Trust-Management System. Via S.M Mukarram Nainar π§΅Conversation
Delightful application of PLT principles to solve an actual problem. Debugging unix permissions problems is going to be more painful in the future because I'm always going to think back to this.
π Unker Non-Linear Writing System. Via Michael Donatz π§΅Conversation
This is what I want to see from a programming language
π’ Will Crichton π§΅Conversation
Given recent events (as well related discussion of lack of diversity in FoC), I just wanted to mention
Now is a good time to reflect on what role people of color can and should play in the future of coding.
That starts with understanding the relationship of technology and race.
I can recommend several great examinations of this topic in the HCI community:
- Does Technology Have Race?
- Critical Race Theory for HCI
- Not strictly race-related, but Morgan Ames also has some great work in critically analyzing hacker culture and techno-utopianism in education policy
π₯ Neural network to translate abstract syntax trees into images. Via noahtren π§΅Conversation
I've been working on a deep learning project that feels relevant to this community, and would love to hear some of your thoughts. I'm training a neural network to translate abstract syntax trees into images (and then back into ASTs since the whole system is an autoencoder.) Right now this is limited to simple arithmetic statements like c / (a+b), but the goal is to try it out on larger expressions with a greater vocabulary, so that you can turn larger ASTs into images. In addition to being really fun and interesting, it feels like it could offer ideas for visual programming? Visualized here is an interpolation between different expression trees. Still kind of rough around the edges.
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.
Post helpers: https://marianoguerra.github.io/future-of-coding-weekly/helpers.html
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.