I remember my time doing Ruby was really informative about testing and languages in general.
The Ruby community was really great at doing automated testing and it's actually where I really cut my teeth on testing, but if you go back and look at the tests you'll find heaps of them are testing and checking types for functions. It almost felt like people were building static typing using automated tests.
Some people bang on about static typing getting in the way of agility, but the reality is that you either end up spending the time creating extra tests, or you end up cutting corners and creating unreliable software which you'll spend a lot of time troubleshooting down the road. You end up paying a big price to save a marginal amount of time at the start of a project.
Better than an ORM is to use a query builder. You get the expressiveness of SQL with the safety and convenience of an ORM.
Most developers that use ORMs create poorly performing monstrosities, and most developers who write raw SQL create brittle, unsafe and unmaintainable software. There is a happy medium here.
Source is safely_endangered on IG. Original has an extra panel but I actually think this version is better.
IGA in Canberra is such a mixed bag.
Some are amazing, super clean and organised and have a unique range of stock. Others feel like a dirty old highway servo in the middle of nowhere where half the stock is out of date.
My original account @beefsack@lemmy.ml was when the project was announced 4 years ago (was either HN or r/rust) but to be honest I've only been properly using Lemmy for a few weeks.
thanks for using Leebra!
go to feed...