Hello. My name’s Sam and I’m from Columbus, Ohio. I’m a software engineer mainly working in binary analysis.I just found this group through a 100r podcast about making your own tools and I had to see what its all about.I enjoy all facets of computing but I mainly find myself reverse engineering these days. I’m currently working on reverse engineering the Wacom tablet driver to create my own (I know these already exist but I enjoy going through the process myself).I’m looking forward to exploring this community and hopefully meeting like-minded people. Cheers.
Hi everyone! I’m Katie, a software engineer from Sydney, Australia. I got introduced to this community because someone shared a video of my talk here (
) about the building a visual programming interface (it’s not about Scratch as the thumbnail would have you believe), and a few people reached out to me from that! It’s awesome to find so many like-minded people who are working on cool things. 😁
Greetings from Gothenburg, Sweden! I started coding in Amiga Basic as a 10-year old, and professionally since 2000, mostly web, C++ and graphics. Although I always loved programming, I also always strongly felt that there has to be a better way than the status quo. Frustratingly, my teachers, colleagues & peers didn't seem to care. When I finally found Bret Victor's work, it felt like a huge validation - "I'm not alone, I'm not crazy, someone else gets it too!"Consumed the Future of Coding site in "read-only mode" for years (thanks for the great content, Steve!), but I didn't join the community in read-write mode until now that I have something substantial to contribute - coming soon in the #share-your-work channel.Interested in everything, but with a special focus on:* Visualization - as in revealing the shape and size of abstract things clearly,
not just giving bar charts a sci-fi look* User interface design - really unhappy with current mainstream trends, UIs ought to empower users rather than dumbing things down
* Pipe dreaming of redesigning OSes, the internet and the web stack from scratch with the benefit of hindsight
* ... but also charting realistic incremental improvements
* Green/environmental issues - neither hardware nor CPU cycles are free, make sure they carry their weight
Hi everyone. I’m Francois. Here’s what I’m working towards. It is called Gooey. I'm going to blather a bit here, to see if any of my background is interesting for context.My background is in making design/dev tools, platforms, and of course just making experiences. I was a game developer for the first 10 years of my career and then went on a decade run of doing startups. I work at Bose having done Applied Research in the XR/tools space for the last 3 years and now am being promoted into running all Software Incubation within our investment arm. Lately I've been more seriously experimenting and discussing getting funding to start a company around this space. I can't share too much just yet, until I either get a legal waver from Bose Legal, and finish some discussions on potentially spinning out from Bose. I want to work on this no strings attached though.Gooey's rough description and direction is: using game engine/editor technology but applied to refining and communication concepts to others. I'm a fan of a tool that is browser first and am pursuing that approach. I think highly baked in social features is extremely important. Figuring out how to make securely re-mixable components that will have access to often personal or professional data is top of mind. Other things I'm interested in:
How do you make interactive design code/assets that will still be runnable/loadable/useful in a decade (not be dependent on likely to go away environments like APIs)
Figuring out which is more optimal: being the whole runtime/IDE stack, being a more clean embedded runtime, or being more of a file-format/protocol.
Is there a conflict between learnable and powerful?
Creators can easily make an ecosystem of hard to understand building blocks and processes, is there something that can be done to help grow a culture of caring about crafting good remixable components such as static analysis or badges/scores marked by each component?
Should I make a new programming language or try to tame existing languages with some editor enforced invariant enforcement?
Ensuring components are say functionally pure, or a DAG, and/or deterministic for instance can lead to some serious optimizations, cleaner implementation, and I think learnability.
I'll stop there, I've thought about this for almost 15 years, so I could talk forever.I'd like to build a sustainable/high-profitable company so I can have a healthy amount of funding to pursue necessary research with smart collaborators. I'm struggling with how to balance wanting to make something open source. I'd say I really like Figma's approach of just making something awesome people want to pay for, being a relatively open company sharing their design thinking, and of course I think the CTO making cool shit for the community (such as in esbuild). This makes me feel like Figma gives back to the community. Of course there is plenty of space for a magnitude more of giving back and being transparent, which is where I'd hope to fall. It's all easier said than done to make sure you aren't a starving idealist/artist.My favorite company overall though (and I find this funny, after all of the hate I had when they were trying to kill the browser) is Microsoft in terms of vision for enabling developers both profitably and in giving back a lot with awesome open source projects. Github is in my opinion, the most well designed product ever.