@SumitM_X I remember having to do this back in the day because adobe flash couldn’t get the respond body of a non 200 response 🤦🏻♂️. Thankfully those days are long gone.
@Abhinavstwt I had this on an old MacBook. It was the coating coming off. I managed to remove it all by giving it a good rub with alcohol based screen wipes.
@coorasse Keep it a monolith. Run 2+ servers point the web at one and the api at the other (subdomains) and you can scale them independently of each other. I’ve been down the route of separating them into separate apps and having a “core” shared gem and it’s not worth the overhead.
@sj26@siaw23 Agreed on this. I run all my dev servers/tests within docker. Only thing I’m yet to figure out nicely is getting rubocop/linting working in vscode without having to install ruby/gems outside docker.
@_swanson I’ve been doing rails 15+ years and find juniors a good source of methods/features I’ve missed. I guess us old timers have the tendency to use the methods we know where as they spend a lot more time reading docs.
@d_feldman I suspect a lot of people who don’t already have an electric car would be quite anxious about having their first go in one as a rental especially somewhere away from home.
@_swanson I can’t find the article now sadly but it suggested making all jobs resumable then automatically killing then after X seconds. That way the job gets it’s “fair” amount of time before getting added back to the queue to continue later.