[1]Home [2]Recent [3]Comments [4]Search

[1]Home [2]Recent [3]Comments [4]Search
[5]Login
1. 13
[6]How does your current dev workflow looks like [7]☶ [8]ask
[9]programming
[10]mraza007 avatar authored by [11]mraza007 12 hours ago | [12]27
comments
[13]27

Share your favorite dev tools that helps you remain productive such as
text editors,terminal,configs and etc
1.
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
Post (button) Preview
2. [ ]
5
[14]evanrelf avatar [15]evanrelf 7 hours ago | [16]link
My development environment is kinda like the UNIX philosophy
version of an IDE. I use:
+ Fish as my shell
+ Kakoune as my text editor
+ tmux for windowing and persistent session stuff
+ fzf for fuzzily changing directories and picking files
+ ripgrep and fd for searching
+ kitty as my terminal emulator
I’m probably forgetting other things, but those are the important
ones. My personal laptop runs macOS, but all other machines run
NixOS.
I work almost entirely with Haskell and Nix, so language specific
tools include stuff like Cabal, ghcid, ormolu, and HLint. I also
use home-manager for declarative package management, as opposed to
the more imperative nix-env style.
3. [ ]
5
[17]alicebob avatar [18]alicebob 7 hours ago | [19]link
vanilla vim in a basic terminal. Works everywhere, and I don’t have
to spend brain-cycles thinking about it.
1. [ ]

[20]duraki avatar [21]duraki 5 hours ago | [22]link
How do you deal with multi language barrier? ie. Space vs Tabs
in different project? Do you manually expandtab/tabstop?
1. [ ]

[23]akavel avatar [24]akavel 4 hours ago | [25]link
Personally, until I need to do it often enough to put in
my .vimrc for a particular filetype, I kinda already
remember the :setl sw=2 ts=2 et (replace 2 with whatever
needed) “magic incantation” for when needed. Umm… a
moment of self-reflection: is vim really a
stockholm-syndrome lover I thought it to be in my younger
days?… Yet in other editors, I’d have to do it by mouse
or keyboard shortcuts anyway…
4. [ ]

[26]stephenr avatar [27]stephenr 8 hours ago | [28]link
+ IDEA Ultimate (aka IntelliJ IDEA). I last wrote Java (and it
wasn’t much then) checks notes 5 years ago, and I still don’t
get why each of the language-specific JetBrains editors
exists, but apparently this is the only one that will support
plugins for any other random language (e.g. PHPStorm can’t
install the python language plugin, and PyCharm can’t install
the PHP language plugin).
+ Vagrant. From a shared single-VM dev environment, to an 8-10
VM simulation of a ‘production’ site. Yes it has a few rough
edges, but realistically everything does, and I’m mostly
familiar with these rough edges now.
+ A pretty vanilla zsh on macOS, the only really ‘custom’ thing
is a little script to setup & store dotfiles & similar in
iCloud drive.
+ TablePlus (for SQL)
+ Kaleidoscope because command line diffs are insane for
anything beyond about 2 files.
1. [ ]

[29]pfcuttle avatar [30]pfcuttle 1 hour ago | [31]link
About the different JetBrains products, my guess is that you
only pay for the features you really use. It’s still weird
that you have to install different applications if you want to
mix and match e.g. Python and PHP, but not Java.
I don’t think I ever got the hang of a GUI for doing SQL. I’ve
used DB Visualizer a bit, but too many times there are
situations where the command line is just a few keystrokes
away.
1. [ ]

[32]stephenr avatar [33]stephenr 50 minutes ago |
[34]link
I get the pricing difference - but why not just have the
different licences enable different plugins then - and
they even acknowledge this weird behaviour with both a
“all products” licence and a dedicated desktop tool, just
to install/update/launch all the various tools.
Re: SQL - the GUI part is 99% about viewing results more
easily - the vast majority of the time it’s just showing
me the result of a query I wrote (or occasionally copied
from an error log).
5. [ ]

[35]zge avatar [36]zge 4 hours ago | [37]link
I’ll try to give a sketch of an Emacs-centered workflow. My main
tools are (surprisingly) GNU Emacs and xterm+bash. I don’t need
much more than that.
When working on something, I usually have one of two setups:
+ For compiled languages, I split Emacs intro three windows (for
non-Emacs users, what the window manager calls a “window” is a
“frame” in Emacs-speak, while a frame in the Emacs window is a
“window”). Usually a file buffer on one side of the screen,
and a vertically split window with a compile buffer on the top
and a terminal*/dired below. These can be rotated easily
(using window-swap-states). But I would usually order than so
that rotating through the buffers makes sense. Binding
recompile to a handy key is very useful, in my case I use the
F2 key.
+ For interpreted languages, assuming there is proper Emacs
support, I would have mostly the same setup, except that the
compile buffer would be replaced by a REPL, and I would tend
to not have a terminal open.
Regarding Emacs extensions, projectile is very useful, but I’m not
an advanced user. My main commands are projectile-find-file and
projectile-kill-buffer. Sometimes I forget to use the latter, and
then I end up with 700 opened buffers, like a few weeks ago. Other
noteworthy packages are avy, for jumping to symbols, but also
copying and moving them around, ivy/swiper, for faster completion
and perhaps dumb-jump for looking up definitions without having to
set anything up. Any other tips would be language specific.
[38]This is my configuration, in case anyone cares, but I’m in the
process of re-writing and shrinking it, so it’s not as tidy as it
used to be.
* In my case Eshell.
1. [ ]

[39]twee avatar [40]twee 2 hours ago | [41]link
It’s interesting how different our setups are considering we
both use Emacs; it fascinates me every time I come across one
how varied the users of Emacs are.
Thank you for your configuration, by the way. I can’t remember
how I first came across it, but I’ve found a few nice settings
in there, and like your list of inspirational configurations
which I’ve also found a few nice things in. When you switched
to Rmail I got quite excited, I barely know anyone else who
uses it!
6. [ ]

[42]Ameo avatar [43]Ameo 3 hours ago | [44]link
I’m very surprised that nobody has said they use VS Code yet. I
figured it had the lion’s share of the market, but maybe that’s
just webdevs.
I use VS Code exclusively as my text editor, except for Vim which I
occasionally use for editing config files and writing commit
messages. I write Rust for my dayjob (fullstack) and most side
projects (also fullstack), and I use the trunk rust-analyzer which
works pretty well these days except for situations with lots of
complex macros and codegen. I also write a good deal of
JavaScript/TypeScript which VS Code supports 100% out of the box.
I make very extensive use of full-codebase search with VS Code
(ctrl + shift + f) as well as normal find. I also make extreme use
of go-to definition; I feel that my workflow is neutered if I’m
working anywhere without both of those features available,
regardless of language. I find that I only use the file tree on the
left secondarily; I primarily navigate between files by following
go-to definition or clicking on results in all-code search.
I use code formatters for every language I write in; I can barely
work without one now. I type out a whole piece of logic without
pressing newline or space unless necessary and then have it
auto-format when I save. I use linter plugins for VS Code wherever
available. The thought of not having at least syntax checking
in-editor feels incredibly constraining.
A few other editor plugins:
+ Auto add trailing newline
+ Auto trim trailing whitespace
+ Side-by-side markdown preview
+ GitLens (show file history, show line history, show blame for
currently hovered line in bottom bar, etc.)
+ Language-specific extensions wherever available
+ VS Code live share which I’ve used for pair programming a few
times with mixed results
I have my frontend, backend, and any other pieces running in their
own tabs within my terminal (iTerm on Mac, Konsole on Linux
desktop). I use zsh/OhMyZSH with some nice plugins:
+ autojump (fuzzy-jump to directory by partial/close name)
+ show shadow completing all commands while typing (incredibly
helpful)
+ show git branch and dirty status for current directory if in a
git repo
I have a pretty basic set of dotfiles with mostly just config for
stuff like NVM, PATH, GOPATH, etc. I have some useful aliases which
I use (gd for git diff, cb for cargo build, etc.)
I have three monitors and generally have terminal and/or web
browser on the left one, text editor on the middle one, and web
browser on the right (usually for displaying the webapp I’m working
on). I keep all my windows maximized at all times and primarily use
the taskbar to switch between different windows on the same screen.
Taskbar is set to only show tabs for windows on the current screen.
I rarely use a debugger with the exception of the browser devtools
debugger when I use heavily. I rarely use repls with the exception
of, again, browser devtools which I use extremely heavily. When I
do use a debugger, I use VS Code’s integrated debugging for Rust
and C# (those are the only two languages I’ve used a proper
debugger before so far).
Rust utils have taken over my system, replacing many traditional
Linux ones:
+ ripgrep (grep replacement)
+ fd (find replacement)
+ dutree (visual size distribution of subdirs/files)
+ twiggy (Wasm size profiler)
1. [ ]

[45]danielrheath avatar [46]danielrheath 3 hours ago |
[47]link
I’ve started using vscode for my typescript and kept using
sublime for everything else.
Extremely similar overall, most problems have been just
learning new shortcuts etc.
However:
o Sublime is 1 frame faster at rendering text after I press
a key. Bothers me slightly in vscode, but most don’t
appear to notice.
o Several times a week, code gets into a weird state where
code search gets stuck and takes 3-5 seconds to respond
to input. Appears to be pegging a CPU. I suspect there’s
a keyboard shortcut I’m accidentally triggering which
tells it to search everything, even .git and node_modules
but haven’t figured out what it is.
7. [ ]

[48]artemis avatar [49]artemis 3 hours ago | [50]link
Recently I have been migrating to programming with my voice using
[51]https://talonvoice.com
This is having a cascading effect on the rest of my technology
stack as I rearrange things to optimize for what can be controlled
most easily with my voice.
For example, I have always been a vim user, but now I am finding
that I prefer VSCode with the vim plugin. file navigation and a few
other things that I do frequently are easier. Being able to hover
over identifiers for type information saves me from a lot of trips
to documentation or the terminal. it’s also easier for me to
develop missing functionality that I would like to exist in
typescript than vimscript.
I’m probably going to be switching back to fish, so that I can take
advantage of its auto complete.
1. [ ]

[52]indirection avatar [53]indirection 55 minutes ago |
[54]link
Once you’ve been doing it for a month, could you do a small
video or write up? I think this is something we’ve seen
attempted many times over the years but nothing seems
substantial.
8. [ ]

[55]twee avatar [56]twee 2 hours ago | [57]link
I use Emacs, but in a way more reminiscent of Acme. Normally I have
two windows next to each other: the current file and a shell buffer
(not eshell or term, a comint shell buffer running rc), and I shell
out to external commands a lot.
Notable parts of the configuration are the complete lack of syntax
highlighting, the lack of any completion frameworks or fuzzy
filterers (besides hippie), the lack of any advanced emacs features
being used (I don’t use slime, geiser, or whatever for any
language). I have a large amount of aliases and environment
variables set to make sure that my home directory is not dirty (and
have alias ls=ls -l) so that I don’t get lazy. I use 8-wide tabs
instead of spaces (except for lisp) and ag instead of grep. Also, I
use a light theme.
Most of the tools are use are written in C because I found it too
time consuming to get a rust compiler compiled, and I’m at a stage
in life where I’ve got the time to make hipster idealistic
decisions like that.
Really there’s nothing interesting going on, which makes all my
friends who care about this stuff think my setup’s odd because it’s
so plain in comparison to whatever they have set up. I’ve been
writing up a sort of live document explanation thing of what I use
for my own reference over time [58]here if anyone’s more
interested.
9. [ ]

[59]yumaikas avatar [60]yumaikas 10 hours ago | [61]link
For me, my Dev workflow centers around Vim modes
At work, that’s gvim+VimWikis for note taking, VsVim for writing
C#, LinqPad+Vi mode for prototyping code and exploring data.
Outside of that, I have notepad++, a menagerie of CLI tools for
various conveniences to make the Windows command line less painful.
They include directory bookmarks, my own version of ls for windows,
a cli punch clock, and a small RPN evaluator for the odd job. I
also have a tiny webapp for formatting commit messages and keeping
an eye on builds. These tools form a little nest of situated
software that makes my day a lot less painful.
For personal stuff, it’s mostly Vim+bash+tmux+Nim (used to be Go),
and JS where appropriate. When I get a better laptop for it, I’ll
probably get back into Godot.
10. [ ]

[62]jclulow avatar [63]jclulow 10 hours ago | [64]link
I’ve been writing a lot of Rust lately, and I spent some time
configuring [65]rust-analyzer to work through [66]vim-lsp, etc. If
I recall correctly I started with the instructions for [67]rls.
Anyway, it’s been good to be able to use the type information in
the language without needing to use a full IDE – I recommend it! As
an aside, to get proper floating boxes to render I think you need
at least VIM 8.2, which was still apparently unavailable last week
when I checked last.
1. [ ]

[68]arp242 avatar [69]arp242 edited 9 hours ago | [70]link

As an aside, to get proper floating boxes to render I think you need
at least VIM 8.2, which was still apparently unavailable last week
when I checked last.
popup windows were added throughout the 8.1 release with many
different patches (some incompatible), it’s just easiest to
say “8.2”, but the first patch was in 8.1.1364, but you
probably want at least 8.1.1513. Some features and
enhancements were added in later versions.
Vim versions are rather idiosyncratic: every commit to master
is a new “patchlevel”, and every once in a while a new
“version” is released, which is again, just a commit to master
with some docs updates, but outside of that is quite
arbitrary.
Also pretty easy to build Vim yourself if you want a newer
version than what your distro has.
1. [ ]

[71]snazz avatar [72]snazz 1 hour ago | [73]link
Neovim does a [74]far better job of versioning
appropriately and clearly, which is nice. It’s possible
that any given distro version might have a too-old Vim
but a new enough Neovim (although compiling yourself or
using a rolling-release distribution isn’t too hard).
11. [ ]

[75]jgt avatar [76]jgt edited 7 hours ago | [77]link
For some years now, my setup has remained basically the same.
An iTerm2 terminal , in full-screen, on a global hotkey, which
appears instantly with no animation. Inside that, a tmux session
for each project I am working on (I have three commercial
projects).
Inside the tmux session for a given project, I have various windows
which run e.g. psql, redis-{server,cli}, and I work from a window
which contains an equal vertical split (as in the divider runs
vertically).
On the left side is my Haskell or Elm compiler. With Haskell, I’m
always working in GHCi. I use it for interactive development,
inspecting types, running my project’s tests, and running my
project’s local development server. My GHCi is configured with a
number of flags which enable fast, incremental compilation, so I
have a fast feedback loop even on Haskell projects of a couple
hundred modules and 25K+ LOC. For Elm it’s similar, though I rarely
use Elm’s repl and it’s separate from the local development server
runner anyway.
On my right side is vim. I use vim-dispatch to send commands from
vim to the GHCi in the other pane.
Everything except for vim comes from a nix-shell.
12. [ ]

[78]akavel avatar [79]akavel 7 hours ago | [80]link
A recent breakthrough improvement for my workplace workflow was
actually in physical world, and on recommendation from a lobste.rs
user: discovering and starting to use a discbound notebook. It
allows me to easily organise and rearrange my working notes,
whereas before my notebook was chaotically intermixed and finding
stuff in it was nearly impossible.
Other than that I found similar help in Tree Style Tabs plugin for
Firefox, though it also has some aspects I don’t love; but without
it I’d be in a worse situation at work. I live by Gesturefy &
NoScript in Firefox as well.
Other than that, basically vim + Go + Linux/Mac at work, vim +
Nim/Go + Windows/Linux at home; nothing else that is special comes
to my mind. I mean, there’s a lot of small things in configs, such
as .inputrc tweaks to make bash tab-completion much better, or a
~/bin/gl script containing more or less git log --graph --oneline
--decorate --all, etc. They all come together for overall boost,
but too much to describe here. I store most of my config via Nix’s
home-manager on Linux, though it has pros & cons & doesn’t support
Windows.
1. [ ]

[81]akavel avatar [82]akavel 33 minutes ago | [83]link
PS. Can’t edit my post anymore, but I wanted to let myself
also mention [84]Ultimate Plumber, which is a tool I myself
actually created, out of a burning need (so I think it fits
the OP question), and other people seem to really like it too…
13. [ ]

[85]kornel avatar [86]kornel edited 2 hours ago | [87]link
+ [88]Fork (previously [89]GitX) is a productivity boost for me.
Using git fearlessly requires knowing “where” you are in the
graph of commits at all times.
+ Sublime with Rust extension reports errors inline, and has a
button to apply compiler’s fix suggestion. It’s a small thing,
and probably Java-IDE devs had it since ‘90s, but it’s new for
me and I love it.
+ Firefox with Tree Style Tabs and Containers extensions. I need
a million tabs open.
+ Flycut clipboard manager. It has saved me countless times when
I’ve cut some bit of code and forgot about it. Or needed to
paste again some bug number or a URL from 15 minutes ago.
14. [ ]

[90]ilmu avatar [91]ilmu edited 1 hour ago | [92]link
My environment is a mess but slowly it’s converging on what I want
it to be. I use:
+ NixOS + XMonad, the goal is to make xmonad central to
everything and reduce the dependence on text editor, web
browser and terminal window management features.
+ Kitty as terminal, I still use the kitty tabs but I will move
to xmonad tabs (and probably a more minimal terminal) once I
have finished building a couple of other features in my
xmonad.
+ Spacemacs as IDE, neovim as a terminal editor, I know it’s a
bit weird but it’s expedient for now. I’m slowly weaning
myself off of spacemacs window management, now I mostly have
emacsclients and terminals tiling my screens rather than a big
emacs window with splits.
+ Qutebrowser and firefox for browsing, this is similar to
above, qutebrowser is great and it’s easy to make small named
sessions to open and close. However I have a massive firefox
session that I need to slowly break apart and organize.
+ Zathura for pdfs, I read a lot of pdfs so this is relevant I
suppose, it’s also another good thing about using qutebrowser
is that its UI fits my pdf flow better. I use pboy or paperboy
(haskell TUI) to rename and organize my pdfs.
I use find and ripgrep a lot but I rarely reach for tmux or fzf,
although fzf is a very useful tool so I should probably start
forcing myself to use it until I start reaching for it.
Edit for “workflow”
At work I do go, I have emacs set up with a language server and a
tags file so I can jump to definition or hover on a symbol for
information and such things. When I work I mostly just make a
couple of changes, run the local tests, run the global linter and
then if it passes I send it to the CI, sometimes there’s a problem
in some other test, then I fix those and run the local tests and
global linter but never the global test suite because it locks me
out of my system pretty much…. I have a portrait screen on each
side of my laptop so it’s like having 5-7 laptop screens, the
layout I most often end up with is some kind of “emacs region”,
“browser region” and “terminal region” but I change this as I go.
My workspaces use a binary space partition layout and I have
hotkeys to rearrange the trees.
When I do things in my free time it’s mostly going to be related to
my environment, so nix and haskell, I don’t have a good flow for
nix and it’s kind of frustrating but I am actually making myself a
tool to fix this (and other similar problems). For haskell I use
ghci a lot but when I’m at home I only have the laptop screen, so
normally I have an emacs window and a terminal window and then use
the kitty tabs and emacs window splits. It doesn’t scale well
because I keep shuffling through and it’s hard to reference things
quickly or keep two things side by side or something. My work
window management flow is better but it just means that my WM
config is sufficient when I have enough screen space but I am
missing quite a few features for managing many windows in a smaller
viewport.
Currently where I suffer the most is with note-taking, I use
org-mode but I’d rather have a graph database.
15. [ ]

[93]pfcuttle avatar [94]pfcuttle 1 hour ago | [95]link
Depends on the machine I’m working on, but common elements are:
+ Zsh, tmux
+ Vim for Python, YAML, XML, Make, etc…
+ IntelliJ for Java
+ VS Code for HTML, CSS, JavaScript and TypeScript
+ Firefox with adblocker and privacy extensions
+ All the nice Rust utilities that popped in the last few years:
bat, fd, hexyl, rg, etc…
I do customize all the tools I use. For now I settled on:
+ [96]Fira Code with ligatures
+ [97]Ayu Theme
+ Horrible hacks to make those damned italics work with tmux and
vim
Desktop is on Manjaro, work machine is on MacOS.
16. [ ]

[98]dsh avatar [99]dsh 53 minutes ago | [100]link
I’m a web developer, so there’s a few tools I use every single day.
+ PHPStorm - my IDE that I use for PHP and Node.js development -
very good debugging and code completion included here.
+ ElementaryOS - very beautiful, but I’m moving back to Xubuntu
at the end of the month.
+ Vagrant - spins up a PHP environment for Magento 2 development
- as well as other PHP services and apps we develop in house.
It also has Node.js installed for front end building
+ Node.js - right on the bare metal to run scripts, test stuff
+ PHP on the bare metal to test, write, etc
+ SAM for developing single AWS Lambdas locally
+ Slack to talk to the team
+ Firefox is the main browser, we have Office 365 so I use the
Outlook web client a lot for emails - the first time I ever
let a web app push notifications through the browser
+ I use regular old BASH with TMUX in my terminal
+ Vim for editing configs and other system files
+ HTTPie for testing RESTful APIs and services
+ DBeaver for Database Management
That’s all I can think of that I use every day.
17. [ ]

[101]nikivi avatar [102]nikivi 25 minutes ago | [103]link
My one is described in GitHub repo for [104]macOS & [105]iOS. I got
new mac a month ago so it is further simplified, will update the
repos shortly.
But of the recent things, I moved most project management to Notion
from Trello. Started using VS Code insiders with minimal
extensions.
I want to rewrite and/or start using
[106]https://github.com/Keats/kickstart to bootstrap new projects.
18. [ ]

[107]vhodges avatar [108]vhodges 17 minutes ago | [109]link
+ Bash shell
+ Kitty terminal emulator
+ Tmux (when remoting in to my linux box and at work)
+ Emacs (pretty vanilla these days, just a few extra packages)
+ WindowChef for my X11 WM
+ Make (except for Rails)… even for Go, muscle memory and
shorter to type :)
+ Basic POSIX tooling (grep, etc)
+ Aging (but still going strong!) 1st gen Retina MacBook Pro
(mid-2012)
+ Newish desktop Linux box (2015) runnng Arch

[110]Moderation Log [111]Hats [112]Tags [113]Wiki [114]Privacy
[115]About

References

Visible links
1. https://lobste.rs/
2. https://lobste.rs/recent
3. https://lobste.rs/comments
4. https://lobste.rs/search
5. https://lobste.rs/login
6. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks
7. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks
8. https://lobste.rs/t/ask
9. https://lobste.rs/t/programming
10. https://lobste.rs/u/mraza007
11. https://lobste.rs/u/mraza007
12. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks
13. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks
14. https://lobste.rs/u/evanrelf
15. https://lobste.rs/u/evanrelf
16. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_kclyoj
17. https://lobste.rs/u/alicebob
18. https://lobste.rs/u/alicebob
19. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_ik6bcl
20. https://lobste.rs/u/duraki
21. https://lobste.rs/u/duraki
22. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_09tgit
23. https://lobste.rs/u/akavel
24. https://lobste.rs/u/akavel
25. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_i6uftz
26. https://lobste.rs/u/stephenr
27. https://lobste.rs/u/stephenr
28. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_nesddr
29. https://lobste.rs/u/pfcuttle
30. https://lobste.rs/u/pfcuttle
31. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_ostflj
32. https://lobste.rs/u/stephenr
33. https://lobste.rs/u/stephenr
34. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_pyferg
35. https://lobste.rs/u/zge
36. https://lobste.rs/u/zge
37. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_hmngim
38. https://zge.us.to/emacs.d.html
39. https://lobste.rs/u/twee
40. https://lobste.rs/u/twee
41. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_5r7ior
42. https://lobste.rs/u/Ameo
43. https://lobste.rs/u/Ameo
44. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_zofllt
45. https://lobste.rs/u/danielrheath
46. https://lobste.rs/u/danielrheath
47. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_mw5w9v
48. https://lobste.rs/u/artemis
49. https://lobste.rs/u/artemis
50. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_qgak0s
51. https://talonvoice.com/
52. https://lobste.rs/u/indirection
53. https://lobste.rs/u/indirection
54. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_knnrof
55. https://lobste.rs/u/twee
56. https://lobste.rs/u/twee
57. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_wpa2s5
58. https://distinctly.pink/colophon.html
59. https://lobste.rs/u/yumaikas
60. https://lobste.rs/u/yumaikas
61. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_80rud6
62. https://lobste.rs/u/jclulow
63. https://lobste.rs/u/jclulow
64. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_akxkzt
65. https://github.com/rust-analyzer/rust-analyzer
66. https://github.com/prabirshrestha/vim-lsp
67. https://rls.booyaa.wtf/
68. https://lobste.rs/u/arp242
69. https://lobste.rs/u/arp242
70. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_tgs3gn
71. https://lobste.rs/u/snazz
72. https://lobste.rs/u/snazz
73. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_hrwxf4
74. https://neovim.io/roadmap/
75. https://lobste.rs/u/jgt
76. https://lobste.rs/u/jgt
77. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_7fldzu
78. https://lobste.rs/u/akavel
79. https://lobste.rs/u/akavel
80. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_x2kyzk
81. https://lobste.rs/u/akavel
82. https://lobste.rs/u/akavel
83. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_pfw3a9
84. https://github.com/akavel/up
85. https://lobste.rs/u/kornel
86. https://lobste.rs/u/kornel
87. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_0eyo8p
88. https://git-fork.com/
89. https://rowanj.github.io/gitx/
90. https://lobste.rs/u/ilmu
91. https://lobste.rs/u/ilmu
92. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_hwxnm6
93. https://lobste.rs/u/pfcuttle
94. https://lobste.rs/u/pfcuttle
95. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_gut6zx
96. https://github.com/tonsky/FiraCode
97. https://github.com/ayu-theme
98. https://lobste.rs/u/dsh
99. https://lobste.rs/u/dsh
100. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_ctnd9r
101. https://lobste.rs/u/nikivi
102. https://lobste.rs/u/nikivi
103. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_xnnlb2
104. https://github.com/nikitavoloboev/my-mac-os
105. https://github.com/nikitavoloboev/my-ios
106. https://github.com/Keats/kickstart
107. https://lobste.rs/u/vhodges
108. https://lobste.rs/u/vhodges
109. https://lobste.rs/s/qi5dmk/how_does_your_current_dev_workflow_looks#c_wawk7c
110. https://lobste.rs/moderations
111. https://lobste.rs/hats
112. https://lobste.rs/tags
113. https://github.com/lobsters/lobsters/wiki
114. https://lobste.rs/privacy
115. https://lobste.rs/about

Hidden links:
117. https://lobste.rs/
118. https://lobste.rs/login
119. https://lobste.rs/login
120. https://lobste.rs/login
121. https://lobste.rs/login
122. https://lobste.rs/login
123. https://lobste.rs/login
124. https://lobste.rs/login
125. https://lobste.rs/login
126. https://lobste.rs/login
127. https://lobste.rs/login
128. https://lobste.rs/login
129. https://lobste.rs/login
130. https://lobste.rs/login
131. https://lobste.rs/login
132. https://lobste.rs/login
133. https://lobste.rs/login
134. https://lobste.rs/login
135. https://lobste.rs/login
136. https://lobste.rs/login
137. https://lobste.rs/login
138. https://lobste.rs/login
139. https://lobste.rs/login
140. https://lobste.rs/login
141. https://lobste.rs/login
142. https://lobste.rs/login
143. https://lobste.rs/login
144. https://lobste.rs/login
145. https://lobste.rs/login