Adam TF

@FlyssaStudio How can I get a hold of you so I could use some of your chaotic models for a game I'm @FlyssaStudio

2D to 3D dragon sculpt

Check this out: WE ARE GOING ON A TRIP

@katie_haun I might be completely off here and correct me if I am wrong but it seems someone might be trying to impersonate you on LinkedIn, linkedin.com/in/katie-haun-…, just wanted to give a friendly heads up (X seems to be where you are most reachable)

@nftchance Also, are you mostly a solo web3 dev or part of a larger team, on a side note, love your website and some of your posts are great! Thanks for putting that together

i still don't get it tbh. this just doesn't make sense to me. my original tweet was about the developer experience. i couldn't care less about the experience of a project manager tbh they are pointless individuals to have on a team imo, especially a smart contract one. it would be best if they got out of the way and just let the devs focus on what needs to be done, slowing down the process and introducing more hurdles isn't going to solve any problem. if you want sandbox environments, that's what testnets are for. if you don't want to deploy to locally, you can already use a fork. if you want to deploy to multiple chains it takes a single command. if you want to ensure something works the way it's described, you just write tests. products are deprecated because they don't provide enough value to persist in development. looking at truffle and the points above. deploying contracts at high velocity is the wrong mindset to have imo.

What in the world are modern smart contract developers using? hardhat: - mind-bogglingly slow - can't get a response to anything. not even an acknowledgement. hardhat-ethers: - Incompatible with any modern front end. - conflicts with viem & abitype usage. hardhat-viem: - straight up does not work - the starter test kit don't even function - no functioning libraries - it's basically bricked foundry: - absolutely torturous to use. - an infinite amount of caveats that are horribly documented - SEO/naming is so abysmal you can't find anything - requires importing several libraries just to run a test - uses submodules as dependencies - has some of the worst formatting I've ever seen - a minimum of 2x your work to make your frontend implement your now solidity-cooked tests Smart contracts on Ethereum have so many issues today because it is nearly impossible to achieve even a decent workflow. I don't understand how this can be the state of things. Years have passed, and what happened? Everything got worse... At least when things were simple, you could write your contract and tests and integrations without tens of hours of work that have no justifiable basis. Now, good luck deploying a contract that's anything more than a basic openzeppelin fork.

@nftchance I would be curious on any specific examples you could provide when trying to use Defender "it just doesn’t really do anything and then things it did do were flat out wrong a good portion of the time, just super opinionated and filled.." reference to above

@nftchance Correct your original tweet was around dev experience but I think it does overlap with Devops as hardhat/deployments/foundry can be involved in this space But given your topic was on dev exp. perspective, I think I may have skewed things a different direction

@nftchance 2. getting product manager/operations involved more in the development process can be tricky, please see here on how Truffle teams tried to solve this: trufflesuite.com/blog/iterate-f… (Just using the links to show my points without full explanation, but happy to dive further via chat)

it just doesn’t really do anything and then things it did do were flat out wrong a good portion of the time, just super opinionated and filled with edge cases that made the intended value difficult to actually realize im genuinely not sure what devops for this stuff beyond monitors of active environments looks like tbh so probably not the best person to ask on this. as of now, I don’t have any problem in this area that needs to be solved but again, could be totally wrong about this if you can be a bit more specific with the problems you’re trying to solve maybe I can provide better insight but rn I’m a little confused

@nftchance I am sorry "X" 😀

@nftchance sure sorry for any confusion, kinda hard with character limit on Twitter and such core problems are: 1. multichain deployments and singlechain dApps CI pipelines can be difficult to setup, see the guide above for all the details

@nftchance thanks for the honest answer here, appreciated to answer your question, I would ask why did you think Defender was pointless? is it because a dedicated devops tool for web3 is not needed in your opinion?

I used it for like 3 days, was blown away how pointless it was and swiftly got out of there not sure why you’d be doing dev/staging/prod environments livr, automated testing is already solved by normal ci/cd, nothing here needs a unique solution? I must be misunderstanding what you’re getting at tbh

@nftchance For example, haven't used Defender myself but I don't see a lot of references to programmatic dev/test/prod environments with automated testing, managing CI pipelines, etc

@AdamTF6 definitely, there is -- openzeppelin defender is the best I know of as of now defender.openzeppelin.com/v2/#/code

@nftchance Thanks for the link, have you used them before? My team and I are working on a devops tool for Web3 more inspired by what the great folks at Truffle did before their solution got deprecated, trufflesuite.com/blog/iterate-f… and Truffle Dashboards, trufflesuite.com/blog/iterate-f…

@nftchance medium.com/better-program…

@AdamTF6 No, the top level interface is not the issue for any serious dev.