3 ms·
I can't speak to the technical aspects here (I'm only familiar with nextjs not rails, so it's unclear to me how much of the article is just a reflection of the
by ummonk 1y ago
I can't speak to the technical aspects here (I'm only familiar with nextjs not rails, so it's unclear to me how much of the article is just a reflection of the author's own comfortability with rails or a reflection of a more technically suitable architecture). But I do find it really weird that a company which apparently has multiple software engineers is worried about infrastructure costs amounting to less than $1k a month... Seems penny-wise pound-foolish to be worried about hosting bills.
- gedy 1y agoYeah, we were spending 10s of thousands of dollars on CI costs a month for a huge Rails app's integration tests alone..
- adenta 1y agoWhat CI provider?
- gedy 1y agoWas using TeamCity, then dropped some moving to another system. The broader point was basically that the Rails UI integration tests took a very long time, and required the whole system up, and we had a pretty large team constantly pushing changes. While not 100% unique to Rails, it was exacerbated by RoR conventions. We moved much of the UI to a few Next.js apps where the tests were extremely fast and easy to run locally.
- PapaPalpatine 1y ago> Rails UI integration tests took a very long time How many integration tests do you have? I generally only test a few core flows and then leave the rest to controller/request tests.
- gedy 1y agoA lot. We were moving towards that approach when I left, though the detailed UI tests were then in JS tests which didn't need the whole app running.
- dyogenez 1y agoWe have one developer (me) and we're bootstrapped and not yet profitable. That means I'm paying the difference every month in hosting and working for free. The site makes it look like we have a lot more together than we are.
- ummonk 1y agoFair enough. I think I misinterpreted the "as new team members joined" paragraph as talking about other engineers.