Day 1:
- HTML Structure:
- Doctype declaration
- HTML, head, and body tags
- Basic document structure
- HTML Tags
This was yesterday's road map. We looked at the basics of html
#100DaysOfCode#codechallenge#dailycoding#learntocode
During the development and deployment of all software errors are unavoidable, it's no different o blockchains: errors exist on the blockchain, but the handling process is primitive.
A thread🧵:
1. What does primitive mean?
primitive simply means that it's limited or better still underdeveloped.
> If a transaction fails, it simply reverts.
> All state changes are discarded.
> Gas fees are often lost.
> Execution halts without built-in recovery mechanisms.
2. in web2 softwares, errors are expected, and measures are taken against them.
> System retry
> roll back
> log failures, and they recover gracefully. this is the standard in engineering practices.
3. this makes building reliable applications on the blockchain really difficult as the developers must anticipate every failure case upfront or push complexity offchain.
4. this has resulted in many applications relying on:
> off-chain monitoring
> external rely bots
> manual intervention
> complex guard logic
all in an attempt to compensate for limited on-chain error handling.
4. the problem comes from the original design of blockchains. You see, blockchains were designed for deterministic execution and not fault tolerant application workflows.
5. @RialoHQ approaches this in a much better way, by treating errors as terminal events; rialo introduces native error awareness at the protocol level.
6. this allows developers to define:
> how failures are handled
> what should retry
> what should roll back
>what should trigger alternative logic; all within the same environment.
7. with native error handling:
> failed steps can be isolated
> state can be conditionally preserved
> recovery paths can be encoded onchain without the need for any external systems
8. use cases include:
> multi-step transactions
> scheduled actions with fallback logic
> cross-chain operations with failure recovery
> long running workflows
all which are handled onchain
9. better error handling improves
> application reliability
> developer experience
> user trust
this makes failure manageable and not catastrophic.
this problem has lasted long enough and rialo is paving the way for a much better standard.
that's all for today on on-chain error handling. learnt a thing or two about rialo and the blockchain?
Drop a follow and share for a friend and I'll see you on the next one❤️.
Day 52: Build Phase
Meeting with the team, taking progress from both the product designers, frontend dev and backend dev.
We are happy to announce that we are going to be working on Ecommerce website with lots of exciting features
#buildphass#100daysofcodechallenge#javascript
Day 2 of my 100 days of UX/UI design challenge!
Today's focus: Consistency in design
I learned the importance of consistency in layout and spacing....
Thanks for following along on this journey! Let's keep designing and learning together! #UXUIDesign#100DaysChallenge#Day2
Day 1 meeting where we shared what we learnt for the day. The rule is strictly follow the roadmap no matter how far you must have gone with learning. We are still bringing more goodies guysss.
Stay tuned 🌚
#100DaysOfCode#codechallenge#dailycoding#learntocode#javascript
What to Expect
Over the next 100 days, I'll be sharing:
- Daily updates on what I've learned and accomplished
- Code snippets and examples
- Challenges I faced and how I overcame them
- Resources and tips for learning
- Reflections on my progress and insights
I'm so happy to announce that my frriends and I are embarking on a 100 days of coding challenge.
I'll be sharing our designs and progress everyday on this platform
So stay tuned🌚✨
#100daysofcode#learntocode#codechallenge#dailycoding
Ending of March I and my friends embarked on a 30 days of coding challenge. Gracefully we rounded off the challenge today. And we are privileged to have @eliezerajah his words really inspired us, and triggered us to embark on more.
Thanks @eliezerajah for having you.