171–180 of 519 posts
Earlier quoted context omitted.
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?
The 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.
- Git - quite self-explanatory - Visual Studio Code - I like more than the paid version (that I have a subscription for) - SQL Server Management Studio execution plan modes - it is a gem that few people know about and even fewer can utilize it effectively to make 10 second queries run in 30 milliseconds. - Composer (PHP) as my first encounter with package management, years ago. - Notepad++ - the only mini-tool availa…
There is a paid version of VS Code?
- Git - quite self-explanatory - Visual Studio Code - I like more than the paid version (that I have a subscription for) - SQL Server Management Studio execution plan modes - it is a gem that few people know about and even fewer can utilize it effectively to make 10 second queries run in 30 milliseconds. - Composer (PHP) as my first encounter with package management, years ago. - Notepad++ - the only mini-tool availa…
There is a paid version of VS Code?
It has helped me so much in applying TDD rigorously in every app that I write by giving me very quick feedback on code I write.
The simple fact you can refactor something and within seconds know if everything still works is a massive time saver and that allows me to write better tests. It also makes flaky, slow and coupled tests visible as you get used to the speed of test execution that the “bad” ones jump out at you.
Well worth the license
The vi mode for Bash. Blew my mind when I discovered it and it probably saved me hundreds of hours already. I used to have multiple copies of this cheatsheet [0] at my desk for every new developer I would see editing a terminal command with the left and right arrows. [0] https://catonmat.net/ftp/bash-vi-editing-mode-cheat-sheet.pd...
1. Copernic Desktop Search pre version 3. The version I use is over ten years old and still looks and works better than any other desktop search product I've ever used. Instant results when searching your file and network system, presented in a format appropriate view. Please note that the version is important here, it went from being a stunning piece of freeware to a worthy corporate product years ago.
2. Trello. Every non-trivial task I undertake is managed through here, it's so simple and flexible.
That would easily be using an integrated REPL. The more integrated it is (with your IDE/editor) the better the experience and productivity boost. And the difference is quite large. When you are working with a language that has first class REPL support you start to - 'get' why Emacs exists - become faster at writing code in general - write much more experimental and open - become more motivated in testing smaller assu…
However, one thing I've found invaluable over the years is developing operational tools to support my deployed code, in a language with a built in REPL.
At different times, I have used Clojure and Jython for this (high level way to call my Java libraries, or to invoke APIs over the network), and most recently Ruby (has been easy to deploy and run scripts or ad hoc commands over irb for operational tasks, in the same environments where my service runs).
This allows me to build up code over time that I can use to
* Quickly make calls to my service to triage or debug production issues.
* Write scripts to quickly validate a new install.
* Script operational tasks at a high level that doesn't make sense to build into the service itself (can allow the service to be more stateless, for example).
* Bypass layers and make calls to the underlying database (can be more powerful than the command line tools dedicated to a specific database).
* Can be more powerful and composable than curl or Postman for making web calls.
* Have used it to analyze the state of messages in a Kafka topic (with a custom gem).
So I highly recommend building a tool set around a language with a good REPL for anyone responsible for a service with a REST API, or any other kind of API available over a network.
- GNU/Linux + i3wm; complete control over my programming environment. - bash + GNU coreutils; seriously, take the time to be able to write helpful bash scripts which can run basically anywhere. - git; use it even when you're not pushing to a remote. Add helpful aliases for everyday commands. Build a good mental model of commits and branches to help you through tough merges. ( my ~/.gitconfig: https://gist.github.com/…
My life was also improved with some additional aliases in my git config: [alias] dfif = diff idff = diff grpe = grep