1. It helps me stay focus on the task at hand. One recording for each task 2. It lets me practice how to articulate stuffs. Its like blogging but ephemeral (because i wont upload this) 3. It helps me get motivated. Cant let my "thousands" of viewers down 4. It lets me review my blunders so i know how to watch out for them in the future 5. Its fun. I can let off some steam because i can curse all i want, my audience is 18+ and fine with some "sentence enhancers". I am Filipino but i record in English so i get that extra bonus practice.
Ask HN: What are your favorite developer-efficiency tips?
81–90 of 532 posts
Re: Ask HN: What are your favorite developer-efficiency tips?
#82I usually comment with the same thing on these tip threads. And that is learn to rebind your keyboard. Make each key programmable modifier. Open apps, run scripts/macros instantly. My Karabiner config: https://github.com/nikitavoloboev/dotfiles/blob/master/karab... I go as far as binding keys to instantly type `console.log()` or `fmt.Println()` or the other language equivalent with my dot modifier key. Plus typing th…
Maintaining a Wiki or any sort of extensive note taking operation requires a lot of dedication and I guess practice? Do you have any tips for someone who wants to start out? Is there a smaller step that one could take initially?
Re: Ask HN: What are your favorite developer-efficiency tips?
#83Re: Ask HN: What are your favorite developer-efficiency tips?
#84Re: Ask HN: What are your favorite developer-efficiency tips?
#85Learn your environment and learn it well (over time). Every single thing that seems like weird arcane magic invented by brilliant wizards is just code or words, and often not a lot of it. Go find that code and read it. Docs are good, but they are almost never complete enough, because truly exhaustive docs would simply be the code [1]. Similarly, with something like CSS or OAuth that have specs, blog/tutorial content…
Re: Ask HN: What are your favorite developer-efficiency tips?
#86I believe longer contiguous periods of time developing are very helpful.
Re: Ask HN: What are your favorite developer-efficiency tips?
#87KEEP 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…
Re: Ask HN: What are your favorite developer-efficiency tips?
#88If you have to look something up or solve something and it takes more than 2 minutes then write the solution down in your notes. Lots of times you'll need that again and you won't have to search for it again.
I am a bit conflicted about the note-taking part. If you keep writing notes, at some point you will have to search through all of them to find what you need. So you not only spend the time to write the note, you still have search for the solution and there's the risk of the solution becoming outdated (eg. maybe the problem now has a better solution due to new versions of software)
In general I find that logN is faster than solving the problem from first principles again (N!).
Re: Ask HN: What are your favorite developer-efficiency tips?
#89Note this can be painful to leave an old favorite behind.
Re: Ask HN: What are your favorite developer-efficiency tips?
#90A couple others have mentioned shell tricks. One of my favorites is using Alt-. (in Bash and Zsh) to insert the last argument of the previous command. Press it multiple times and it will cycle through the last argument of all previous commands. It's great for when you want to, say, `ls thing` and then `vim thing`. Yesterday I went looking for a similar key that would insert a copy of the last argument on the current…
I assume you're talking about only on linux? On a mac `alt .` and `alt /` are mapped to characters ≥ and ÷