Explore >> Select a destination
|
You are here 
|
lostechies.com | ||
| | | | |
www.milanjovanovic.tech
|
|
| | | | | How should you handle errors in your code? This has been a topic of many discussions, and I want to share my opinion. One school of thought suggests using exceptions for flow control. This is not a good approach because it makes the code harder to reason about. The caller must know the implementation details and which exceptions to handle. Exceptions are for exceptional situations. Today, I want to show you how to implement error handling using the Result pattern. It's a functional approach to error handling, making your code more expressive. | |
| | | | |
lukasrotermund.de
|
|
| | | | | The Go standard library provides hundreds of features that make life easier for us Go developers. In this series, we'll look at the library's code together. | |
| | | | |
ethanmarcotte.com
|
|
| | | | | It's often suggested that design systems would improve the way organizations work. I've been wondering about that. | |
| | | | |
zig.guide
|
|
| | | Slices can be thought of many-item pointers ([*]T) with a length (usize). | ||
