react-app-boilerplate VS scaffold-eth

This comment comes from a lot of iterations in both my work and personal projects. It's my opinion that anything modified or imported is "source code" and should this be in src/. Frankly, most of the community disagrees which is why public/ exists in the first place. Even that page you linked, while it does specify index.html should be separate, still implies index.html is a part of source code and IMO should be treated as such. Maybe it was premature for me to bring this up, but it's why I put index.html, favicon, and others in src/ in my React boilerplate repo repo. Just one of those "at discretion of the dev" type of things.

Personally, I don't like having to download files and hiring managers/interviewers have even less desire since they're usually in a rush and interviewing many candidates. I'd suggest converting your resume download button to a PDF-viewer hyperlink (e.g. Google's built-in viewer). That way, people can view your resume without having to download it while still giving them the option to download it. Or, if you want the resume to stay on your site instead of a new tab, you could always embed it instead.

Specifically, if I have particularly important, detailed, and informative information about a change, it should be saved somewhere (Jira, docs, comments, git messages, pick your poison). Assuming that "I named my variable well so everyone will always understand the tens of concepts around my thinking process" is incredibly short-sighted and will result in a bad team experience. It has to be documented somewhere. IMO git commit messages are the best b/c you can easily git blame any line in an IDE and know exactly why that line was changed, removing all relation to other lines' changes.

Scaffold ETH: https://github.com/scaffold-eth/scaffold-eth

Can't wait for it to be released tbh, we won't really know how the market will utilize it until its full released! are there beginner friendly tools / examples like scaffold for ETH? https://github.com/scaffold-eth/scaffold-eth

For another method to set up a DApp, check out Scaffold-ETH by Austin Griffith. You can also get great DApps examples with BuidlGuidl.

hm creating your own crypto token is a smart contract, its just a standardized set of classes, modify the classes and see what happens

anyway try https://scaffoldeth.io

you compile the tutorial website first and then build a bunch of common smart contract scaffolding

note this is the EVM ecosystem so it would be impossible to conflate example in pure BTC, smart contracts are playing catchup in BTC ecosystem. a couple competing attempts there.

My friend is still in the space and his main mission is to onboard new developers into Ethereum. He has a project called Scaffold-ETH which is a quick start template for Ethereum development. This Next.js Ethereum Starter is my interpretation of his project.

I'm experimenting and I don't want to use opensea or similar platforms. I just want to create an NFT with an image I uploaded to IPFS, offer it to close friends and then renounce ownership to make it truly immutable (sorry if that's stupid, I am learning) I used https://github.com/scaffold-eth/scaffold-eth tutorial and I already minted on Polygon Mumbai testnet. It has a script to run every time I want to mint, but I want to bulk mint 100 NFT's (same artwork).

For example, Scaffold ETH helps quickly start building and prototyping on the Ethereum blockchain. It provides tutorials and libraries to make DeXs, NFTs, multisig wallets, smart contracts, etc.

and Austin Griffit’s famous Scaffold Eth: https://github.com/scaffold-eth/scaffold-eth

https://github.com/scaffold-eth/scaffold-eth in combo with https://speedrunethereum.com/