marvstazar

1. Just a single sentence idea or even copying the relevant messages from chat or email. If you are using Jira or similar, this is where MCP gets useful.

2. Only Claude at the moment

3. Each has its own repo and own CLAUDE.md/AGENTS.md file. The CLAUDE.md file is just a lookup document.

The detailed project specific markdown are under the rules folder, e.g. "forms-and-dialogs.md", "roles.md", etc. These rules are always updated by the agent for all new features/bug fixes, etc.

I also instruct the agent to always keep detailed markdown in the docs folder, which is subdivided into: idea/plan/review. These get created when new features or other significant updates are implemented.

4. The agent so far has not failed to reference the above files, so it already knows what approach to do when working on a new task.

5. I built my own skills framework for this (inspired by Superpowers) and still using it.

Pretty good timing now that Rails has released a security update :|

https://rubyonrails.org/2026/11/4/Rails-8.0.5.2-and-8.1.4.1-...

I was wondering why there was a dragon there, is it from Wrath of the Lich King?

Somewhat tuning out these "X is better than Y" news and articles, as things are still moving quite fast. In a few weeks, OpenAI offers more value for money and the cycle repeats again.

As a Claude subscriber, I am quite enjoying the value I get from Anthropic. But I am not forgetting that this is their loss leader, and API access is still their main driver. So strike while things are good, but expect some pullback in the future.

Biggest problem right now for me is what do I tell my children to pursue in college. Up until last year my default answer is a path towards Software Engineering. Now, I am not even sure anymore.

I can work on this "soul-sucking" job, but what of the next gen?

I agree with the premise here, and is on par with what I experienced in AI-assisted development. This is the same idea baked in https://github.com/marvs/kantan-dev, which is that artifacts should be kept within the repo so that future development has built-in context discovery.

Organizing the markdown files by feature/issue/change makes it easier for the LLM to search for the appropriate documentation. Coupled with well-broken down Claude rules files, and Claude Code (or other harnesses) get better as you make more changes.

As a senior developer you already spend a significant amount of time planning new feature implementations and reviewing other people's code (PRs). I find that this skill transitions quite nicely to working with coding agents.

There's a music video by Ummet Ozcan, "Kayra" that shows videos of these eagle hunters: https://www.youtube.com/watch?v=n21YEsQy67E

From what I understand, the sqlite3 comment was made it context of the Solid libraries. Basically common Redis-backed functionality can now be sqlite3-backed instead.

I do share your preference on using Postgres as the main database. Having that as the main db with sqlite3 used for auxiliary functionality sounds great.

I suggest you back up the HTML files as a record of her work when she was still a child, it will be a family treasure in the future :) You can even add it under your family's domain for safekeeping.

How does it compare to Github Copilot?

DHH did mention in the article that if you are just starting up and finding market fit, you should use the cloud and not buy your own hardware.

If you inherited a project with no tests at all, mocking is a lifesaver. It allows you to only worry about specific aspects of the application so you can start writing and running tests. I agree though that if not done properly, it can be overused and can make your tests practically worthless.