Longtime software developer turned performance and life coach.
When you ask a question, show your effort, provide all the details that will help someone to help you and be precise.
- StackOverflow question checklist
- Open letter to students with homework problems
- What have you tried
- Short, Self Contained, Correct (Compilable), Example
- How To Ask Questions The Smart Way
- Don't be a help vampire
- How does accepting an answer work
- Ask about the problem rather than your "solution"
- Answering your own question is acceptable, just do it the right way
When you answer a question, don't just paste your code. Your answers will be much better when you explain why your code is doing what it does and how it achieves the asker's goal. It makes it a whole lot easier to follow along. As it is I am much more inclined to up-vote answers that have an explanatory text about what the code is doing and why it is written as it is.
Obligatory link whenever someone thinks they are improving security by imposing all sorts of rules on password composition: Password strength
- Stack Overflow 17.7k 17.7k 44 gold badges5555 silver badges7474 bronze badges
- Software Engineering 7.8k 7.8k 33 gold badges2727 silver badges3333 bronze badges
- User Experience 5.6k 5.6k 33 gold badges1919 silver badges2929 bronze badges
- Meta Stack Exchange 358 358 11 silver badge1111 bronze badges
- Project Management 211 211 11 silver badge66 bronze badges
- View network profile →
Top network posts
- 146 What is the benefit of not using Hungarian notation?
- 88 What's the difference between faking, mocking, and stubbing?
- 55 Pros/cons of splash-screen with articifial loading delay
- 52 Safely fixing production database data
- 40 Removing '#$A' from Delphi string
- 35 "Weak reference": down to earth explanation needed
- 27 What should I use? UTF8 or UTF16?
- View more network posts →