Extroverted Developer

I built Taskleef because every Kanban tool I tried felt like a glorified to-do list. What started as a web app for people who actually care about how they manage their work has just hit a big milestone — Taskleef is now available on the iOS App Store.

Download Taskleef for iOS

A Companion, Not a Clone

Most apps try to cram their entire desktop experience onto a phone screen. We went a different direction. The Taskleef iOS app isn’t a 1:1 copy of the web app — it’s a companion to it.

Taskleef on the web is where the heavy lifting happens. Real-time Kanban boards, WIP limits, AI agents you can watch work, team collaboration — that’s your command center for serious project management.

The mobile app has more humble aims. It’s a place to quickly capture ideas, jot down tasks, and lightly organize your thoughts. It’s closer to a todo list than a project management tool — and that’s on purpose.

One Platform, Two Modes

Here’s what makes it powerful: it’s all the same platform underneath. That task you captured on your phone while waiting for coffee? It syncs instantly to Taskleef on the web, where it can become a full card on a Kanban board with subtasks, AI assistance, and team visibility.

You can move up and down the capability chain just by switching devices. Quick capture on mobile, deep work on desktop. A fleeting idea on the train becomes a structured project at your desk. No re-entry, no copy-paste, no friction.

This Is Just the Start

Getting approved for the App Store is a milestone we’re genuinely pumped about. But it’s also just the beginning of the mobile story. We have a lot planned — better notifications, widgets, Shortcuts integration, and more.

If you’ve been using Taskleef on the web, go grab the iOS app and start capturing. If you haven’t tried Taskleef yet, there’s never been a better time to see what Kanban is supposed to feel like.

Get Taskleef on iOS →

Honestly? Yes. Picard ruined a lot of us.

TNG is basically a 178-episode argument that if you solve material scarcity, humans will choose to be decent. That’s a dangerous thing to show a kid because then you spend the rest of your life measuring reality against the Federation and finding it wanting.

How would the world behave if we had the replicator?

“We work to better ourselves and the rest of humanity” is the post-labor thesis. And the reason you feel that tension so acutely is that Roddenberry handed you a moral baseline that the actual world consistently fails to meet.

The cruelest trick TNG plays is making it look obvious. Of course you don’t let people starve when you have replicators. Of course you don’t exploit people when scarcity is solved. It feels self-evident on the Enterprise. Then you look around at a world that produces enough food to feed everyone and doesn’t, and the gap between what’s possible and what is becomes physically uncomfortable.

So yeah. Blame Picard. He’s the reason a generation of engineers went into tech half-believing they were building the Federation and are now reckoning with the fact that they might have built the Ferengi Alliance instead.

Experts are usually expert of the past not the future

– Sebastian Thrun

Holy crap, the movement to get huge models working well on local hardware has kicked off and the results are impressive.

This morning I used this project https://github.com/danveloper/flash-moe.git

Which allows me to run this HUGE Qwen 3 – 327B parameter model ON MY LOCAL MACBOOK PRO. It’s a bit slow, but damn if it doesn’t work! SOTA on my LAPTOP

</freakout>

I have no idea what I’m doing when it comes to marketing. However, over the past week I’ve begun ads for Taskleef and today I overhauled the landing page.

I’d love feedback if anyone is willing to take a look https://taskleef.com

Maxxing is the thief of joy

That’s how I always read this anyway

That’s how I always read this anyway

Just like the Guilded Age robber barons. Only academics who study this time in history will know the name.

Unlike Julius Cesar, Marcus Aurelius, Plato, Socrates, Abraham Lincoln

The difference? Introspection

There are several debates happening in the tech industry right now amongst software engineers. One of them goes along the lines of “If you don’t read the code the AI is producing, then how do you know what it does?!”

Things I find strange about this argument:

• No software engineer has read every single line of code that goes into a project
• Most don’t read their own entire code base, let alone any libraries or dependencies that go into them
• Reading code alone doesn’t tell you how it _actually_ works when you put everything together.
• NASA Showed that a formal code review process (reading the code) catches somewhere between 60%-90% of defects [Source 1, Source 2]

The serious answer to this is: Regardless of how code was created, you need to test it in order to know that it does what it’s supposed to

It doesn’t matter if you wrote it, you don’t know it works until you test it.

It doesn’t matter if an AI wrote it, you don’t know it works until you test it.

It doesn’t matter if another team wrote it, you don’t know it works until you test it.

It doesn’t matter if a compiler generated it, you don’t know it works until you test it.

There are many ways to verify code

• You can write automated testing of all sorts
• You can have formal verification systems such as algebraic types and rust’s borrow checker
• You can have humans manually test things
• You can have users test things

But in the end it’s the verification, the convincing yourself it works, that matters for taking responsibility. Not whether you read it or not.