A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
If you want to be an expert in the language yes, you should be able to explain any piece of code, and how does behave at runtime or compiled to.
But most devs do not want to be experts so .. theres that.
IMO, most people likely don't want to be experts because there is a point of diminishing returns after you've acquired a certain proficiency with a language.
That is one reason, there many and all good ones, I did not implied that they should strive to become an expert.
We should have experts to push the boundries further, but just a few is enough
An excellent well-wrapped point. Ground your skillset proficiencies based on the truth that software adapts and will always adapt.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you want to be an expert in the language yes, you should be able to explain any piece of code, and how does behave at runtime or compiled to.
But most devs do not want to be experts so .. theres that.
IMO, most people likely don't want to be experts because there is a point of diminishing returns after you've acquired a certain proficiency with a language.
That is one reason, there many and all good ones, I did not implied that they should strive to become an expert.
We should have experts to push the boundries further, but just a few is enough
An excellent well-wrapped point. Ground your skillset proficiencies based on the truth that software adapts and will always adapt.