Write your software documents assuming that the readers know flat zero about the topic in that document. #embedded #Software #softwaredevelopment #softwaredeveloper #softwarethatmatters
Make your system predictable. Check it with this question: Can you say the maximum CPU load at any given moment? #embedded #Software #softwarethatmatters
Always ask what to do if out-of-range output comes in over the data bus. Throwing it away is a very different architecture than buffering or stopping data reception. #embedded #Software #softwarethatmatters
The description of interfaces is probably the most volatile part of any embedded specification - data fields, order, data types, and value range. Clarify this first. It takes a lot of time, especially if other teams are involved. #embedded #Software #softwarethatmatters
Not all of the code needs to be 1st class. Be pragmatic. Focus on more essential modules first. #embedded #Software #softwarethatmatters
Do not guess what users want. Ask them. 9 out of 10 times, you'll get a different answer than you expect. #embedded #Software #softwarethatmatters
Include the dynamics of your system/software into architecture documents. It is often an overlooked part, which creates a lot of questions. #embedded #Software #softwarethatmatters
Give your inputs and outputs ID in the requirements documents; it will be easy to trace them to test cases. #embedded #Software #softwarethatmatters
When estimating how long it will take to write code, factor in clarifying requirements and interfaces. They usually take 2x more time than planned. #embedded #Software #softwarethatmatters
Contrary to most coding guidelines, 100% unit test coverage is not necessary all the time. Put some common sense into it. #embedded #Software #softwarethatmatters
Include fault-injection points into your design right from the start. They are a fantastic help for testers and for your debug sessions. #embedded #Software #softwarethatmatters
Complexity usually grows along the project development timeline. Therefore, keep it simple at the beginning. Things will complicate themselves. #embedded #Software
Make gradual quality improvements. Setting high goals at the beginning is usually less efficient in Software Quality improvement.
Most errors come from the interaction of modules, not from the modules themselves.
Try to include scheduled resets into your systems. It will help mitigate a whole family of common embedded systems issues, including Single Event Upset (SEU).
United States 트렌드
- 1. #FanCashDropPromotion 1,199 posts
- 2. #เพียงเธอตอนจบ 1.44M posts
- 3. LINGORM ONLY YOU FINAL EP 1.43M posts
- 4. Apple TV 9,314 posts
- 5. trisha paytas 1,263 posts
- 6. zendaya 4,096 posts
- 7. #FridayVibes 6,925 posts
- 8. No Kings 215K posts
- 9. GAME DAY 33.2K posts
- 10. #SlideToMe 14.9K posts
- 11. #Yunho 24.9K posts
- 12. Good Friday 60.6K posts
- 13. Mamdani 279K posts
- 14. Shabbat Shalom 4,590 posts
- 15. Cuomo 120K posts
- 16. F1 TV 2,890 posts
- 17. Justice 336K posts
- 18. Bolton 283K posts
- 19. New Yorkers 47.8K posts
- 20. Happy Friyay 1,519 posts
Something went wrong.
Something went wrong.