Regarding goals and timeframes for personal goals.
What I’ve noticed is that marathons work better than sprints for long-term goals.
Last year, I came across an idea that the ideal timeframe to achieve something meaningful is 100 days.
It’s close to a quarter, but the number itself is simple and round - and our brains tend to like that.
We deal with a lot of stress every day. Because of that, even a one-week break from a productive routine can make it feel like you’ve completely fallen off track.
Add an active inner critic, and it becomes even harder to get back.
With a 100-day timeframe, you give yourself permission to pause.
You don’t panic if you slow down - you know you still have enough time to move forward.
You know what? jQuery 4.0 has been released!
Interesting fact - jQuery still powers roughly 70% of the top websites. Whether it’s a legacy system for a global enterprise or a quick landing page, jQuery has been the reliable backbone of the internet for nearly two decades!!
Huge congrats to the contributors and the OpenJS Foundation for keeping the "Write Less, Do More" spirit alive!
Everyone else on your feed:
- Vibe-coding viral apps overnight and making millions
- Vibe-coding games that blow people’s minds
You:
- Spending 3 hours trying to center a button on a landing page using you favorite AI tool
- Getting a $500 API bill for AI tokens for an app that still doesn't work
Something went wrong, but where?
The end of the year is approaching - which means it’s time to set new goals.
My rule: make them clear and measurable, AND start working on them right now before end of the year to see if they truly matter to you. A sort of probation period.
One of my goals for next year is getting the CKA (Certified Kubernetes Administrator) - so I've slowly begun preparing for it already.
What's your biggest goal for next year?
Decided to pause Advent of Code for now - it's too time consuming and things are a bit too packed at the moment.
At least I know what need to improve for next time!
So React managed to shake the internet twice this week.
- first, a newly discovered CVE in React Server Components
- second, Cloudflare's mitigation efforts that caused additional disruption
I've never been a fan of Server Components - the approach feels like a throwback to early-2000s PHP. Ironically, today's PHP ecosystem is far more mature, while React is rediscovering ideas from decades ago
We are aware of the issue impacting the availability of Cloudflare’s network. It was not an attack; root cause was disabling some logging to help mitigate this week’s React CVE.
Will share full details in a blog post today. Sites should be back online now, but I understand the frustration this causes and the work being