Cool Guides
Rules for Posting Guides on Our Community
1. Defining a Guide Guides are comprehensive reference materials, how-tos, or comparison tables. A guide must be well-organized both in content and layout. Information should be easily accessible without unnecessary navigation. Guides can include flowcharts, step-by-step instructions, or visual references that compare different elements side by side.
2. Infographic Guidelines Infographics are permitted if they are educational and informative. They should aim to convey complex information visually and clearly. However, infographics that primarily serve as visual essays without structured guidance will be subject to removal.
3. Grey Area Moderators may use discretion when deciding to remove posts. If in doubt, message us or use downvotes for content you find inappropriate.
4. Source Attribution If you know the original source of a guide, share it in the comments to credit the creators.
5. Diverse Content To keep our community engaging, avoid saturating the feed with similar topics. Excessive posts on a single topic may be moderated to maintain diversity.
6. Verify in Comments Always check the comments for additional insights or corrections. Moderators rely on community expertise for accuracy.
Community Guidelines
-
Direct Image Links Only Only direct links to .png, .jpg, and .jpeg image formats are permitted.
-
Educational Infographics Only Infographics must aim to educate and inform with structured content. Purely narrative or non-informative infographics may be removed.
-
Serious Guides Only Nonserious or comedy-based guides will be removed.
-
No Harmful Content Guides promoting dangerous or harmful activities/materials will be removed. This includes content intended to cause harm to others.
By following these rules, we can maintain a diverse and informative community. If you have any questions or concerns, feel free to reach out to the moderators. Thank you for contributing responsibly!
view the rest of the comments
I'm luckily enough to work on a small team like the one you described, and yeah - our trello board isn't fully fleshed out. We can put vague descriptions of what needs to be done and the team gets it done.
I think SMART goals are one of those rare times where an HR course writer unintentionally hit on something that some people need to hear. There's a junior engineer on my team whose goal was just, "I want to get better at infosec" - not measurable, time boxed, etc. by trying to at least hit one or two of the guidelines, they were able to flesh out this goal into things like "I want to attend a major security conference this year" and "I will study for, and achieve my Security+ cert".
It worked for them - and helped them clarify their broad nebulous goal into smaller specific and achievable goals - but obviously like all business/hr things SMART goals aren't for everyone.
That's a fair point about SMART being exactly what some people may need to hear. I hadn't thought about it that way.
That's also a process that falls entirely under "common sense". No need for "SMART" to have a chat with your Junior and agree on what can be done to meet his desired outcome.