7) lastly, don't worry about making a mess. mess is just the evidence that you've done a ton of work and explored every path you could think of.
6) it helps a lot to start drawing in figma before writing any code to test visual ideas. many times i have used the document structure exported from figma to kickstart in-code prototyping.
5) going back to 2.5.... the /*svg*/ in front of the template string may be a small detail but it makes this way of doing things tolerable. in vscode, i use the `es6-string-html` extension.
3) have a plan for how to source randomness with solidity. i like generating a seed and passing it throughout the code. the benefit of this method is determinism. 4) get really familiar with svg, how the paint model works, how groups work and obviously the basic attributes of each tag.
so what should you do? 1) ask gpt for an html file template. you'll have many such templates as you try ideas (most will be bad) and explore. 2) almost without exception, programatic elements can be written as functions which return template strings. 2.5) for example:
don't use react, static site generators or svg libraries like svg.js. you'll have to learn those and again that will slow things down.
first, in most cases, ignore solidity. solidity comes with constrains that are detrimental to the speed of rapid prototyping. i prototype in js.
some thoughts about whats become my favorite way to prototype generative svgs for onchain deployment
posting on warpcast feels safe, isolated, calming. posting on warpcast dot com on the other hand
This is why engineers should be kept in the office basement and never allowed to interact with anyone at the company except via kanban board. Thank you ChatGPT for making this dream a reality.
Any activity, tool or object that gets in the way of achieve some form of higher effect in the world is a total waste of time and every time people on Tw*tter prostrate themselves over Vercel or fucking edge functions or something is another 40 brain calories dissipated out into the universe to achieve exactly nothing.
Which is not to say that tools aren't helpful or important. Obviously they are. Anything that clears the way materially, psychologically or emotionally is acceptable to use. Anything that gets in the way or blocks free motion in your creative process should be thrown out.
I like making things first and foremost. I don't really 'like' programming or design because most of these tasks are extremely rote and I imagine in the future I'll like them even less. Every time people debate tools (tailwind etc) I just think to myself that these people don't actually like making things.
I hate AI 'art', but using AI in earnest in a code environment is so incredibly OP that it boggles my mind weekly