• Nick Smith

    Nick Smith

    2 years ago
    Disregarding performance or implementation concerns, is self-describing data the way to go? Is there a conceptually "nice" approach to encoding the meaning of data other than composing it from well-defined attributes? Do schemas have any purpose beyond acting as a "type system" and a data compression technique? Should every piece of data in a programming system be self-describing? We can compress away the redundant descriptions within collections.
    Nick Smith
    gman
    +2
    14 replies
    Copy to Clipboard
  • e

    elbear

    2 years ago
    is there anyone familiar enough with OpenAI’s GPT-3 to tell me if you can use it in this way: You feed it a text and then ask it questions about the text in the form: • How do I do X? • What are the main concepts present in the text? I’m thinking of something like Progressive Summarization: https://fortelabs.co/blog/progressive-summarization-a-practical-technique-for-designing-discoverable-notes I hope my question makes sense
    e
    1 replies
    Copy to Clipboard
  • r

    Ricardo A. Medina

    2 years ago
    What are good related podcasts you've listened to? (aside the FoC one, of course) I can recommend Meta Muse. https://twitter.com/MuseAppHQ
    r
    Ray Imber
    +1
    4 replies
    Copy to Clipboard
  • jarm

    jarm

    2 years ago
    Hybrid Live Coding Interfaces: performance & craft Workshop day 1/2 Live streaming today 4pm UTC on the ICLC YouTube channel: http://youtube.com/watch?v=SFb677O7D6A Full programme: https://hybrid-livecode.pubpub.org/workshop2020
    Hybrid Live Coding Interfaces: performance and craft
    
    Workshop day one (UTC)
    
    Session 1 - Instruments #1
    
    16:00   Rafaele Andrade
    16:15   Magno Caliman
    16:30   Evan Raskob
    16:45   Ivan Abreu Ochoa
    17:00   Anne Veinberg & Felipe Ignacio Noriega
    17:15   Break
    
    Session 2 - Heritage algorithms
    
    17:30   Tincuta Heinzel
    17:45   Karitta (Kit) Zellerbach
    18:00   Paola Torres Núñez del Prado
    18:15   Victor Zappi
    18:30   Discussion
    
    19:00   End of Day 1
    jarm
    1 replies
    Copy to Clipboard
  • jarm

    jarm

    2 years ago
    jarm
    1 replies
    Copy to Clipboard
  • opeispo

    opeispo

    2 years ago
    It’s been really nice learning and interacting with all of you. So many interesting perspectives! What are the most influential things that you have read or watched or done and would recommend?
    opeispo
    Chris Knott
    +9
    18 replies
    Copy to Clipboard
  • gman

    gman

    2 years ago
    gman
    Dan Cook
    2 replies
    Copy to Clipboard
  • curious_reader

    curious_reader

    2 years ago
  • Kartik Agaram

    Kartik Agaram

    2 years ago
    @yoshiki's https://www.notion.so/Dango-b46c07f3dc224f968c768885abe70e70 deserves more eyes than it would get when buried deep in a comment thread. Original context for the curious: https://futureofcoding.slack.com/archives/C0120A3L30R/p1595894934187200?thread_ts=1595738168.147900&cid=C0120A3L30R (I'd love for more people to hoist great comments by others to the top-level, as a sort of counter-force to always responding within-thread.)
    Kartik Agaram
    Ryan King
    +2
    6 replies
    Copy to Clipboard
  • ogadaki

    ogadaki

    2 years ago
    Somewhere else in this Slack, @Stefan wrote:
    I love seeing apps experimenting with what touch and mobile can add to traditional workflows instead of just looking at its limitations.
    Every time a new “future” of coding app is presented, and it only works with mouse and keyboard and requires a large screen I’m a little sad of the missed opportunity.
    Interesting topic, that I'd like to bike-shed think about together. I fully agree that touch devices and small screen devices are opportunities to imagine new way for programming. But I feel that it is quite hard to address. In particular small screens. Even with text programming, I always feel the need for a big screens. I can't imagine doing this on a phone. And for visual programming, having large screen make it possible to adopt some "map kind" organisation of your programming artifacts, to have nice global view of what your are doing. And something that is challenging, it to design visual representation/manipulation that works well for both large screen/keyboard'n mouse and small screen/touch. What do you think of that? Is there some examples of programming environment that succeeded in this space?
    ogadaki
    opeispo
    +7
    21 replies
    Copy to Clipboard