| ▲ | milch 4 hours ago | |||||||
I don't think I've ever been unhappier than working on a Rails project. See a bug on the site - something is rendering incorrectly. grep to find the view. Great, there's a method that is being called to render the buggy section. Grep for the method name - 0 hits. Amazing, it's something that is synthesized somewhere and I have no idea where. Guess I'll stop what I'm doing and read docs for an hour. If you do nothing but use Rails all day, sure, but the whole convention over configuration thing is such a huge anti pattern to me. | ||||||||
| ▲ | ramon156 an hour ago | parent | next [-] | |||||||
I would advice reading the "efficient rails" book, which explains a lot about how to debug RoR apps. | ||||||||
| ▲ | 3 hours ago | parent | prev | next [-] | |||||||
| [deleted] | ||||||||
| ▲ | jimbokun 3 hours ago | parent | prev | next [-] | |||||||
I’ve had similar experiences with Spring Boot Java applications. Methods in stack traces that don’t exist in source code but are magicked into existence by annotations. | ||||||||
| ||||||||
| ▲ | craigmcnamara 4 hours ago | parent | prev [-] | |||||||
method(:name).source is your friend | ||||||||
| ||||||||