Rabidgremlin

For some very basic level protection use devcontainers and install the agent into that....

A better approach is to use the Docker Sandboxes feature. Locks things way down so that the agent only has access to the files you give it and you can lock down its network access too. Also does things like keep any credentials outside of the container (microvm actually).

Yep it is Bootstrap. Well bootstrap-react to be more precise.

The site was actually built as an experiment on "spec first" coding with AI agents... in this case using Codex CLI. Underlying tech is Typescript, React, Zustard (for state), Bootstrap (for layout/components) and Konva JS (for 2D canvas) and vite for building/bundling. Deployed to AWS S3 bucket fronted by AWS cloud front using Github actions.

I'm planning on adding a video.

Welcome to a whole new obsession!

Nice idea. Will add it to the list

Yeah... I had that tabs/slots and STL on my list but lot priority

It does snap but it was a bit iffy. I have improved it so give it a try.

Re SVG export it is on the list.

Yeah, foam core is easy to work with but a bit thick. The tool does let you set the thickness in the project properties so you may be have some luck setting it to be thinner.

I'll hopefully get a video up soon

Interesting idea. Definitely something I could add.

yep, agree

It should hopefully work better on a phone/tablet now. I'm planning on adding a video soo showing how to use the app and what it does... but you can check out https://www.reddit.com/r/boxinsertdesigner/ for examples

eek, I forgot I had posted here and got distracted with the holidays.... will start to respond now..

If he wants to advance in the game space then he can either keep in the "visual coding" area using something like https://www.construct.net/en or start heading down the text coding path with https://godotengine.org/ or https://www.lexaloffle.com/pico-8.php

100% agree with you... taking the time to do/go design first greatly improves the quality of the final API...

But as some comments below point out, an OpenAPI spec is a pain to create manually which is why TypeSpec from Microsoft is such a great tool. Lets you focus on the important bits of creating a solid API (model, consistency, best practices) in an easy to use DSL that spits out a fully documented OpenAPI spec to build against! see https://typespec.io/

mmm, I have it on disk from a POVRay book I bought like 20+ years ago.... I wonder if the Internet Archive has it ???

I have a bunch of plant examples here http://blog.rabidgremlin.com/tags/l-systems/

I've had an "architect" job in some form or another for 20+ years, so have learnt plenty of things that would have greatly surprised my younger self...

My day job is basically to be a "force multiplier" and it boils down to:

- cat herding = meetings, discussions, negotiation, "shoulder to cry on" = way more soft skills then I ever thought I'd need

- Big picture stuff = "town planning" for tech, second order thinking, pulling together cohesive plans/strategies, principles, constraints = way harder to effectively communicate this stuff than my younger stuff would have thought

- rapid altitude changes = dropping from the 10000ft view down to helping a team troubleshoot some production issue, helping a junior dev with a code issue, solving a dispute between devs, hands on evaluation of some new tech, then jumping back up to talk to a leadership team about some new grand strategy, or to planning out a multi year program of work = a ton of skills that my younger self would have never have guessed at, finance, budgets, "business" language, operating models along with keeping my technical skills sharp

In terms of resources:

- Anything around learning to story tell and communicate effectively

- The "97 Things Every Software Architect Should Know" essays

- Your tech skills - write PoC apps, side-projects, try out new tech, learn to quickly grok strengths & weaknesses of tech

I did the same thing on a road trip when I was bored... Worked really well.. created a video on the experience https://youtu.be/FxQpRoZI3kM

* The Web didn't really exist so no phoning a million stackoverflow friends for help and code snippets. So...

* Reference manuals shipped with compiler and good reference books were gold

* You could learn the entire API/SDK/Framework and keep it in your head

* Blocks of assembly were a legit way to improve your code's performance

* OOP was hitting mainstream along with all the new ideas and approaches (and pain) it entailed

* Turbo Pascal rocked for DOS development

* Source control was iffy/non-existent

* I loved it

Sounds like an Omega Race clone/variant

A mix of stuff. Being coding 40+ years, 30 of those as a job. Currently I do 3 days a week working as a solutions architect, herding cats for a large grocery chain. 2 days a week I work for an R&D team for a company building digital people, doing hands on coding, ML, NLP etc etc... hence the talking to robots :)

Apparently I "sit in my office and talk to robots all day" according to my slightly scathing 10year old son.

Is this issue also related? https://github.com/explosion/spaCy/issues/9606

TIC-80 isn't quite as refined as PICO-8 but its still pretty awesome. A few months ago I figured out how to setup TIC-80 so I could code on my mobile whilst on the move: https://www.youtube.com/watch?v=FxQpRoZI3kM

Interesting... Thanks

Any ideas around what could be leveraged here with docker? I'm thinking it would be great to have all dev tooling + IDE bundled into containers for quickly switching projects/ getting devs up to and running fast.

I like it!

Unfortunately not :(