Louis :emacs: on Nostr: npub1l0hpz…ent5q What I mean specifically is that you look at your 100 lines of ...
npub1l0hpznk5jnr093e4au49hjygje6zamkhkknv8z0ka5tsjn4r366ssent5q (npub1l0h…nt5q) What I mean specifically is that you look at your 100 lines of mostly imperative Go code and think, how can I make that better and more expressive?
Just to realize that in Go there is rarely such an opportunity, compared to many other languages, that allow you to learn more advanced functional concepts and abstraction patterns over time.
It took the Go devs 14 years to release a generic min/max function and slice/maps utility functions like Contains. I probably wrote thousands of rudimentary, ugly for loops because those did not exist.
npub1jz4fkl2yy7ar6n7lxg8ahd6ydps2pwrxngsj0y8yueqv3n3rv77s7rd2ua (npub1jz4…d2ua)
Just to realize that in Go there is rarely such an opportunity, compared to many other languages, that allow you to learn more advanced functional concepts and abstraction patterns over time.
It took the Go devs 14 years to release a generic min/max function and slice/maps utility functions like Contains. I probably wrote thousands of rudimentary, ugly for loops because those did not exist.
npub1jz4fkl2yy7ar6n7lxg8ahd6ydps2pwrxngsj0y8yueqv3n3rv77s7rd2ua (npub1jz4…d2ua)