I have never written a line of code in my life unless you consider peek and poke commands on a Commodore 64 code. In any case, today I created a stand-alone PC program that takes a story premise, writes a script, writes character sheets, and then writes location descriptions. Then it breaks the script into shots and writes detailed prompts. Full Markdown, json and export. Now I am sure that there is a lot that could be added to it, a lot could be tweaked and who knows how well it works yet. I don't. But, to me, being of sound mind and advanced age, I never expected to be able to do this. Now I am working on four more things. Let's see how this does.

Gen Xers are the most technologically adaptable generation in human history, from the dial-up modem to AI. Together we can overcome any challenge and AI is our next tech challenge. Let's learn it together. :) Share a picture of yourself and tell us what you want to learn about AI. I'll go first... I want to learn AI so I can be in control of my employment future.

A second brain typically means "an AI-augmented personal knowledge system where the AI doesn’t just store notes—it reads them, reasons over them, synthesizes insights, surfaces forgotten connections, and can help act on them." Basically a database of all your thoughts, ideas, communications, etc. I've broken them into different subsets of areas of focus. I'm also creating folders with information related to specific business practices or business experts. Then you point Claude to those areas and create a skill to review the information based on what you want out of it.. Using recommendations from people ahead of me and the Claude space, which are most those people :), I'm using the free download Obsidian to organize this information. Ideally, you'd put Obsidian into your standardized work flow and automatically export data to the appropriate folders through your workday so the second brain grows naturally with your experience. Right now this process is manual, so it's taking some time to get enough data in there to test out different skill markdown files,find out how best to store the information, organize the information, and access the information. I'll let you know how that goes.

Pete’s second-brain discussion has me thinking about the difference between saving something and being able to use it again. I’m learning practical AI alongside sales, and I want my notes to help me pick up the next session without starting over. We grew up learning plenty of new technology, but a bigger filing cabinet still needs a sensible label. How do you decide which notes become lasting reference material and which stay with a single project?

By V0xium I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.