#LậpTrình #KiếnTrúcPhầnMềm #CSharp #Encapsulation

Phần 4: Encapsulation & Designing for Ignorance

Đừng hiểu sai encapsulation chỉ là "private fields + getters/setters". Đó là cơ học.

Encapsulation thực sự là về **epistemic**: Ai được phép biết gì và ai cần bị… làm ngơ.

Mỗi thông tin bạn expose ra ngoài là một dependency, một rủi ro coupling. Encapsulation tồn tại để giới hạn sự lây lan kiến thức này, giúp hệ thống có thể refactoring và phát triển độc lập.

Hãy xem ví dụ về `Order`:
❌ Sai: `p

停止错误地将对象当作数据容器！掌握“Tell, Don’t Ask”原则：别问对象要数据，而是告诉它该做什么。这样能提高封装性、减少重复代码，让逻辑更清晰。举例说明，Shop 类不应直接操作 Account 的余额，而应调用 account.canAfford() 和 account.withdraw() 让 Account 自己处理。这样写更符合面向对象设计。

#OOP #Programming #TDA #Encapsulation #CodeQuality #LậpTrình #ThiếtKếPhầnMềm #TốiƯuMã #LậpTrìnhHướngĐốiTượng #NguyênTắcLậpTrình

https://dev.to/jonghwayoo03_dev/stop-asking-for-data-master-the-tell-dont-ask-principle-373g

Private Fields Use # Symbol?!

Private fields are HIDDEN! The # symbol makes properties truly private. You can't access them from outside, even with bracket notation. This is REAL privacy!

#javascript #javascripttricks #privatefields #symbol #encapsulation #javascriptweird #javascriptquiz #codingchallenge #javascriptshorts #javascriptwtf #classprivacy #advancedjavascript

https://www.youtube.com/watch?v=ycxs4Sb_7Eo

Brent's Encapsulated C Programming Rules (2020)

https://retroscience.net/brents-c-programming-rules.html

#HackerNews #Brent #C #Programming #Encapsulation #CodingRules #RetroScience

After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:

* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

#NullCoalescing #NullChaining #LanguageDesign

Một bài viết từ /u/EgregorAmeriki thảo luận về đóng gói (encapsulation) trong lập trình không cần dùng từ khóa private, thay vào đó áp dụng thiết kế dựa trên giao diện (interface-based design) để tối ưu tính bảo mật và tính linh hoạt của code.

#Lập_trình #Object_Oriented #Design_Pattern #Công_nghe #Thiet_ke_phan_mem #Programing #OOP #SoftwareDesign #Encapsulation #InterfaceDesign

https://www.reddit.com/r/programming/comments/1o934q9/encapsulation_without_private_a_case_for/

Artemis II Payload Integration 🛰️🧑‍🚀

#ArtemisII #CapeCanaveral #CarruthersGeocoronaObservatory #Encapsulation #Florida #IMAP #InterstellarMappingandAccelerationProbe #JohnFKennedySpaceCenter

⏩ 16 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=16&user=OptimusPrimeBot&ilshowall=1&offset=20250920010947