According to Golang documentation, “An interface type is defined as a set of method signatures”. Fair enough, and that sounds like it is quite similar to how interfaces work in other languages. While there certainly are similarities, there are also nuances that you would be better served understanding before leveraging this construct.
In this course, we will take a simple example (a manufactured one, sure) to understand how interfaces work in Go, and do a bit of LIVE coding. The idea is that by the end of this course, you will have a good sense of how interfaces work, and when they may be a good fit for the problem you are trying to solve.
Purchase course in one of 2 ways:1. Go to https://getsnowpal.com, and purchase it on the Web
2. On your phone:
(i) If you are an iPhone user, go to http://ios.snowpal.com, and watch the course on the go.
(ii). If you are an Android user, go to http://android.snowpal.com.
Building a Mobile App - Part I (Starting to build a native mobile app, and wondering which way to go?)
Building a Mobile App - Part II (React Native, Flutter, and some others)
Aggregations in Mongo - Much faster and the best (and maybe only?) alternative in many cases
Make your Git commits frequent so you run into fewer merge conflicts
Heroku Cloud Application Platform - why it will help your TTM (Time to Market)
Building a Brand New Application? Looking for a way to reduce your ramp up time?
Development Efficiency - Are you bouncing your servers too often?
Code Quality - How can you assess the quality of a codebase before reviewing a single line of code?
Backwards Compatibility Issues - a few ways to ensure that you do not run into them
Native Mobile App - Design Patterns & Separation of concerns (Part 1)
Native Mobile App - Design Patterns & Separation of concerns (Part 2)
Databases & Denormalization - Faster queries for faster retrieval
Reusable UI components (React and beyond) - both presentational & functional
Caching - What to Cache, and When to Cache (Part 3)
Caching - Are you optimizing before identifying the problem? (Part 2)
When looking to make performance improvements, it is natural to look for that ”single” big problem. But, that’s hardly ever the case.
Keep your code DRY. As in, super DRY! Code duplication is a maintenance nightmare.
Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?
Should you implement that next requirement now, later or never?
[Paid Course] Snowpal Education: Writing scripts to understand REST APIs
Join Podbean Ads Marketplace and connect with engaged listeners.
Advertise Today
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
A Prairie Home Companion: News from Lake Wobegon