Content pfp
Content
@
0 reply
0 recast
2 reactions
xh3b4sd ↑ pfp
xh3b4sd ↑
@xh3b4sd.eth
I built the Uvio prototype within 12 weeks. Frontend, backend, smart contracts, UI, UX, design, APIs, background jobs, token engineering, user auth, mechanism design, infra, documentation, CI/CD, etc. Hit me up if you want to talk about any consumer crypto engineering challenge. I don't know it all, and it's not all "right", but it all works. Currently working on the design for user notifications.
1 reply
0 recast
1 reaction
Charlie Simms pfp
Charlie Simms
@validdiktorian
May I ask how long it took you to develop on the blockchain? I’m a software engineer (11 YoE) with a background in EE and I feel like my head is swimming with new terminology. (I’m trying to avoid using LLMs to build b/c I’m one of those devs who needs to understand how everything works to debug properly.)
1 reply
0 recast
1 reaction
xh3b4sd ↑ pfp
xh3b4sd ↑
@xh3b4sd.eth
Could you specify your question a bit more? Are you interested in how long it took me to get comfortable with those new blockchain related concepts? Or would you like to know how long it took to write the Uvio smart contracts? My generic answer would be that all technical fields are full of acronyms and levels of abstraction. I would nowadays always recommend to pair-program with an LLM together. If you are already a rather seasoned engineer then you are in the fortunate position to ask rather qualified questions and you get an early sense at which point the model is hallucinating and bullshitting you.
1 reply
0 recast
0 reaction
Charlie Simms pfp
Charlie Simms
@validdiktorian
How long it took to get comfortable with blockchain-related concepts. I’m comfortable with abstraction (e.g., ISAs, OS kernels, network APIs), but there are so many different blockchain technologies (e.g., DeFi primitives, transaction models, exchanges) that it’s been tricky to figure where/what/how to build.
0 reply
0 recast
0 reaction