惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MyScale Blog
MyScale Blog
F
Fortinet All Blogs
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
D
Docker
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
爱范儿
爱范儿
V
Visual Studio Blog
Last Week in AI
Last Week in AI
WordPress大学
WordPress大学
aimingoo的专栏
aimingoo的专栏
小众软件
小众软件
L
LangChain Blog
Vercel News
Vercel News
阮一峰的网络日志
阮一峰的网络日志
IT之家
IT之家
P
Proofpoint News Feed
博客园_首页
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
The GitHub Blog
The GitHub Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
C
Check Point Blog
Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
The 80% You Don’t See: What Tracking My Work Taught Me
LazyDoomSlay · 2026-04-24 · via DEV Community

I started tracking my work recently.
Not with some system.
Not with some productivity guru method.

Just… writing things down.

Here’s what came out of it.

It wasn’t some big realization.

More like small things… stacking up.

my thoughts about tracking


Q: Why did you start tracking your work in the first place?

A:
I think it’s needed.

You need to appreciate your own progress even if nobody else sees it.
Also, I wanted to understand:

At this pace… where am I actually going?


Q: What did you think you were doing well before tracking?

A:
Nothing specific.

But now I think more.
I compare more.
And that makes it easier to decide what’s actually worth doing.


Q: What did tracking immediately prove wrong?

A:
That tracking is some “online coach” thing.

It’s not.

It’s just:

evaluating your own steps without judging yourself.

Just understanding why you made certain decisions.

Friction & Reality

It started to feel like a 20/80 kind of thing.

You see the 20%.

But most of the work lives in the 80%.

Ever had that feeling?

You think you worked all day…
but can’t explain what you actually did.

overview my idea

Q: When you say “I worked all day” what does that actually mean?

A:
Depends.

Sometimes “all day” == a few hours of real productivity.
Other times, I can go 8 hours straight on my own projects.

So yeah… “all day” doesn’t mean much by itself.


Q: How much of your time is real output?

A:
At work -> a few hours of focused, real output.
On my own stuff -> I can lock in for much longer.

Different energy.

Patterns I Didn’t Expect

Not in a dramatic way.
Just… quietly.

Q: What pattern kept repeating?

A:
I kept asking myself:

“Why am I not exploring things more?”

I do other hobbies gaming, exploring music, random stuff
but sometimes I skip the kind of work I actually enjoy
(side projects, deeper exploration).


Q: What surprised you about your behavior?

A:
I started questioning how I push myself:

“Am I pushing in the right direction… or just pushing?”

Also had this thought:

maybe I could present something at a Rust conference one day.

And these posts… might actually help with that.


Q: What did you not want to admit?

A:
That I actually have experience.

I’m not some “big” developer.
But I do have things worth sharing.

The Quiet Realization

Q: Did tracking ever “hit” you hard?

A:
Not really.

It’s more like a background process.
I don’t think about it daily.

Only when I sit down to reflect like writing this.


What Actually Got Better

Q: What did tracking help you understand?

A:
My habits.

  • what’s actually bad
  • what’s just human
  • what’s needed to not burn out

Not everything unproductive is “wrong”.

Some of it is just… necessary.


Q: Did anything become clearer?

A:
Yes.

I started focusing on things that actually have an effect.

Small things. Real things.

Not “big ideas influenced by media”.

I see people around me chasing huge things.
I’m building something simple but useful.

No AI hype.
Just coding and solving problems.

And honestly… that feels better.


Final Thought

Q: Tracking my work didn’t make me more productive. It made me realize…

A:
…my habits.

My progress.

And that I should actually appreciate my own effort.

Even small wins.
Even messy ones.

Because they add up.

What’s one thing you noticed about yourself?