Career advice threads may be removed at the moderators discretion based on response to the thread." This sub is for discussing issues specific to experienced developers.Īny career advice thread must contain questions and/or discussions that notably benefit from the participation of experienced developers. Violations = Warning, 7-Day Ban, Permanent Ban. This includes posts that could be interpreted as trolling, such as complaining about DEI (Diversity) initiatives or people of a specific sex or background at your company.ĭo not submit posts or comments that break, or promote breaking the Reddit Terms and Conditions or Content Policy or any other Reddit policy. No racism, unnecessarily foul language, ad hominem charges, sexism - none of these are tolerated here. If you have less than 3 years of experience as a developer, do not make a post, nor participate in comments threads except for the weekly “Ask Experienced Devs” auto-thread. Do not participate unless experienced (3+ years) This community leans towards being a specialized subreddit facilitating discussion amongst individuals who have gained some ground in the IT world.įor an idea of what is encouraged in this subreddit and what is not (please report anything that does not follow the rules): Rulesġ. Although it is pronounced by many as "ME-see", the author insisted that it should be pronounced as "Meese" like Greece or niece.Welcome to the /r/ExperiencedDevs subreddit! We hope you will find this as a valuable resource in your journeys down the fruitful CS/IT career paths. There is some debate regarding the pronunciation of the acronym MECE. However, there are cases where redundancies are desirable or even necessary. Īnother attribute of MECE thinking is that, by definition, it precludes redundancies. For instance, while it may be desirable to classify the answers to a question in a MECE framework so as to consider all of them exactly once, forcing the answers themselves to be MECE can be unnecessarily limiting. Īlso, MECE thinking can be too limiting as mutual exclusiveness is not necessarily desirable. The MECE concept has been criticized for not being exhaustive, as it doesn't exclude superfluous/extraneous items. By reorganizing the information using MECE and the related SCQA storytelling framework, the point of the topic can be addressed quickly and supported with appropriate detail. In Six Sigma, the DMAIC process is used, but executive audiences looking for a summary or overview may not be interested in the details. In some technical projects, like Six Sigma projects, the most effective method of communication is not the same as the problem solving process. Similarly, MECE can be used in technical problem solving and communication. Strategy consultants use MECE problem structuring to break down client problems into logical, clean buckets of analysis that they can then hand out as work streams to consulting staff on the project. A non-MECE example would be categorization by nationality, because nationalities are neither mutually exclusive (some people have dual nationality) nor collectively exhaustive (some people have none). Examples of MECE arrangements include categorizing people by year of birth (assuming all years are known), apartments by their building number, letters by postmark, and dice rolls. The MECE principle has been used in the business mapping process wherein the optimum arrangement of information is exhaustive and does not double count at any level of the hierarchy. It was developed in the late 1960s by Barbara Minto at McKinsey & Company and underlies her Minto Pyramid Principle, and while she takes credit for MECE, according to her interview with McKinsey, she says the idea for MECE goes back as far as to Aristotle. The MECE principle, ( mutually exclusive and collectively exhaustive) is a grouping principle for separating a set of items into subsets that are mutually exclusive (ME) and collectively exhaustive (CE).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |