Joined devRant on 4/12/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
You need a DecoratorInjectorFactory, which generates a DecoratorInjector, which injects a fully configured Decorator object into your class, configured with XML.
@Messer, both. We have a massive feature, we designed, but no one bothered to sit down and think about the UX implications, so now that we're about to release it, the main stakeholders/managers are bringing up issues with UX. Like getting rid of some screens, redesigning and merging others.
In vim, that would be :adgxthz
!important. !important everywhere.
NSFW warning! :-)
I think no feature should be so monolithic as to require 4 months of continuous dev time.
1. Break it down to smaller, more manageable, testable deliverables.
2. Use proper topic branches to avoid disrupting other smaller features.
3. Have UX testing with wireframes, rather than updating design documents and specifications after development has begun.
4. Enforce consistency with the rest of the application rather than developing everything as one off pieces.
It's been a $&it-show all around.
I have absolutely given up on striving for coherence, and have instead opted to minimize the amount of work I have to do between now and when it all falls apart and we have an inevitable rewrite