Related Content
 |
Joking Around and Taking Work Seriously You may be totally serious about your job yet give the impression that you’re not. Laughter and fun help some people tackle the high-priority, stress-inducing problems they face every day, but it can also be misinterpreted by others that they aren't taking their work seriously. How are people perceiving your behavior? |
|
 |
How to Make Sure Your Website Is Fully Accessible Ensuring accessibility to websites, applications, tools, platforms, and other forms of technology is not only a legal requirement; it should also be a social responsibility of web developers, testers, and other software professionals. Here are some basic recommendations to keep in mind to make any website accessible. |
|
 |
Security Testing: A Constructive Mindset with a Destructive Approach A typical tester mimics end-users, who are constructive when exploring an application’s functionality. But the role of a security tester is different. Their focus is mainly on mimicking hackers, who are intentionally destructive. A solid security strategy should balance both constructive and destructive efforts. |
|
 |
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |
|
 |
4 Tips to Refocus Stale Standups The daily standup is supposed to get everyone on the same page and make teams more productive and efficient. But it’s easy for this short meeting to become stale and stop providing any real benefit. Here are four ways to get out of the slump of merely delivering status updates and re-energize your daily standups. |
|
 |
Beware of Success Stories The tendency to look back and think you know what contributed to a success is called survivorship bias. It occurs when you make a decision or take some action based on past successes while ignoring past failures. That's why it's important to approach reports of successful projects with a healthy dose of skepticism. |
|
 |
Trusting Your Data: Garbage In, Garbage Out Poor quality input will always produce faulty output. Improper validation of data input can affect more than just security; it can also affect your ability to make effective business decisions. Bad data can have impacts on how you make quantitative decisions or create reports, if you can’t trust the data you receive. |
|
 |
Lessons Learned from Product Failures Being agile is all about learning from failures and building on experiences. This applies to not just individuals, but even to large organizations. The key is being transparent and objective in accepting and understanding failures, and taking away lessons for future actions and decisions. Just keep innovating. |
