Welcome to Project Patterns!
This wiki is about sharing project experiences and using simple terms to explain common challenges. The main focus is on software projects, however, many of the examples will apply to any type of project.
Everyone is welcome to read and contribute. Please adhere to the following Project Patterns Code of Conduct.
|Clean up the living room before moving the couch||The code may be in a bad state even it not visible from the outside. It may need cleaning up before changes are made.|
|Get to know each other||Invest time to get to know the people your work with. Your stakeholders as well as your fellow team members. Grabbing coffee, lunch or a beer together is well worth the investment. This establishes trust. And once you feel comfortable in a team it’s easier to discuss questions/topics openly.|
|Mock it till you make it||The goal is to provide an early visual prototype of a system to get user feedback. This can prevent a lot of useless features from being fully implemented and delivered to the end customers.|
|Counting coins||Some coding work requires high concentration & there is no point in asking the person counting every few minutes how much they have counted so far. Deep work is a useful strategy to allow employees to focus and get in the flow for longer periods every day.|
Need help? We will help you with your wiki as needed. To start, try checking out these helpful links:
- MediaWiki guide (e.g. navigation, editing, deleting pages, blocking users)
- Miraheze FAQ
- Request settings changes on your wiki. (Extensions, Skin and Logo/Favicon changes should be done through Special:ManageWiki on your wiki, see ManageWiki for more information.)