2,752 karma · joined August 24, 2012
The idea is universally we can all relate to the negative, but the good is rarely universal, but often local.
This is what drives social media or media in general to tend negative.
https://matthewevanseducation.substack.com/p/why-context-mat...
https://www.researchpubs.com/shop/p/research-89-jg-ballard-l...
https://www.canarymedia.com/articles/clean-energy-manufactur...
But now that is problem is solved a director will come along and say... I want a scene with a big glass of water and the camera will zoom in on it and will see the monster refracted through the glass.
We took an Elm app from our web app and put into Excel to control downloading reports. Works great.
Except you have to side load this and that is a pain - or you have to go through the MS App Store, which is a whole other headache.
If anyone has any advice on making it easy for customers to install Office apps please let me know.
Someone of this could be system overload I suppose.
One of the problems with writing detailed specs is it means you understand the problem, but often the problem is not understand - but you learn to understand it through coding and testing.
So where are we now?
Once, my wife and I were stopped, but not frisked, and cited for riding bikes, on a sidewalk at 2AM on a stretch of Atlantic Ave that would kill you to ride on. It made no sense, until I found out that my neighbor and his friend had been murdered at a street party. There was a drag net out trying to find the killer and they stopped anyone for anything.
A tough city.
For these tests we don’t care about the content only that something didn’t get incorrectly set or the mailer interface changed.
Now if the developer changes the Mailer to require a user object the compiler tells us there is an error. Sorbet will error and say “hey you need to update your code here and here by adding a User object”
Before we would have had test coverage for that - or maybe not and missed the error.
And the LLMs take advantage of the types through the LSP and type checking.
It’s not like Ruby becomes Haskell. But it does provide a good deal of additional saftey, less testing, LSP integration is good, and it is gradual.
There is a performance hit but we found it to be quite small and not an issue.
But there are area of our application that use Grape and it is too meta for Sorbet so we don’t try and use it there.
But was Space Jam using multiple images or just one large image with and image map for links?
https://sorbet.org/blog/2021/07/30/open-sourcing-sorbet-comp...
There are deeper problems here that a Result type is not gonna fix.
We have started to use typed HTML templates in Ruby using Sorbet. It definitely prevents some production bugs (our old HAML templates would have `nil` errors when first going into production).
But most of the US this is impossible by design. Where I grew up you might live right next to a grocery store- but it is a mile walk because of the wall and road design. Nuts.