3 ms·
Coming from a statically typed background, having Sorbet types in a Ruby/Rails monolithic codebase helps immensely. I can think of 3.5 ways my productivity is
by karmakaze 2y ago
Coming from a statically typed background, having Sorbet types in a Ruby/Rails monolithic codebase helps immensely.
I can think of 3.5 ways my productivity is limited:
1. how fast I think: understand problems/come up with solutions - not a bottleneck as I juggle things waiting on (3)
2. how fast I write - this is the least impactful, if you do it right there usually isn't that much to write. Having dependable refactoring tools for a Ruby/Rails codebase would be killer.
3. how fast I
a. test - this has been getting slower
b. ship - the slowest by far, time cycling in reviews, CI/CD pipeline
That is to say don't over-optimize your tools in areas that don't impact the slower parts of your flow.
- ativzzz 2y ago> a. test - this has been getting slower AI helps with this one - if you use a code editor that has an AI plugin, being able to write out some describe/it blocks and add the code you're testing to the LLM context as well as some similar specs, the LLM can bootstrap parts of it for you
- karmakaze 2y agoSorry I mean running not writing tests. I like the suggestion to use LLMs to write them. I often use them to catch typos. The codebase I work in is a monolith and the test runner is optimized for running many tests not one-offs.
- ativzzz 2y agoAh I see. Yea our CI is getting slower with more tests but so far we've found increasing parallelization helps. And for one off tests, spring + rspec is good enough