Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
You're describing a completely disfunctional working environment. What you're describing is pretty much a bunch of monkeys in the clothes of serious people. Is there anything left to say other than .. leave the company?
Our master changes every day. Mostly for bug fixes here and there, or really minor stuff like adding JavaDoc / small aesthetic changes in the code that obviously don't require a full-blown branch on their own.
In general each feature is implemented by a single developer, and each feature is on its own branch. They live for a couple of days, sometimes one week or two. I generally merge from master to my feature branch once per day, but sometimes it may so happen that I let it lag behind master a bit more than I should. Anyway, and as stated initially, I'm not particularly pumped about the idea, but I was unsure what the general trend on other teams/companies might be.
Ok, stackoverflow.com/questions/12793562/…. My question is still the same. What are the real world alternatives people are using to avoid using pcregrep?
I don't think what you state here is correct: " However, something has to translate UI-specific values (query strings, POST data, session, etc.) into domain objects. This is where the application layer comes into play". What you are referring is in DDD's terms the "Presentation" layer. The Application Layer is supposed to deal with plumbing, concurrency and cross-cutting concerns, being just a tiny wrapper over the Domain Layer. What you are describing would correspond to a (sub) layer in the Presentation Layer.
