3 ms·
I've been a Rails dev for a long time. I've tried a bunch of things and keep coming back to it for the same reasons as you. I'm incredibly productive in it. Fo
by SkyPuncher 3y ago
I've been a Rails dev for a long time. I've tried a bunch of things and keep coming back to it for the same reasons as you. I'm incredibly productive in it.
For the longest time, my primary complaint has been a lack of documentation/conflicting information when you break from convention. It can be extremely challenging to find/understand the "blessed" way of doing things. Thankfully, ChatGPT is extremely good at providing a starting point for this stuff.
- theonething 3y agoCould you give an example of how ChatGPT helped you specifically with Rails?
- SkyPuncher 3y agoThe one that I use it the most for is writing ActiveMigrations while integrating with some of Postgres features. There's a lot of settings that get pass-thru to the DB, but aren't clearly documented. I know it's possible, I just can't remember the syntax. Same thing with some of the more advanced Model relationships. I just don't write _that_ many relationships, so I tend to forget how Rails wants certain things defined. Since a lot of things rely on config, rather than "normal" runtime code, it can be frustrating to debug. ChatGPT just gets me to the right answer. --- It's also pretty useful at gut checking DB design. There's been a few times where it's suggested a different approach than what I expected and I've preferred it's suggestions.
- theonething 3y agoWow, thanks. I gotta start checking out how to leverage ChatGPT more.