Cheezy World

I see a lot of people posting about how bad AI is at creating code. I, along with everybody I work with, am having the opposite experience where AI is producing high-quality code that is well factored and tested. For a long time it has been a mystery how people can have such opposite experiences.

I now have three cases where close friends were making such statements and I offered to have a chat to understand their experience. In each case, they were using tools that were far from ideal and the tools they had were not configured at all. When I told them about options to provide AI with more instructions and constrain / direct how it works they were surprised.

A million small things - on to Version 1.0

This is the final post in this series. There were many things that needed to be done that were not on the original plan so I worked with my trusty AI tools to complete them. This post simply lists them and provides a some details where I thought it was interesting.

Do not worry about this being the end of the series. See the What’s Next section at the bottom of this post to see where this is all going. What’s next is very exciting and I hope you stay with me on this.

Polish & Enhancement

It is finally time to get back and finish phase 7 of our plan. Here is what remains:

#### Phase 7: Polish & Enhancement

- [ ] **UI/UX improvements**
  - [ ] Design beautiful board cards with Tailwind CSS
  - [ ] Add hover effects and transitions
  - [ ] Improve spacing and typography
  - [ ] Add loading states for async actions
  - [ ] Add empty states for boards without columns/tasks
- [ ] **Add notifications**
  - [ ] Use Phoenix LiveView flash messages for success/error
  - [ ] Style flash messages with Tailwind CSS
- [ ] **Add confirmation dialogs**
  - [ ] Add confirmation for board deletion
  - [ ] Add confirmation for column deletion (mention tasks will be deleted)
  - [ ] Add confirmation for task deletion
- [ ] **Error handling**
  - [ ] Add proper error messages for validation failures
  - [ ] Handle edge cases (deleting last column, etc.)
  - [ ] Add 404 pages for missing resources
- [ ] **Final Quality Checks**:
  - [ ] Run `mix test` and ensure all tests pass (510 tests, 0 failures)
  - [ ] Run `mix test --cover` and verify coverage meets threshold (94.60% coverage)
  - [ ] Run `mix credo --strict` and fix any issues (no issues found)
  - [ ] Run `mix sobelow --config` and fix any security issues (no issues found)
  - [ ] Run `mix precommit` to run all checks together (all checks passed)

Starting with UI/UX improvements

We start by asking TideWave to complete the first two tasks under UI/UX improvements. Less than five minutes later we have some sparkle.

Cleaning up Authentication

This is the last episode before we get back to our original plan. The authentication system currently in place is what was generated by running the mix phx.gen.auth command. The styles were cleaned up a little when I asked Claude to create a nice style for the entire site. But the behaviour is the generated form and is not what I want. In part 14 we will attack this head on.

Setting permissions for users

Currently every user can do everything in the application. A read only user can delete a board or make any type of change they want. Let’s fix that.

Focus on Owners first

First I want to focus on ensuring the board owner can do board-level actions and other users cannot. Let me start by listing out the things that only owners can do:

• Edit and delete their boards
• Add new columns to a board
• Edit or delete columns from their boards
• Reorder columns (including drag-and-drop)

I think this is a good list. Let’s ask TideWave to make these changes.