Day 9/100 π
LeetCode 1631 β Path With Minimum Effort.
This one reminded me that understanding a solution is very different from being able to come up with it myself.
Still relying on tutorials, but slowly building the intuition.
9 days down. π₯
#100DaysOfCode
Day 8/100 π
Switching things up today.
Worked on LeetCode 83 β Remove Duplicates from Sorted List.
After spending the last few days wrestling with graphs, it was nice to slow down and focus on linked list fundamentals.
Still learning, still showing up.
#100DaysOfCode
Day 7/100 π
One week into the challenge.
Still travelling around Cornwall, but managed to squeeze in some coding today:
LeetCode 3069 β Distribute Elements Into Two Arrays I.
The goal was never to code for hours every day. It's to keep showing up.
#100DaysOfCode
Day 6/100 π
Cornwall trip + coding challenge = trying to find 20 minutes somewhere in the day π
Solved LeetCode 3622 β Check Divisibility by Digit Sum and Product.
Not every day has to be productive. Just need to keep showing up.
#100DaysOfCode
Day 5/100 π
Graphs really tested me today.π₯²
Worked on LeetCode 127 β Word Ladder and 743 β Network Delay Time.
After struggling with a medium for hours, I actually started wondering if graphs are the toughest part of DSA.
Still learning. Still showing up.
#100DaysOfCode
Day 4/100 π
Work was busy today, so I only managed one LeetCode problem.
417 β Pacific Atlantic Water Flow.
Not every day will be a big coding session. Today was about keeping the streak alive and learning something new.
#100DaysOfCode
Day 3/100 π
Today: LeetCode 207 β Course Schedule.
Worked through another graph problem and started learning about dependencies and cycle detection.
Still following tutorials and implementations, but I'm understanding a little more each day.
#100DaysOfCode
Day 2/100 π
Today I worked on 2 LeetCode graph problems:
β 994. Rotting Oranges
β 130. Surrounded Regions
Still relying heavily on tutorials and following implementations, but even that is helping me understand the patterns.
One step at a time.
#100DaysOfCode
Day 1/100 π
Starting a 100 Days of Coding challenge.
No complicated goals:
β Code every day
β Get better at DSA
β Share what I learn
Today: DFS + Graph problems.
Letβs see what 100 days of consistency can do.
#100DaysOfCode
100+ problems later.
Today I solved my first LeetCode Hard Problem without any help.
No Tutorial
No AI
No Hints
Small milestone.
Back to solving.
#LeetCode#DSA#BuildInPublic#DSAAfter30s
One thing I've realised after solving first 100 DSA problems:
Progress doesn't come from seeing new questions.
It comes from seeing the same patterns over and over until your brain starts recognising them automatically.
#DSA#LeetCode#InterviewPrep
100 DSA problems solved. It still feels overwhelming.
Doing this alongside a full-time job has taught me that the biggest challenge isn't solving problemsβit's staying patient.
Some days I feel like I'm improving. Other days, I question everything.
#DSA#LeetCode#FAANGPrep
Is a "pretty" UI enough?
While sleek design is important, a truly quality UI is about building an experience that is fast, secure, accessible, and scalable.
I've broken down the 5 core pillars of a quality UI in my latest article. π
4. SEO: Ensuring your beautiful website can actually be found. I share technical best practices for front-end developers.
5. Usability: Creating an intuitive and effective experience that builds trust.
π¦ In #javascript, parameters and arguments are different things. #parameters are placeholders defined in a function declaration, while #arguments are the actual values passed when calling the function. Parameters set expectations, while arguments provide values.
Many React developers use indexes as keys while mapping a list. But Fun Fact #React does not recommend it. This can negatively impact performance and may cause issues with the component state if the order of the list changes. Use indexes only as the last resort. #javascript