Sometimes deliberate roadblocks can be a good thing to get more efficient and effective products and workflow. Here's how.
Evolving and explaining how we run our company
As we write in “It Doesn’t Have to Be Crazy at Work”, you should treat your company as a product too. To improve a product, you listen, learn, (re)consider, concept, and iterate. …
The 10 Best Practices for Remote Software Engineering
At face value, when we think of developer productivity we might think of effectiveness in time management, communication, and task completion.14 Although we are drawn to personal workflow or time management tools, and learning secrets to improving our productivity, ironically this quest for the holy grail can sometimes take us off course and be a detriment to our productivity. The problem is that accomplishing tasks or having a filled up schedule does not necessarily equate to productivity. Creating a formulaic working strategy, as was common in the last century, does not either.a,8,13 Productivity is less a quality that can be easily measured,b controlled, or improved directly with tools, but instead is a human element that manifests from developer happiness.
21 Productivity Hacks I’ve Picked Up Over the Years
A thorough list of practical productivity methods I've used and refined over the last 16 years.
Bob Moesta - Jobs-to-be-Done Find Out the Why!
Less stress, more productivity: why working fewer hours is better for you and your employer
There’s always too much work to be done on software projects, too many features to implement, too many bugs to fix. Some days you’re just not going through the backlog fast enough, you’re not producing enough code, and it’s taking too long to fix a seemingly-impossible bug. And to make things worse you’re wasting time in pointless meetings instead of getting work done. Once it gets bad enough you can find yourself always scrambling, working overtime just to keep up. Pretty soon it’s just expected, and you need to be available to answer emails at all hours even when there are no emergencies. You’re tired and burnt out and there’s still just as much work as before. The real solution is not working even harder or even longer, but rather the complete opposite: working fewer hours.
6 steps to perfecting an open source product strategy
The future of building great products lies in breaking down the boundaries between business and technical thinking.
Please stop multitasking. I’m begging you. Please.
The greatest trick we ever pulled on ourselves as knowledge workers was convincing ourselves we could juggle multiple projects with no consequences.
AI-Generated “Workslop” Is Destroying Productivity
Despite a surge in generative AI use across workplaces, most companies are seeing little measurable ROI. One possible reason is because AI tools are being used to produce “workslop”—content that appears polished but lacks real substance, offloading cognitive labor onto coworkers. Research from BetterUp Labs and Stanford found that 41% of workers have encountered such AI-generated output, costing nearly two hours of rework per instance and creating downstream productivity, trust, and collaboration issues. Leaders need to consider how they may be encouraging indiscriminate organizational mandates and offering too little guidance on quality standards. To counteract workslop, leaders should model purposeful AI use, establish clear norms, and encourage a “pilot mindset” that combines high agency with optimism—promoting AI as a collaborative tool, not a shortcut.
How to be more productive without forcing yourself
Imagine you could work more and be wildly productive. And you wouldn’t need to force yourself to work.
It’s Time to Embrace Slow Productivity
We need fewer things to work on. Starting now.
How to not screw up your product strategy | Jade Rubick - Engineering Leadership
An overview of common mistakes people make while developing a product strategy, tips for creating a successful strategy, and how to communicate and execute on a product strategy.
Hey! I'm Isaac
I like building tools, breaking workflows, and putting them back together better.
How to brainstorm great business ideas
It's been said that ideas don't matter, and that only execution does. I wholeheartedly disagree. You need both to succeed, but you can only get so good...
Maybe you should do less “work”
Working in tech, I've observed developers who work as hard as possible when they don't need to. I’m here today to tell you that it's a bad idea and you shouldn't do it.
Harnessing Frustration: Using LLMs to Overcome Activation Energy
One of my biggest weaknesses as a software engineer is procrastination when facing a new project. When the scope is unclear, I have a tendency to wait until I feel I’ve “felt out” the problem to start doing anything. I know I’ll feel better and work much faster when I get “stuck in” but I still struggle with that first step, overcoming the “activation energy” required to engage with the details. LLMs have been a game-changer for me in this respect: I can just throw a couple of sentences at them with the shape of the problem. This leads to one of two outcomes: The LLM comes up with a good solution, usually in a slightly different way than what I was thinking. I realize “oh wow the solution is much simpler than I thought”. Straight away I start thinking about the consequences of implementing and improving what the LLM suggested. The LLM comes up with a solution that I intuitively recognize as “wrong”. My immediate reaction is frustration (“How could it get it so wrong”) which leads me to go back and forth with the model, explaining to it why its solution could not possibly work. But in the process of arguing with the model, my brain is churning away and generating variations or different approaches that could work. After a while, even if the AI is still on the wrong track, the debate will trigger a moment of inspiration where suddenly the solution will come to me. I’ll excitedly start up a new conversation and start working through it with the model. The key is the emotional reaction I have immediately to the LLM’s response, either excitement or frustration. By harnessing this immediate feedback loop, I get my brain out of its passive, procrastination mode. It’s almost like a jolt: either I’m thrilled because it’s simpler than I thought, or I’m spurred to action by the urge to correct a perceived ‘wrong’ answer. This forces me to engage with the problem in a meaningful way.
Finding Flow: Escaping Digital Distractions Through Deep Work and Slow Living
Learn how to achieve flow state and defeat digital distractions through environment design, mindful breaks, and deep work practices for a more focused life.
