3 ms·
> I used to be excited by programming language features instead of what problem I was actually trying to solve with programming. This happened to me too, witho
by tdeck 5y ago
> I used to be excited by programming language features instead of what problem I was actually trying to solve with programming.
This happened to me too, without using Go. I think I just got older.
- throwaway894345 5y agoThe nice bit about Go is that this maturity is baked into the philosophy and thus the language, the tooling, and the ecosystem where it benefits even younger developers. For example, your own hard-earned wisdom is great but it doesn't automatically make your language's package manager (or any other software you depend on, including libraries) better. But when that kind of wisdom is idiomatic, everything is better even when it's built by more junior developers.
- tdeck 5y agoOh, I'm not necessarily suggesting that my lack of curiosity about new language designs is a good thing. In fact I think it's kind of a mixed bag. I'm only clarifying because I don't want to seem to be implying something negative about younger developers.
- throwaway894345 5y agoI didn't think you were implying anything about younger developers, I was noting the rather significant difference between "I've matured as a programmer" and "maturity was baked into the language I use and its idioms, tools, ecosystem, etc".
- tdeck 5y agoYeah, my point was that "matured" and "wisdom" are value-laden words and that's not necessarily the connotation I wanted to convey. Ideally I would get excited about both the problem and the tools. I completely understand the point you're trying to make about the ecosystem though.
- adamc 5y agoI came here to say that. I agree with your analysis.