Ask HN: What are your favorite developer-efficiency tips?

Post by chadlavi » Fri, May 08, 2020, 10:57 PM UTC

ra7 wrote: post #87

chadlavi wrote: post #50

KEEP NOTES. Write everything down. Write down what you were thinking about, how you felt about decisions, things you tried for bug fixes. you never know when this stuff will be useful to you again. I keep really basic markdown notes in a git repo, roughly one file per day with an ISO date name, but some things I give a separate file name (still with the iso date, but with some descriptive words) for things that might…

I want to take notes everyday, but I keep getting bogged down by how to organize those notes so I can "look back" efficiently. Essentially, I want to avoid taking so much notes that I'm reluctant to search for something because I haven't organized it well. Do you think the ISO date name method is working well for you?

Post by xupybd » Fri, May 08, 2020, 11:01 PM UTC

5cott0 wrote: post #39

growlist wrote: post #37

Learn to touch-type properly. I'm not a shit hot typist or anything, but it does make hours on a keyboard more pleasant. And (hate me) I do judge other devs on it. If someone can't be bothered to invest a few tens of hours on such a key productivity enhancement then what does that say?

Same. Learn to type ~100 words/minute, I was surprised by how much more productive it has made me. Using a touch type trainer for a minute or two can also be a little mental break from writing software for hours.

Post by aeyes » Fri, May 08, 2020, 11:07 PM UTC

Post by andrewtsaplin » Fri, May 08, 2020, 11:09 PM UTC

Uhhrrr wrote: post #92

Never waste time logging in again: scp ~/.ssh/id_rsa.pub me@[IP address]:/home/me/.ssh/authorized_keys Make aliases for your most common commands. Someone in a similar thread posted a script for parsing your history to find them out. For me they were all git subcommands. Write a script the second time you have to do something. On a macro level: Don't work on doomed projects. Don't update tools in the middle of a proj…

Post by Uhhrrr » Fri, May 08, 2020, 11:11 PM UTC

andrewtsaplin wrote: post #97

Uhhrrr wrote: post #92

Never waste time logging in again: scp ~/.ssh/id_rsa.pub me@[IP address]:/home/me/.ssh/authorized_keys Make aliases for your most common commands. Someone in a similar thread posted a script for parsing your history to find them out. For me they were all git subcommands. Write a script the second time you have to do something. On a macro level: Don't work on doomed projects. Don't update tools in the middle of a proj…

But instead of this: scp ~/.ssh/id_rsa.pub me@[IP address]:/home/me/.ssh/authorized_keys you can use this: ssh-copy-id me@[IP address]