When I used Swift, I frequently was surprised to find some simple part of a program actually required me to sit and plan for several hours.
The exhausting amount of mental energy is the only part that reminds me of coding in Assembly.
I frequently was surprised to find some simple part of a program actually required me to sit and plan for several hours.
It's perfectly normal in programming to encounter domain problems that take longer than one predicted, or to plan ahead with pseudo code, proofs of concept, class diagrams, etc.What is abnormal is, over and over again, to find oneself utterly stumped on how best to implement something very basic. At least, it's abnormal when using a high-level language.
Is it what the enum abstraction can model easily that is the issue?
If so, I believe the Rust community has similar issues regarding error handling. There are multiple libraries like thiserror and anyhow.
https://old.reddit.com/r/rust/comments/1mexsqr/the_way_rust_...
https://old.reddit.com/r/rust/comments/1q3wb3l/stop_forwardi...