Which tools or packages should be known by a developer irrespective of programming language to be a better developer?

[jmaida]

Some of the best advice everyone or anyone can use, especially writing code.

"A little time, a little trouble, your better day" Badfinger

[englebart]

Study other programming libraries and languages for their good ideas. Ex. C++ STL (Standard Template Library) design principles and performance. SmallTalk - amazing pure OO design. I really like the Boolean design with SmallTalk. SQL - amazing power built on top of a few, consistent building blocks Functional Programming concepts. Leads to very testable/provable code State based design Etc

[OriginalGriff]

The Mandalorian[^] But between series 2 and 3, you need to watch The Book of Boba Fett[^] as the last three episodes continue the Mandalorian story line and there'd be a "big jump" or "plot hole the size of Tatooine" if you didn't! This is the way.

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

[abmv]

I think only hard work and learning from your mistakes and trying to be better will help... no tools or packages will help.. all the other thinks you can learn but end of the day its your code that matters

Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long

[Mycroft Holmes]

I watched the first one and was not overly impressed, but now I can binge watch both, by which time s3 should be complete. This is going to piss off the better half, I going to want the BIG TV.

Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP

[BillWoodruff]

wisdom, sagacity, discernment, patience, imagination, non-defensiveness, curiosity.

«The mind is not a vessel to be filled but a fire to be kindled» Plutarch

[Chris Baker 2021]

Understanding the domain you are writing code for. I know that's quite specific per project, but nonetheless important I feel.

[Luis Guerrro]

Not a package nor tool, but you need to know how to debug, either with the help of an IDE/debugger tool (like VS) or without it (the old way, by placing messages or flags sent to screen, database, or console). Also you need to know how to search for help, may sound a little odd, but a few new guys/gals I work with seem to be lost on how to look for help on internet... i remember when I started, you have to look at books and magazines, now it's easier with search engines, sites like codeProject, etc, but you still need to know how to ask questions/look for answers, how and what to search, and that comes with experience (and some common sense). HTH

[Matt Bond]

Analytical puzzles. Debugging and trouble-shooting code is a significant portion of one's time writing & maintaining code - no one writes perfect code the first time, every time. If you can't quickly analyze the issue and fix it, then you spend a lot of time on wasted efforts and dead-ends. This also applies to unit testing. Determining the minimum number of valid tests to test meaningfully different scenarios is as much art as science. Most developers know to test the happy path and the extremes (like testing for one-off errors when working with arrays). But there are many cases that might be less obvious for any specific scenario.

Bond Keep all things as simple as possible, but no simpler. -said someone, somewhere

[Matt Bond]

Defend your code like pirates defend their treasure. But also know when to bury it and supply only a hastily scrawled map (documentation) to it. :)

Bond Keep all things as simple as possible, but no simpler. -said someone, somewhere