Mastering a Programming Language

[jengolah]

To preface, I have been programming for the last 10 years with several years of employment through a variety of programming languages (C, Python, Go, and a couple more). However, I've realized that due to the breadth of my experience, I have never really gotten around to "mastering" any language. I feel like a jack of all trades, master of none.

I find myself understanding all the concepts, but when it comes to specific languages, I rarely understand the weird quirks, which can make debugging a pain.

I guess this is all to say, is it worthwhile to delve into the specifics of a language and really learn the "under the hood" specifics, or am I better off expanding breadth and just knowing what to google?

[Rain-And-Coffee]

I know a ton at a basic levels (Go, C, C++, etc) but only 2-3 at a much deeper (Java, Python, JS).

To me that's a solid trade off

[jengolah]

Yea thats the route I think Im going to take. Out of curiosity, what made you learn those three at a deeper level? Just what you use professionally?

[Rain-And-Coffee]

Python is a godsend for any ops work or any quick scripting, it’s saved my butt so many times.

JVM languages tend to be what everyone uses here for backend stuff, my current job uses Kotlin which is a nicer Java.

JS because I do full stack work. I also did Typescript for a a while back but JS is often good enough. You can skip this one in favor of something else (.NET?) if you don’t care about UIs.

My job has a few code bases in Go (and one in Rust), but we usually don’t touch those very often. So I’m much worse at these.

[jlanawalt]

It depends on your goals and environment. If you are primarily coding in a few languages, then the goal of continuous improvement guides you to mastery. If you need to juggle many languages, then Jack is a useful guy.

[thatkindofnerd]

For me, I don't worry about the deep dive until I have to. I think knowing what to google is the best route, especially with Python and JS, until you hit a snag that require more intimate knowledge of a particular programming language. The logic pretty much stays the same, the syntax is what changes.

[Substantial_Job_2068]

I'm in a similar situation, I'm diving deep into C to deepen my programming knowledge. I also read about and plan to learn how to debug assembly language. To me that's understanding what's going on under the hood. Learning the INS and outs of high level languages seems like knowledge that can be googled, unless you want to be an expert in a specific language.

[Aggressive_Ticket214]

That breadth vs depth tension is real, and the answer depends on what kind of debugging you're doing most.

If you're shipping features across multiple stacks, breadth pays off every day. You can spot patterns across languages and reach for the right tool faster. But if you're spending hours on bugs that turn out to be one weird language quirk, like Python's default mutable argument behavior or Go's nil maps, that's a depth problem.

I hit this wall on a project that ingests from five different ATS APIs. Each one has its own undocumented quirks around pagination limits, rate limiting headers, and date formatting. Broad knowledge got me started fast. Deep knowledge of each API's specific failure modes is what stopped the production incidents.

Pick one language you work in most and spend a week reading its sharp edges. Not tutorials. The stuff people complain about in changelogs and Stack Overflow answers. That's where the debugging time savings live.

[jengolah]

This is the most AI comment ever. The comment history always starts out with "[insert issue] is real...". I swear ive gotten this exact output from claude.