- Published on
Understanding Go interfaces requires a shift in thinking, especially for those accustomed to explicit interface declarations in other languages. With practice and familiarity, the concepts become more intuitive and easier to work with.
Shift
All Posts
- js (9)
- go (8)
- javascript (8)
- native-functions (5)
- higher-order-functions (5)
- encapsulation (5)
- abstraction (5)
- immutability (5)
- seperation-of-concerns (5)
- function-composition (5)
- native (4)
- functional-programming (4)
- indigenous (3)
- prayers (3)
- ai (2)
- innovation (2)
- aws (2)
- ci (2)
- microservices (2)
- security (2)
- linux (2)
- arch-linux (2)
- guide (2)
- computing (2)
- filter (2)
- map (2)
- reduce (2)
- interfaces (2)
- k8s (2)
- diversity (1)
- wrangling (1)
- growth (1)
- maintainability (1)
- c (1)
- codebuild (1)
- codepipeline (1)
- syntax (1)
- logic (1)
- errors (1)
- debugging (1)
- indigenous-wisdom (1)
- business-practices (1)
- devsecops-shifting-left (1)
- devops (1)
- shift-left (1)
- service-maturity (1)
- operational-efficiency (1)
- product-quality (1)
- ethnography (1)
- ux (1)
- design (1)
- git (1)
- hooks (1)
- accelerate (1)
- project (1)
- structure (1)
- risks (1)
- development-velocity (1)
- stem (1)
- hiring (1)
- joy (1)
- thinking (1)
shift (1)
- algorithms (1)
- land-utilization (1)
- corporate-responsibility (1)
- tutorial (1)
- data-structures (1)
- json (1)
- xml (1)
- data (1)
- medicine (1)
- wisdom (1)
- naming (1)
- oop (1)
- platform-maturity (1)
- efficiency (1)
- platform (1)
- maturity (1)
- roadmap (1)
- method-sets (1)
- abilities (1)
- robots (1)
- sre (1)
- cybersecurity (1)
- slsa (1)
- nist (1)
- ssdf (1)
- eo-14028 (1)
- ubuntu (1)
- eks (1)
- kubernetes (1)
- kates (1)
- este-mvskokvlke (1)
- muscogee (1)
- estvlke (1)
- creek (1)
- okalahoma (1)
- tulsa (1)