Love this video and its what I've been looking for. I wish cursor and your browser was full screen and no video in the background. Also wish for 4K video, but other than that, awesome job!
Thanks for watching and for the feedback! I nixed the background video and zoomed in a bit more on my newer videos. I am gradually improving my equipment and video editing skills.
Thanks! I have been experimenting with this combination and so far I am impressed. I plan to create more videos as I discover new and better ways to leverage AI with Rails.
Nice, thanks for sharing and I’m looking forward to more videos like this. One small suggestion would be to loose the background and make the window fullscreen for the video to maximize readability of the code. No need to see you typing, we can rear it 😀 🙏
Thanks for watching and providing feedback! After watching the video back on a smaller screen I agree with your suggestion. I have half of a video recorded using the same technique but going forward I will maximize the editor. 🙏
YW, thanks for the feedback! I have improved this in some of my later videos. I need to be more consistent though, I tend to forget to zoom in when I am recording.
User stories are not requirements. Should have requirements as a strategic objective or even an initiative. Break those out into epics with requirements. User stories are then created to further refine a requirement into smaller sprint length chunks.
Thanks for your feedback. You're making a common argument for distinguishing the difference between user stories and traditional formats, but it's not set in stone. Here's a definition from the Agile Business Consortium: "A User Story is essentially a well-expressed requirement. The User Story format has become the most popular way of expressing requirements in Agile for a number of reasons." That being said, I believe it's more important to focus on distinguishing between functional and non-functional requirements rather than getting too caught up in comparing traditional requirement formats to user/goal-oriented formats. On larger projects with bigger teams, more extensive analysis is often needed before introducing user stories. However, on smaller projects with smaller teams, the problem may be well understood, and the need for additional ceremony is minimal.
Thank you for the feedback! In my more recent videos, I’ve started zooming in a bit further. Sometimes, when I’m coding on projects, I zoom out and forget to adjust it back before recording. I’m working on improving this as I develop better recording habits.
Amazing! Only video that does it from start to end. Love your videos, thanks so much.
You're welcome! Thanks for the kudos!
Keep up the good work! We need more RoR channels like this.
Thanks! I agree.
Love this video and its what I've been looking for. I wish cursor and your browser was full screen and no video in the background. Also wish for 4K video, but other than that, awesome job!
Thanks for watching and for the feedback! I nixed the background video and zoomed in a bit more on my newer videos. I am gradually improving my equipment and video editing skills.
Great guide! Very useful and interesting video. Thank you so much!
Your're welcome! I am glad you found it useful.
That was really great
Thanks! I have been experimenting with this combination and so far I am impressed. I plan to create more videos as I discover new and better ways to leverage AI with Rails.
Nice, thanks for sharing and I’m looking forward to more videos like this. One small suggestion would be to loose the background and make the window fullscreen for the video to maximize readability of the code. No need to see you typing, we can rear it 😀 🙏
Thanks for watching and providing feedback! After watching the video back on a smaller screen I agree with your suggestion. I have half of a video recorded using the same technique but going forward I will maximize the editor. 🙏
Thank you for this. Font could be slightly bigger, only gripe.
YW, thanks for the feedback! I have improved this in some of my later videos. I need to be more consistent though, I tend to forget to zoom in when I am recording.
User stories are not requirements. Should have requirements as a strategic objective or even an initiative. Break those out into epics with requirements. User stories are then created to further refine a requirement into smaller sprint length chunks.
Thanks for your feedback. You're making a common argument for distinguishing the difference between user stories and traditional formats, but it's not set in stone. Here's a definition from the Agile Business Consortium:
"A User Story is essentially a well-expressed requirement. The User Story format has become the most popular way of expressing requirements in Agile for a number of reasons."
That being said, I believe it's more important to focus on distinguishing between functional and non-functional requirements rather than getting too caught up in comparing traditional requirement formats to user/goal-oriented formats. On larger projects with bigger teams, more extensive analysis is often needed before introducing user stories. However, on smaller projects with smaller teams, the problem may be well understood, and the need for additional ceremony is minimal.
@ hmm good points. I like your ideas here and would agree with the premise.
please increase the text size...its barely visible what your typing
Thank you for the feedback! In my more recent videos, I’ve started zooming in a bit further. Sometimes, when I’m coding on projects, I zoom out and forget to adjust it back before recording. I’m working on improving this as I develop better recording habits.
@@AIonRails-v9s its very hard to find rails video, nobody does....hope u will continue. If possible make a video on content rating system
Really? i see code barely
Really. 🧐