How AI Cut My Meeting Time in Half
I wasn't trying to kill meetings, just survive them. A few AI habits quietly cut my meeting time in half. Here's exactly what I changed.
Evidence-based guides on productivity, habit formation, mental models, learning, and self-improvement. Practical over inspirational — focused on what actually works.
I wasn't trying to kill meetings, just survive them. A few AI habits quietly cut my meeting time in half. Here's exactly what I changed.
One tiny action, done before anything else, quietly set the tone for every hour that followed. It cost me two minutes and changed the whole day.
Steal my prompt library — seven templates I reuse for writing, planning, research, and decisions, with the exact wording.
I prided myself on juggling everything. Then I learned my brain was never juggling at all — it was just dropping things faster.
I thought I was getting organized. I was actually procrastinating with extra steps — and tool-hopping was the whole disease.
I used to drown in open tabs and half-read articles. Now an AI assistant does the digging and I do the thinking. Here's the workflow that changed how I learn.
I used to dread content for the whole month. Now I batch it in a single focused session with AI doing the heavy lifting. Here's the exact system.
Checking things off feels like progress. Most of the time it's the comfortable activity that hides the real, uncomfortable work.
For thirty days, nobody on my team sat in a status meeting. An AI ran them instead. Here's what broke, what got better, and what I'll never go back to.
Dropped into a huge unfamiliar codebase? Here's the exact week-one playbook I use to go from lost to shipping, without reading every file.
The honest result of waking at 5 AM for a month — including the part nobody mentions when they sell you the dream.
A small, unglamorous AI stack that quietly does about an hour of work before I've finished my coffee. Here's the exact lineup and what each one does.
I stopped doing the busywork and let AI assistants run the boring half of my job for a month. The results were not what I bragged about on day one.
I tracked every working hour for 30 days, expecting to learn I code a lot. The data said something far more uncomfortable about how I actually spend my day.
The pragmatic balance between purity and progress. When chasing perfect code becomes the thing that stops you from shipping.
I ask it in every review and design doc now. One deceptively simple question that quietly upgraded how I build software.
The real multiplier is more learnable than talent. What actually separates the engineers who seem to do the work of ten — and why you can copy it.
Indexes, transactions and joins stopped being scary. The mental models that turned the database from a black box into a tool I actually control.
The blinking cursor terrified me for years. The small mindset shift that turned the terminal from scary into my favorite tool.
I learned three programming languages and got worse at all of them by repeating the same mistake. The pattern took me years to see.