Mynd for software engineers
Software Engineer, as it appears in the app.
A software engineer designs, codes, tests and fixes, in a team. Architecture decisions and the reasons for each choice are lost quickly.
The ready-made structure
Score 82 out of 100. What the score means.
The structure goes from foundations to collaboration: Foundations, Languages, Architecture, Development, Infrastructure, Systems and Collaboration. An architecture decision goes in Architecture, Design; a bug in Development, Debugging.
The full tree is at the end of this page, with the names as they are in the app.
Suggested Context phrases
The structure says what each record is about. The Context phrases, which each person creates, say the rest. For this profession, some that tend to serve:
Architecture decision Bug fixed For the team Technical debt
A report that sends itself
One slot for the team. Every Friday, the records marked Architecture decision and Technical debt go to everyone.
What you gain: Decisions are written down and the team does not repeat discussions.
The release notes of a version, sent once on launch day.
In this version, Start, each person has 14 automatic search sends and 14 card sends; in Run, they will be able to have as many as they need. Each send has its own search, its own recipients and its own frequency: daily, weekly, monthly or on a date. Emails go out from the person's own email account, and each recipient receives their own.
The full tree
Foundations3 Types
- Foundations/LogicBooleanAlgorithmsComplexity
- Foundations/StructuresLinearTreesGraphs
- Foundations/ParadigmsOOPFunctionalProcedural
Languages3 Types
- Languages/CompiledCCPlusPlusRust
- Languages/InterpretedPythonJavaScriptRuby
- Languages/ManagedJavaCSharpKotlin
Architecture3 Types
- Architecture/DesignPatternsPrinciplesModularity
- Architecture/SystemsMonolithMicroservicesServerless
- Architecture/DataModelsSchemasPipelines
Development3 Types
- Development/CodingStyleRefactoringDocumentation
- Development/TestingUnitIntegrationE2E
- Development/DebuggingTracingProfilingFixing
Infrastructure3 Types
- Infrastructure/EnvironmentsLocalStagingProduction
- Infrastructure/CIPipelinesAutomationQuality
- Infrastructure/CDDeploymentsRollbacksMonitoring
Systems3 Types
- Systems/OSProcessesMemoryScheduling
- Systems/NetworksProtocolsRoutingSecurity
- Systems/DatabasesSQLNoSQLIndexing
Collaboration3 Types
- Collaboration/TeamsRolesAlignmentCommunication
- Collaboration/ProductRequirementsRoadmapFeedback
- Collaboration/OpsMonitoringIncidentsReliability
