Most active commenters

    ←back to thread

    30 points Userrr | 11 comments | | HN request time: 0.659s | source | bottom

    We often talk about mastering popular languages, frameworks, and AI tools. But what about the less-hyped skills that quietly make you 10x more effective?

    For example:

    Knowing how to write a custom shell script that replaces a SaaS tool

    Building internal tools with no-code + cron + GitHub Actions

    Understanding how to optimize a slow SQL query line-by-line

    Crafting a bash one-liner that saves you hours every week

    Using the command line like a superpower

    I'm curious: What are the most underrated but highly valuable tech skills you've learned that more people should know about?

    Would love to hear stories, examples, or even niche tools you swear by. Bonus points if it’s something you only discovered by accident or necessity, not through a tutorial.

    1. andelink ◴[] No.43664817[source]
    1. Giving a damn. The majority of people don’t care at all about the work being performed. You can easily distinguish yourself by simply caring about whatever it is you’re working on.

    2. A natural consequence of the above: fully reading the documentation, be it man pages or the official technical reference for a given technology. It’s incredible how many people don’t read documentation. You can become one of the foremost experts in your company simply by reading the documentation from front to back. You will seem like a genius.

    replies(6): >>43664867 #>>43666625 #>>43680363 #>>43683073 #>>43683155 #>>43690872 #
    2. mooreds ◴[] No.43664867[source]
    > Giving a damn.

    This is an underrated skill. I agree, the bar is so low that even a little bit of care/user empathy will make you stand out.

    replies(1): >>43670515 #
    3. paulcole ◴[] No.43666625[source]
    > You can easily distinguish yourself by simply caring about whatever it is you’re working on.

    Care about the business, not specifically the thing you’re doing.

    4. moondev ◴[] No.43670515[source]
    If giving a damn makes you stand out, it seems like that would indicate none of your peers or colleagues give a damn. Working at a place where you are the only person that gives a damn feels like torture.

    I also wonder how much tangible value can be created by a group of incompetent people that care, compared to a group of skilled people that don't.

    replies(2): >>43671031 #>>43678348 #
    5. Dementor430 ◴[] No.43671031{3}[source]
    Well, the incompetent will find a way to make it work. Since management usually only cares about that, it will be fine. The competent who dont give a damn will basically result to vibe coding and receive similar results. Just with lower cost.
    6. bruce511 ◴[] No.43678348{3}[source]
    It's interesting how personal experience colors this view.

    Personally I've had the odd colleague who didn't care, but they typically moved on, or got moved on, after a while.

    But lots of people here have obviously experienced it, perhaps at multiple places, and so project that to "all companies".

    I guess it does matter where you work, and perhaps numbering staff in thousands, or tens of thousands, means you end up with a lot of dross?

    7. farseer ◴[] No.43680363[source]
    If I may add to your second point, generating good documentation is also important. Of-course if you give a damn, this may flow naturally.
    8. idontwantthis ◴[] No.43683073[source]
    There was a great article posted here that basically said the difference between knowing nothing and being an “expert” is usually reading a single book on the subject.
    replies(1): >>43703527 #
    9. markus_zhang ◴[] No.43683155[source]
    Just to add: only give a damn about things that you really give a damn about.

    Some people give a damn about everything, which is probably a sickness.

    10. Doxin ◴[] No.43690872[source]
    re: 2: read all the docs, but don't memorize them. When faced with a question it's often enough to remember there are docs about the topic at all. If you don't know it exists you won't know to look it up.
    11. gnz11 ◴[] No.43703527[source]
    Sounds like a prime example of Dunning-Kruger?