An interesting read from link
My favorite list
Perspective #1 - You don’t need hundreds of engineers to build a great product
[Siva] - Have a set of ideas, experiment, fail, learn, unlearn, relearn, and Build a vision of the product not under the pressure of timelines
Perspective #2 - Simple Outperformed Smart
[Siva] - Start to crawl before you learn to run
Perspective #3 - Our highest impact findings would always come within the first and last few hours of the audit.
[Siva] - Functionality, Scalability, Performance matters
Perspective #4 - Business logic flaws were rare, but when we found one they tended to be epically bad
[Siva] - Product is a for customer need not for experimenting technology. Build what is needed for the customer, provide the customer experience
Perspective #5 - Quick turnarounds on fixing vulnerabilities are usually correlated with general engineering operational excellence.
[Siva] - Quality ideas come from the domain, data, and functional understanding. Think from the long term no near term fixes
Good Read - Link
- How does the number of reported defects in source code files correlate to source code quality?
- How much longer development time is needed to resolve an issue in files with low-quality source code?
- To what extent is the code quality of a file related to the predictability of resolving issues on time?
Keep Thinking!!!
