Inspired by two projects of github:schildep I start to explore what can be expressed in Lean and make coding agents implement and prove the implementation at the same time.
I've spent way too much time recently writing TUIs for productivity (eg. merging github PRs, Google Chat DMs, firewall approval requests into one dashboard, another for watching actions on my PRs) and lost a lot of productivity as a result.
there are reasons to procrastinate. sometimes you are not ready for a task and it has to ripen on the back of your had.
sometimes you don't have structure and are not organised.
sometimes you might be overwhelmed by too many tasks.
make a schedule and only try to get one or two things done per day.
productivity is not about getting more done for the sake of it. it's about getting to what is important for you.
Sharing your work with others is a hard computer science problem in 2026, the Year of our Lord. You either here the sound of chirping crickets or the sound of "AI Slop" yells.
My past 3 projects went viral. I didnโt write a single line of code in any of them. But I still feel I engineered them. There were a few people that noticed but the majority didnโt see an issue.
You're fortunate in that you've genuinely captured something that people clearly want with textlog. No one wants another static site generator or coding harness. Ideas that resonate are pretty few and far between now.
I should have said past 4 projects went viral but the other one I did a lot of coding too, so wasnโt entirely โAI slopโ. In all cases though, I made something I wanted to see. It just happened to resonate with others. Still, none of them extremely popular yet. All <500 users.
uncensored Qwen
and OpenClaw
a prompt
and pray
there is no flaw
#poemnotesfollow
@kev๐งprofilefollowrunner. making games, music, software. getting into as much trouble as i can.wrote:
game dev with LLMs assisting on some of the engine legwork I learned to do over the years is the most fun programming I've had since I was 12 years old plucking away at the public library commodore 64
For 30 years, productivity sky-rocketed with the advancement of automation and computing. Meanwhile, a decline in longevity was observed, correlated to sleep depravation. Productivity improvement goes to the owners class' pockets, sleep benefits the workers health.
For 30 years, productivity skyrocketed through automation, yet longevity plummeted as a direct result of sleep deprivation. While these gains accrue to the owner class, sleep remains an undervalued element of the worker's health. We are trading life expectancy for chump change.
That said, in Canada working class started loosing life expentancy for the 3rd year in a row, and WHO figures show a decline in improvement of life expentancy globally. But hey, I am just a no-one on the internet spewing bs :)
a decline in the improvement of life expectancy isn't the same as a decline in life expectancy, it's just that it's improving less fast now, we might be reaching biological limits however?
We tought for years that there was a biological ceiling for sprinters or marathon runners for example, with research backing it, but every one record was shattered. I tend to be cautious of biological explanations.
Currently it provides a single read-only tool that lets agents fetch all the data in Main about the user's home (details about the home itself, systems/appliances, documents, any repairs they've logged). I think it could get interesting once we provide additional tools for logging repairs, upgrades, and more into the home's memory.
Compared to other apps which all build their own AI chat features, I wonder if the move could be to cede ground on this arms race and focus on building other features that add value for our users. Feels like a "commoditize your complement" situation.