3
points
ThierryBuilds
Joined 3 karma
Thierry here. I write about the mechanics of building reliable systems at BuildSoftwareSystems.com. My interests range from C++/Rust memory and OS internals to fault tolerance and microservices architecture. I’m mostly just fascinated by the journey from source code to machine code.
- Thanks for the clarification. Happy new year
- C++ Has changed so much since C++11. It feels like it is picking features from every other language
- I am curious to know what was the contribution of switching to FlatBuffers in that improvement.
- Thanks for your response. Wouldn't using the `_` in the enums somehow make almost all integers index "cartable" to the enums?
- Balancing developer satisfaction with raw productivity is a critical trade-off. While the 'joy of coding' maintains long-term engagement, LLMs provide a necessary lift in throughput. I prefer a surgical approach: disabling LLMs for core logic to avoid 'auto-pilot' bias, while utilizing them for the high-friction work of documentation and unit testing.
- Nice Article. However I fail to understand how using the enum prevents the usage of the wrong index in a data structure. Can you explain further?
- 2 points
- Nice article. And the `Into` trick also accept &String
- I’ve been using Go Expr for a while because it’s zero-dependency and fast, but I kept hitting walls that weren't obvious in the docs—like the fact that map keys in the script are treated as literals, or the "strict vs forgiving" difference between structs and maps.
I put together this deep dive into 10 specific gotchas to help others avoid the same debugging loops I got stuck in.
- 1 point
- On a different note, the syntax for capacity hints of slices vs map can be confusing. m := make(map[string]string, 16) VS a := make([]string, 16)
They look similar but the second argument do not have the same meaning.
I got bitten by it in my early days of Go
Flat buffers is know to bloat client code. Was any trick used to mitigate that?