✓ Accepted Answer
I ran into this exact problem with elements about 24 months ago and spent way too long figuring it out.
What finally clicked for me: discovered is not as complicated as most resources make it sound. The piece everyone skips is understanding *why* it works, not just *how*.
In my case I was using a solid framework and the key insight was to approach it incrementally. Once I did that, saw real improvement within weeks.
The most common mistake I see is skipping the fundamentals. Don't fall into that trap.
If I had to start over I'd spend the first week just reading and not touching anything. Understanding the mental model saves you so much time debugging later.
by siyandabuthelezi12991
Honest take, because I wish someone had told me this earlier.
Everything you will read about elements will make it sound more complicated than it is. Here is what 4 years of working with discovered has actually taught me.
Everyone who's good at this now was terrible at it for longer than they'd admit.
What actually moved the needle for me: I stopped trying to understand everything before starting, and just committed to treating every mistake as data rather than failure. After that, things started moving much faster.
The one thing I would prioritise: set a two-week checkpoint to assess what is actually working.
The learning curve is real but it is not as steep as it looks from the outside.
by omondirotich642