Two bits of advice I'd add, from 30 years in the industry:
* A colleague once said to me, a few years back, "become an expert in one thing", even if it's a small thing.
* "My superpower is reading the manual"
* A colleague once said to me, a few years back, "become an expert in one thing", even if it's a small thing.
* "My superpower is reading the manual"
I've written a post around this topic because you can do this in a systematic way to learn pretty much anything https://nickjanetakis.com/blog/how-i-quickly-find-answers-to....
When I'm introduced to a codebase I'll be doing significant work on, I'll often spend hours at a time just reading the code. Start at main() and skim until you get a feel for the overall architecture, then go figure out whatever subsystems seem mysterious to you. Rinse and repeat. Makes a huge difference when making changes, because that requires reading code anyway, and you'll have a much better idea of what code to read/change.
My experience is that it basically comes down to developer discipline. A disciplined developer will update the docs regardless of whether the docs are part of repo or external and vice versa.
Maybe its just me but plain text does nothing for me so i convert it into visual elements.
Man I wish that worked for Java ;-)
That's worked out.
What I really want to do is be locked in a room with a niche project I can look after until I'm dead a this point. But that ain't gonna pay the mortgage off...
My best guess is the ascendence of Kubernetes has made reading Go rather instrumental; and as a by-product, writing Go seems much more approachable.
It is like the Python of statically compiled languages to me, but with way more safety rails and things you need as your code base grows.
There is just demand for it in general from what I see.
What it does is allow me to circumvent demotivating and productivity draining pain which is seen elsewhere which is pretty much summed up as: shitty build tools, runtime environments, libraries, containerisation, IDEs, concurrency approaches, test frameworks.
Really it's a tool that allows me to actually get stuff done.
It's pretty much what I've wanted for years: a memory safe, GC'ed C with a stdlib that wasn't conceived in the 70s.
* Identify your superpower
What special mojo do you bring to a problem that no one else on your team can? Recognizing and leveraging your superpower can make running w/ a team of true overachievers a lot more pleasant.
How small is small? Some small fields are quite big when you factor in all global experts.
But I think people should choose topic carefully it should be fundamental, maybe it's soon unfortunately gone if you choose a trendy and short-lived tech.