dethstrobe

6 ms·

1. 1.▲
   Video Demo: AI Employee Scheduling(youtube.com)

   2 points by dethstrobe 2mo ago|0 comments
2. 2.▲
   by dethstrobe 6mo ago

   I've been using RWSDK since it was in v0 last year. I really like how simple and elegant it is. And now with v1 there are some really logical patterns that I really enjoy. Like returning Responses from server actions and then the frame
3. 3.▲
   Narrative-Driven Development: BDD+TDD+Living Documentation in One Workflow(test2doc.com)

   1 points by dethstrobe 7mo ago|0 comments
4. 4.▲
   RedwoodSDK Tutorial with Test2Doc(test2doc.com)

   1 points by dethstrobe 8mo ago|1 comments
5. 5.▲
   by dethstrobe 8mo ago

   So last year the Redwood team, after launching v0 also launched a tutorial to built a non-trivial webapp using their framework. But they're now getting ready for v1 and introduced a few breaking changes so made their tutorial obsolete.
6. 6.▲
   by dethstrobe 1y ago

   That's great to know. I was thinking about tackling this from the highest level of abstraction first, so the user interface. I plan on supporting Playwright first for MVP, and then expanding in to Cypress, and maybe even unit testing f
7. 7.▲
   Left Google to solve documentation hell: What if your tests could write your doc(test2doc.com)

   1 points by dethstrobe 1y ago|4 comments
8. 8.▲
   by dethstrobe 1y ago

   I recently left Google. I made a post explaining why, if anyone is interested. (Warning: it's pretty long) https://dethstrobe.com/blog/20250522-google/ Anyway, the ball is currently in the employer's cou