create-eth-app VS react-app-boilerplate

It's a vague question but my goto is to create a basic site with create-eth-app (similar to create-react-app, but for ethereum) https://www.npmjs.com/package/create-eth-app

But I've probably seen more jobs looking for more "standard" frontend work on websites and apps - primarly javascript based on react or maybe vue. I think this create-eth-app repo looks nice for making eth apps.

Hi guys. I'm creating a front end for a contract and I am using React and Ethers, using create-eth-app as a starting point. My app starts like this:

https://github.com/paulrberg/create-eth-app Is a pretty good starting point for react.

You need to use Web3. You can take a look at https://github.com/paulrberg/create-eth-app. The boilerplate already connects to different wallets like Metamask.

Try taking a look at this boilerplate project and how it's done there: https://github.com/paulrberg/create-eth-app

create-eth-app v1.4.0 supports contract deployments to IPFS.

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.