WakaTime VS Stack Overflow Trends

Wakatime.com — Quantified self-metrics about your coding activity using text editor plugins, limited plan for free. - Source: dev.to / 4 months ago

Hi Hackers, One year ago I posted[0] on HN[1] about writing my own replacement for Celery, a background task queue for Python. WakaQ has been running in production[2] for over a year, and it's performed flawlessly. I've even been able to reduce the amount of worker machines needed, saving compute costs, even though the number of tasks executed has increased over time. Now I'm starting a new Next.js project using... - Source: Hacker News / 7 months ago

WakaTime is committed to making time tracking fully automatic for every programmer. By creating opensource plugins for IDEs and text editors, it gives powerful insights about how you code. It is possible now demonstrate these statistics in your GitHub profile. What’s next? Next up, showcase your skills, awards, and certifications. - Source: dev.to / 8 months ago

Building a daily habit to learn or code is essential. In a while, you don’t ask yourself what to do in the next 30 minutes you have. You open the terminal / IDE and practice. I used WakaTime to track my coding time and set a goal of one hour daily. - Source: dev.to / 11 months ago

Why do they all redirect to https://wakatime.com/. - Source: Hacker News / 12 months ago

It has, but it wasn't adopted by the pragmatists in that time. It's hard to tell if the early adopters adopted it either - It doesn't show up at all in the 2023 stack overflow survey (nor in the previous two years) - https://survey.stackoverflow.co/2023/#technology-most-popular-technologies - It doesn't show up in questions asked on Stackoverflow since 2008 -... - Source: Hacker News / 6 months ago

> In 2017 I had React projects in production for years. I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016. > And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box. Again, Next.js != React; the former builds on the latter, it doesn't replace it nor does it claim to be the same... - Source: Hacker News / 7 months ago

> Prior to Next.js, React was hard to setup and maintain No, it wasn't. > I started using Next.js in 2017. It made React a real production framework In 2017 I had React projects in production for years. > React was hard to setup and maintain and hard to make it go fast (on first load) And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are... - Source: Hacker News / 7 months ago

Based on what? https://insights.stackoverflow.com/trends?tags=python%2Cjava. - Source: Hacker News / 9 months ago

Fair enough, my information is outdated. StackOverflow agrees. [1] [1] https://insights.stackoverflow.com/trends?tags=django%2Cruby-on-rails. - Source: Hacker News / 9 months ago