[deleted]
Ask HN: Which tools have made you a much better programmer?
161–170 of 519 posts
Re: Ask HN: Which tools have made you a much better programmer?
#162Re: Ask HN: Which tools have made you a much better programmer?
#163In recent years: 1) Ripgrep 2) Upgrading my Lenovo T430 laptop to a P53
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?
Re: Ask HN: Which tools have made you a much better programmer?
#164git blame inside of the IDE.
line numbers, jumping to lines. shockingly this isn't default in IDE and I frequently still have to learn how to enable it.
autocomplete and quick way to get a list of available methods for an object, based on the actual library or things the object inherits. Javascript IDEs seem to just show a random list of frequently available functions, instead of the actual ones indexed - likely because they are all the same type.
Re: Ask HN: Which tools have made you a much better programmer?
#165Emacs.
Re: Ask HN: Which tools have made you a much better programmer?
#166Re: Ask HN: Which tools have made you a much better programmer?
#167[deleted]
Re: Ask HN: Which tools have made you a much better programmer?
#168The Jetbrains suite. Lightens the cognitive load, makes it easier to refactor and keep code tidy. All of which allow me build better software. For almost everything else e.g. git, learning how to use the command line instead of a UI is the best way for me to learn how the tooling works.
Just downloaded the GoLand 30 day trail. First impressions are I now remember how slow and stuck in goo java based IDEs feel. What cool stuff should I look at as I am willing to be sold on this.
Jetbrains offerings are quite fast. What are you comparing them to?
Re: Ask HN: Which tools have made you a much better programmer?
#169Writing the overall design in plain English before writing the implementation. Not super detailed, but the main data structures and invariants and mechanisms that will make the implementation working. Then start the implementation refining such document as I discover new things.
This is the most useful post so far. I take it a step further and make a diagram in draw.io to understand exactly the data that is coming in and out. This is especially important for working with legacy code where you might get random crap like a name instead of an id and that could throw off your design.
Re: Ask HN: Which tools have made you a much better programmer?
#170Earlier quoted context omitted.
My life was also improved with some additional aliases in my git config: [alias] dfif = diff idff = diff grpe = grep
Nice! I create two-letter aliases, it truly helps: gc = git checkout gs = git status etc...
Nice, I have those same aliases.
Also not afraid to add multi-letter aliases if I find myself typing the same multi-word command over and over.
For example git diff master HEAD becomes gdmh