Questions

After reading the last two chapters, you should be able to cover the responses for the following questions.

Don’t limit yourself to a short answer, try to come up with a more detailed answer.

1. What is a critical section?
2. What is a race condition?
3. Why do we need concurrency/multithreading?
4. What are atomics?
5. What is a deadlock?
6. What is a limitation when using unnamed pipes?
7. When do we need to use sockets?
8. Why is testing the multithreading code harder than testing single-threaded code?
9. What is a class?
10. What is encapsulation good for?
11. What is memory fragmentation?
12. What is a core dump?
13. What is rubber duck debugging?
14. What is a packet sniffer and where it can be used?
15. What are the SOLID principles?
16. What is the difference between cohesion and coupling?
17. What are the differences between a thread and a process?
18. What are the differences between a mutex and a semaphore?
19. What makes the code readable?
20. How would you design a software system for scalability?
21. How do you write secure code?
22. What is the anti-pattern called ‘The golden hammer’?
23. Why would you want to refactor the code?
24. Why it’s a bad design to duplicate code?
25. What is problematic in long methods? How would you solve this?
26. What is problematic with duplicated code? How would you solve this?
27. What is problematic with having multiple switch statements on related objects? How would you solve this?
28. What architectural pattern involves decoupling components and deploying them on different computers?
29. What would you do to understand if the code base you’re working on has a bad design?
30. What design pattern involves multiple objects that are interested in the state of an object and receives a notification when the state changes?