Explore >> Select a destination
|
You are here 
|
jordanorelli.com | ||
| | | | |
www.alexedwards.net
|
|
| | | | | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | Interfaces in Go Name Your Interface Arguments Keep Interfaces Small Accept Interfaces, Return Concrete Types Don't Return Concrete Types Use existing interfaces Don't Force Interfaces Embedding Interfaces Upgrading Interfaces Standard Library Interfaces Tight Coupling Dependency Injection Refactoring Considerations Testing More flexible solutions? Conclusion This post is going to explain the importance of interfaces, and the concept of programming to abstractions (using the Go programming language), by ... | |
| | | | |
blog.percywegmann.com
|
|
| | | | | Don't Overthink It | |
| | | | |
opguides.info
|
|
| | | Chapter 35 - Reverse Engineering # Software # Anyone know of good resources for learning binary reversing? Not particular tools necessarily, but like theory and how to think @XMPPwocky on Twitter An Opinionated Guide on How To Reverse Engineer Software is decent. for me personally: know some assembly, and in particular make sure you know the calling conventions for your platform. when starting out, do it on binaries you can actually run in a debugger and see whats actually happening at runtime. | ||
