Saltar al contenido ForoHackers

Developer tools: start here

Herramientas de desarrollo
#3359 · · Citar · Denunciar

Developer tools are the programs programmers use to make programs: editors, compilers, debuggers, profilers, formatters, linters, package managers. Knowing them well multiplies your speed, and building small tools of your own is one of the best ways to learn how software works.

Key concepts

  • The shell as a workbench: pipes, redirection and scripts glue small tools into larger jobs.
  • Editors and IDEs: text editing, search, navigation and refactoring; learn the keys of one deeply.
  • Language servers: one protocol that gives any editor completion, go-to-definition and diagnostics.
  • Static analysis: formatters, linters and type checkers find problems before the program runs.
  • Dynamic analysis: debuggers, profilers and sanitizers show what happens when it runs.

Vocabulary

  • Toolchain: the compiler, linker and related tools used to build for a target.
  • REPL: read-eval-print loop, an interactive prompt for a language.
  • Profiler: a tool that measures where a program spends time or memory.
  • Package manager: a tool that installs and updates libraries and their dependencies.

What to study, in order

  1. Get fluent in a shell: find, grep, pipes, job control and a small script of your own.
  2. Learn one editor deeply, including its search, multiple cursors or macros, and debugger integration.
  3. Use a debugger and a profiler on a real program, and read what they report.
  4. Configure a formatter, linter and type checker, and run them automatically before each commit.
  5. Write a small command-line tool that solves a nuisance of your own.

Related tags

#shell #debugging #build-systems #toolchains

No has iniciado sesión, así que esto se publica como anónimo: no se guarda con ello ninguna cuenta, nombre ni dirección, y no puede llevar enlaces ni imágenes. Inicia sesión o únete para publicar con tu nombre. Los registros de nuestro servidor web guardan la dirección y la hora de cada petición hasta 14 días; para que la tuya no quede en ellos, usa Tor. Para escribir al equipo de forma confidencial, usa el buzón. Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder