Every daily log is the same as the dirt notebook. It reduces friction when going to create a note because you don't have to think about where to file the note _before_ it's even written. I tag things and can sort them later, if I want, or not. Or can schedule things to loop back into my life (move to the current daily) if I choose. It's the exact same concept as their dirt notebook.
It's not a new concept. Bullet journal, logseq, zettelkasten, org-mode, etc are all inspiration
I have a similar idea in the note taking app I've written for myself over a couple years. I have a new daily page everyday with a simple but powerful tagging system. Adding automation soon that will be kick ass, but for now the mcp server plus Claude Code is pretty dang powerful. It's basically a clone of logseq with my own features. It's got templates and saved views and powerful filtering. It's been super useful for me personally. I need to update the README though. https://github.com/steezeburger/brainspread/
You can only check your email so many times, and you can only work on so many problems at once. You also generally have to be mindful of token consumption. I think it also leads to burnout to work on so much at once. I've been working this way for like a year.
It's tough if you're somewhere that isn't very meaningful to you beyond the technology. I think there will be an existential shift soon towards more fulfilling work. Maybe I'm naive or that's just what I feel I need for myself.
It was definitely amazing, especially as a creator. It's how I learned to program! Actionscript was my first language. The only thing kinda close to the experience now is Processing. There may have been issues with the tech, but it kickstarted so many creative and engineering professional careers. There were so many good apps and games. It had such a rich ecosystem.
Yeah that would be great. I seriously don't understand how a company with this much money doesn't have some of the more basic ux implemented to make it a really great app. Blows my mind.
Does it just make it easier to get in a position you want or does it give you more natural looking positions as well or any other benefits? It's pretty fun to play with!
I've had pretty good luck with using playwright mcp to test web front ends. I think LLMs can totally test GUIs. Either via vision and computer control or via reading the GUI node tree (e.g. DOM) used by whatever you built the GUI with.
I think it's just the wrong metric to optimize for _first_. It's not generally a bad metric to keep tabs on though. Make it work, make it right, make it fast? Or something like that.
Yeah I totally agree! I also think people should still be reading as much code as they can. That's always been true imo. It is just hard to keep up with it now because of how much code an LLM can generate for $20/month. I do think we'll move to higher abstractions of course. We won't have to understand code as much as how the systems and components are architected. It would also be nice to use our new efficiency to return to producing truly optimized and fast software.
Experience is so so valuable right now. We can guide these agents super well, but I do fear for the juniors as you said. I would like to think I'd use the agents to dive deeper and learn faster. It was pretty rough piecing together solutions from Stack Overflow, various irc channels, Reddit, etc. But also, I cheated on my homework in college and didn't really review the answers, so not sure. Though I pursued programming out of interest and not just to complete a degree. Maybe it would have been different. In any case, I'm glad I came into the LLM era with a lot of experience and failures already.
I enjoy using and orchestrating agents a lot to build software, but have never really had the desire to replace my writing with LLMs. I don't write a whole whole lot, so maybe I just don't have enough writing to do to make it appealing, but my emails, blog posts, comments, whatever are the last thing I want to automate. Not only because it's less personal, but because I'm so tired of reading AI cruft myself. So much more text in tickets than there needs to be, for example.
And how are people forgetting to code by using LLMs? Do they just mean they forgot the syntax of a particular language? Or forgot how to architect features or how the development lifecycle works?
I've mostly used LLMs to build more complex things that would have been a lot to manage previously, or to build something completely new and learn how it works. I feel like I've only become a better engineer (and programmer too) because of LLMs.
Socials: - github.com/steezeburger
---