Coding
- “What does your energy level look like after dialysis?”
- “When are you actually at your Mac with both arms free?”
- “What makes this app section so complicated?”
I really like GitKraken as my daily Git application. Check it out: Get GitKraken at 50% off
The Productivity Conversation I Didn't Expect to Have
I sat down to write about productivity. Instead, I accidentally solved my productivity problem.
It started with a simple request. I wanted to turn my struggles with overwhelm and chronic illness into a blog post. Multiple interests pulling me in different directions, dialysis eating up twelve hours a week, YouTube consumption replacing creation - the usual productivity paradox.
You read more about it here.
But something unexpected happened during the conversation with my AI writing assistant. What began as research for a blog post became a real-time case study in how productive conversations actually work.
The Original Problem
The setup was familiar to anyone who’s ever felt overwhelmed by their own interests. I love coding, cooking, RPGs, fitness, reading. My wife has projects that need my support. I’m supposed to be working on an iPad app for her. But instead of making progress on any of it, I find myself watching YouTube videos for hours.
I’d even found a video that perfectly explained the problem - how our brains get hijacked by consumption, how creation provides more sustainable dopamine hits, how shifting from consumer to contributor changes everything.
The Habit that forces your brain to stop consuming
I understood the theory. I just couldn’t implement it.
The Conversation That Changed Everything
“What’s your top priority right then?” came the question.
“Probably the iPadOS app, since finishing that would help my wife greatly.”
Simple question. Clear answer. But then something interesting happened.
“Those twelve hours of dialysis per week? That’s actually prime iPad development time. You could queue up iOS tutorials, work on app wireframes…”
“Well, there’s no Xcode for iPad,” I replied. “And my left arm is completely blocked with needles. I can’t move it.”
Sudden silence. Then: “Right, of course there’s no Xcode for iPad. That was a pretty big oversight on my part.”
What Made This Conversation Different
Most productivity advice fails because it’s generic. It assumes everyone has the same constraints, the same energy levels, the same physical capabilities. The conversation became productive the moment my real constraints got acknowledged.
No judgment about not being able to code one-handed during medical treatment. No generic advice about “just managing your time better.” Instead: “What can you realistically do one-handed on an iPad for four hours?”
The questions kept getting more specific:
Each question revealed another layer of reality that typical productivity advice ignores.
The Lessons Hidden in the Dialogue
Assumptions get corrected quickly. The Xcode-on-iPad suggestion was wrong, but it got corrected immediately instead of becoming the foundation for useless advice.
Constraints clarify priorities. Once we established that dialysis time wasn’t coding time, it became clear that the real development work had to happen during my four productive in-between days.
Specificity beats generality. “Work on the app” is overwhelming. “Identify the next three concrete actions for the app” is actionable.
Questions matter more than answers. The breakthrough didn’t come from advice. It came from questions that helped me see my situation more clearly.
The Meta-Lesson
Here’s what I realized: the conversation itself was demonstrating the productivity principle I needed to learn.
Instead of consuming more productivity content, I was actively working through my specific situation. Instead of generic advice, I was getting targeted questions. Instead of feeling judged for my limitations, I was finding ways to work with them.
The conversation was creation, not consumption. It was collaborative problem-solving in real time.
The Breakthrough Moment
The real breakthrough came when we identified that the missing section of the app wasn’t just technically complicated - it was “lots of different pieces.” Suddenly the overwhelm made sense. It wasn’t one elegant problem to solve, but fifteen mini-features that all needed to connect.
“What if you just listed all the different pieces first? Not designing them, not coding them - just creating an inventory.”
That’s when it clicked. The paralysis wasn’t about not knowing how to code. It was about not knowing where to start when everything felt connected to everything else.
What This Means for Productivity
The best productivity hack might be finding someone who asks better questions.
Not someone who gives you a system to follow. Not someone who tells you to eliminate distractions. Someone who helps you see your actual constraints clearly, then works with those constraints instead of ignoring them.
Generic productivity advice is like generic medical advice - it might work for some people, but it’s useless if it doesn’t account for your specific situation.
The real productivity breakthrough happens when you stop trying to fit your life into someone else’s system and start building a system that fits your actual life.
The Ironic Ending
I started this conversation wanting to write about my productivity problems. I ended up actually solving them.
The blog post was supposed to be about the problem. Instead, it became about the solution.
Sometimes the most productive thing you can do is have a better conversation.
I really enjoy vibe coding as it has become to be known. Claude Code to be specific. It really helps me push along my iOS app nicely. Not very cheap, but also not outrageously expensive for the amount of productivity I get from it.
I’m playing with how far I can push Cursor AI to build an iOS app. 2 views down and it worked great. Still all basic stuff, but works nicely. On the third view it fell over though. I had a calendar on the left and the day’s data on the right. Cursor couldn’t get the data to update based on the date.
I‘ve seen a couple of established iOS developers gripe about SwiftUI and that they should have stuck with UIKit. Would you advise someone starting out with iOS development and zero Swift experience to use UIKit as well? Or is it more of an old dog, new tricks kind of issue?
I now have my own Python module to write Safari WebArchives. Neat. And not too hard to implement.
So now Links also saves a WebArchive copy and triggers a Wayback savepoint.
I rewrote my webcatcher Python script yesterday. It is now leaner, meaner and more resilient against failed downloads. Links is coming together nicely. Pretty much all that is left is a nicer CSS for mobile devices and a web daemon so I can send stuff to Links from my iPhone.
Trying to decide between Trafilatua, Newspaper 4K and Readabilty for my Markdown and PDF creation.