The most annoying thing about software engineering
Is how you spend 2 weeks learning intensely about some topic (e.g. how to do graceful shutdown properly),
And 6 months later you completely forget everything 😡
20 years ago we released Grand Theft Auto - San Andreas.
The original plan was for the 3 cities to be on separate maps. The player would travel between the cities using trains and planes.
(Gta 1 and 2 also had three cities on separate maps)
Memory was very tight on the ps2 and with separate maps, the other cities’ skyline models wouldn’t have to be in memory.
It would also make it easier to have different police/ambulance/firetrucks for each city. Different pickups, weather types etc.
It would also be easier to contain the player until it was time for the next city.
It would also make it easier to organize the models on the DVD city-by-city which would help the streaming.
Just before the artists started working on the three maps, we had a final meeting at R* North in which we changed our minds and decided to go for a big map after all.
We still ended up doing city-specific pickups, police cars and weather.
Happy birthday San Andreas. You turned out all right.
Here are 4 great job boards I've been exploring lately that offer solid alternatives to LinkedIn:
1️⃣ Remote: https://t.co/ABenzhleGO
2️⃣ UI/UX Job Board: https://t.co/gf8rc8spIO
3️⃣ NoDesk: https://t.co/hWqoPWA7Wx
4️⃣ Glassdoor: https://t.co/rXSi9jXEeh
Problem: If an app makes multiple GraphQL calls on the same page, all the GraphQL calls look the same in the network tab.
My approach: Click on each call, one by one, to view the payload's query name.
This is time-consuming.
Anyone have a trick for this?
I've written a lot of stuff about sustainability in football - and there are a lot of well-meaning initiatives.
But there's always an elephant in the room: short-haul flights.
Last night, after beating Newcastle, Liverpool took a 33-minute flight home.