4 ms·
In my experience, most clients we worked with did not request Rails, it was foisted upon by developers who say the five minute blog video, tried to model the bu
by static_typed 13y ago
In my experience, most clients we worked with did not request Rails, it was foisted upon by developers who say the five minute blog video, tried to model the business problem, failed, left for shiny new gig, the client is left vulnerable to the many, many security issues, and a code base that brings tears to the eye of even a hardened developer.
The worst development gig out there? Walking into a Rails code base more than six months old. You are probably the third person to attempt taming the stink feet of magic magic code and thousands of useless unit tests and cucumber drivel that looks fab in a pretty graph but tests almost none of the core important business logic nor really helps anyone understand what was actually requested.
- bbeneschott 13y agoWorse than a six month old PHP project?
- moepstar 13y agoI guess that might be true of any inherited codebase in any language - i shudder to think of encountering something written in PERL from an other developer and having to maintain that code.
- MetaCosm 13y agoIMHO, the pain of being handed code is related to its "magic". The more magic, clever, interesting contortions that are present, the less likely you are to get grips on it in any sensible time. Ruby & Rails give lots of tools to create insanely hard to unwind stacks, but I am not sure they are worse than Django & Python (custom loader [importer], decorators everywhere)... The real bitter pill is that these systems are created with the best of intentions, to make them more maintainable, more DRY, more configurable, more portable... but they generally miss the mark and cause pain for all involved.