Second this. I could use it in place of DataGrip if the company doesn't buy it for me.
learningduck
Joke on me. My company is full remote work, but add more meetings because we have to communicate live somehow, even though we can work asynchronously. Less focus time for me.
I learned the hard way that no is false in yaml. Took us a while to realize why our app failed to start in Norway. Too many ways to do something.
discovered that a molecule in LAL called factor C was responsible for its clotting action. Researchers genetically modified the guts of insects—who belong to the same phylum as horseshoe
How about prefixing your commit with a ticket number?
If a commit message has too much information, then the commit has too much changes
Think of that Coyote and the roadrunner cartoon. If there's a graffiti that looks like a tunnel the coyote may run into the tunnel based on vision alone, but a secondary sensor will help telling that there's a wall.
Irl, If the vision failed to recognize that there's something on the road, at least a secondary sensor will protest that there's something on the road.
How are they essential when most consoles aren't 4k capable. Switch, Series S, PS4 they all look fine on a 4k TV. Games on Series S even take less storage space, because they don't use 4k assets.
True that. Coming from Windows, I really don't understand why this feature isn't built into Mac. Most Linux distros have this feature.
But they don't have to compile shaders every time the game is launched. Only when I install a new content or the first time I install the game.
Steam or whatever launcher could still ask the resolution I want to use before it starts downloading. If the player changes their mind, then they can download higher resolution assets later.
Diablo 2 back in the day would ask which resolution I want to play on in its installer.
I wish these games had some options that let me choose which resolution I want to play on and download resources just for that resolution.
I learned about this page from The primetime and I mostly agree with the Grog especially on software testing. It's funny that it came up when I was adding integration testing to our project that's relying only on unit test with 0 integration testing. So many mocks are required and changing any behavior, while wishing that you don't forget to update every mock is a wishful thinking.