Some best and bad practices by Anthony Alaribe at Golang Nigeria. Highlights: - Closures vs methods for dependency injection - Errors are values - Using function adapters in Go

1. Go Best and Bad
Practices
LAGOS, NG. 18 AUGUST, 2018
Anthony Alaribe
Opera (Opay team)
@tonyalaribe

2. Today’s (glorious) blather.
Handle errors first 01
Use Function adapters
Closures vs Methods
Errors are values
A Concurrency Gotcha
02
03
04
05

3. How to write code that is:
02. A SIMPLE TYPE SYSTEM
- Simple
- Maintainable
- Readable (Yet powerful)

4. Disclaimer
02. A SIMPLE TYPE SYSTEM
- This talk is based of a lot of other
resources in the community from
people like
- Francis Campoy,
- Robe Pike,
- Steve Francia, etc

5. Avoid nesting by
handling errors first

6. 01. AVOID NESTING BY HANDLING ERRORS FIRST

7. 01. AVOID NESTING BY HANDLING ERRORS FIRST

8. Use function
adapters

9. 02. USE FUNCTION ADAPTERS (HIGH ORDER FUNCTIONS)

10. 02. USE FUNCTION ADAPTERS (HIGH ORDER FUNCTIONS)

11. Methods vs
Closures in Web
Architectures

12. 03. Methods vs Closures

13. 03. Methods vs Closures

14. 03. Methods vs Closures

15. 03. Methods vs Closures

16. Errors are
values

17. 03. ERRORS ARE VALUES

18. TENETS OF GO DESIGN
Errors.
An error can be
anything which
satisfies the
golang interface
03. ERRORS ARE VALUES

19. 03. ERRORS ARE VALUES

20. 03. ERRORS ARE VALUES

21. NOTE
03. METHODS VS CLOSURES
r.Mount("/api/todo",
todo.Routes(configuration))
Things to Note:
The smaller code surface area.
Using closures, the code feels
more compact
(and in my opinion, elegant).
functionA(argA)(argB)(argC)
Closures can be a little less
unnatural, since you can have
scenarios such as

22. A few Bad
Practices

23. Excessive use of inline
functions in concurrent
programming

24. 03. INLINE CONCURRENCY

25. 03. INLINE CONCURRENCY

26. 03. INLINE CONCURRENCY

27. Debugging is twice as hard as writing the
code in the first place. Therefore, if you
write the code as cleverly as possible,
you are, by definition, not smart enough
to debug it.
BRIAN KERNIGHAN

28. Thank you