Ask HN: Which tools have made you a much better programmer?
181–190 of 519 posts
Re: Ask HN: Which tools have made you a much better programmer?
#182An unexpected result of being anal about whitespace for a few months was productivity with large code bases.
I no longer have Sonar itself in my workflow. But I defo feel that tool made me a better programmer.
This is not really a recomendation for Sonar but a recomendation to go find a relevant code style tool and work with it until it you are no longer learning code formatting and you are learning code clarity.
Re: Ask HN: Which tools have made you a much better programmer?
#183Earlier quoted context omitted.
Nice! I create two-letter aliases, it truly helps: gc = git checkout gs = git status etc...
Here's mine: alias g="git" __git_complete g _git # enable git autocompletion (braches, etc.) alias gc="git commit -am" alias gp="git push" __git_complete gp _git_checkout # checkout is more useful than _git_push because it autocompletes the branch alias ga="git add -A" alias gd="git diff" alias gb="git branch" alias gx="git checkout" __git_complete gx _git_checkout alias gs="git status" alias gl="git log"
alias gcane="git commit --amend --no-edit"Re: Ask HN: Which tools have made you a much better programmer?
#184For me, the transition from Bash to Zsh has been a huge efficiency boost. Mainly because of some great plugins for Zsh, such as z, zsh-peco-history (better history search), zsh-autosuggestions, and zsh-syntax-highlighting. My blog post about setting up a Linux workstation describes this in detail: https://tkainrad.dev/posts/setting-up-linux-workstation/#swi... . The best thing is, there is no initial productivity hit…
It has its own "histdb" command but the best part is that it integrates well with zsh-autosuggestions, so with the right SQL query you can make it suggest something "the latest command in the current session that matches, or if not found, the most frequent in that directory".
I know it is controversial because it is not using a text file and UNIX loves text files, but it really nice, and you still have your .zsh-history if you want to.
Re: Ask HN: Which tools have made you a much better programmer?
#185Earlier quoted context omitted.
My only beef with ripgrep is that "rg" is only a small typo away from "rm". One time I almost deleted my working directory but luckly I had passed the -i flag for case insensitive search :)
Have you considered creating an alias - such as "rip" or "grrr" - for using ripgrep to help avoid that concern of rg vs rm?
But now that you mention it, creating an alias gr=rg sounds like a no-brainer. Thanks.
Re: Ask HN: Which tools have made you a much better programmer?
#186Earlier quoted context omitted.
There is a paid version of VS Code?
Maybe the person meant to say Visual Studio Code is preferable to Visual Studio.
As a Vim user of 2 decades, I have to confess something: VS Code is a far better programmer's editor than Vim. It's pretty responsive, has seamless (and better) integration with language servers [1] than Vim, has better autocomplete than Vim (due to said language server) and the Vim keybindings are not terrible.
For the first time, refactoring (renaming variables) is easy because the editor now understands the language-specific structure of the code as opposed to the code being treated as a long string. It's possible to attach a language server to Vim but it's fiddly and doesn't work that well.
Re: Ask HN: Which tools have made you a much better programmer?
#187I'll add two really simple, but also very effective tools. Search: in the form of things like "the silver searcher" ( https://github.com/ggreer/the_silver_searcher ) or "fd" ( https://github.com/sharkdp/fd ). And, Replace: with tools like sed ( https://www.gnu.org/software/sed/ ). These are really simple tools but they are also very powerful. I have surprisingly often needed to change from version X.Y.Z to version A.…
Re: Ask HN: Which tools have made you a much better programmer?
#188Re: Ask HN: Which tools have made you a much better programmer?
#189As a development tool: You can default to writing the majority of your code dumb, terse[1], and straightforward, even if you know there's a clever algorithm you might be able to use, because that way is easier to debug. Computers are fast and N is usually smaller than you think, and when you apply the profiler you'll find out that that the biggest performance problem isn't the thing you were going to optimize anyway.
As a product tool: People are more likely to buy responsive programs. The state of modern websites is so bad that non-programmers will actually comment. Every tester for Space Trains[2] commented on how smooth it is. That's a game, but I've seen the same comments on productivity software I've written.
[1] As in omitting layers, not as in omitting descriptive variable names.
Re: Ask HN: Which tools have made you a much better programmer?
#190Using multiple programming languages. Using Golang has helped me create better data structures, and using C helped me understand linking, using python helped me understand closures, and using Ruby helped me understand that I hate programming.
can you elaborate on ruby? i'm curious to understand your experience with it and what brought you to the conclusion that you "hate programming".
I don't like programming. I like it when the computer does what I tell it to do. I find that drastically easier to accomplish in Ruby (especially Rails).