

Uhhhh, I dunno, I suppose that’s possible. Rotten Tomatoes wasn’t around in 2000, was it? Would they have aggregated from, like, newspaper reviews at the time?
Uhhhh, I dunno, I suppose that’s possible. Rotten Tomatoes wasn’t around in 2000, was it? Would they have aggregated from, like, newspaper reviews at the time?
This came out a year BEFORE the first F&F movie.
I JUST rewatched Gone in Sixty Seconds on a whim, on like Thursday, and spotted that it apparently has a 38% critic rating from Rotten Tomatoes. Fuck that noise, that movie is a materpiece of filmography.
Many of the articles from those platforms are useless noise, but I do still occasionally want to read something that’s posted. When that happens, I just F12 and bypass the paywall, or look for the comment that has the article text, from someone else who has already done that.
A very large portion (maybe not quite a majority) of software developers are not very good at their jobs. Just good enough to get by.
And that is entirely okay! Applies to most jobs, honestly. But there is really NO appropriate way to express that to a coworker.
I’ve seen way too much “just keep trying random things without really knowing what you’re doing, and hope you eventually stumble into something that works” attitude from coworkers.
Generally, you want to salt ss early in the process as tasting is possible. Allowing it to cook into the food makes it more effective, and you’ll usually end up using less overall.