2,611 karma · joined December 12, 2012
[ my public key: https://keybase.io/wildpeaks; my proof: https://keybase.io/wildpeaks/sigs/yQmAnhmw5ODzOpfBpYvX1T7owc-Fwoe6TpMkU8-94Ho ]
Being in the Share menu, I'd only see "Add to home" while already in the process of sending to someone else, so I wouldn't have time to check what this is (as it would distract from my goal), and I'd have forgotten the option exists by the time my task (sharing the site) is complete.
I use both iPhone 13 Pro & Pro Max everyday because I do iOS development (among many other things), so it's not like I don't know how to use the newer models, but the Home button is so intuitive I can use the 7 even when I'm half awake whereas I need to pay close attention to the screen on 13.
Not having a Home button is like a keyboard without an Esc key.
You can especially see it now with long COVID reducing mental capacities short or long term: processes that were designed to require only low mental load (thanks to automation and tools) didn't break and business continued to operate smoothly.
Accessibility is good for business.
For example: "we use Github for source control: it has good security, price is reasonable, comes with a bug tracker and a CI that are easy to use" is more than enough.
It's also more than OK to reply "I don't know, but I can find out if you think it's important", they're not performing a power play, they're merely looking for information in the same way they'd look for information from a computer.
It's also a way to know if it's a company culture where higher ups frown upon underlings asking pragmatic clarifying questions when assigned a task (another red flag because ego will hinder the productivity because developers will fear angering higher ups and will build the wrong thing, thus losing time and money you can't afford to waste in smaller companies).
It's also a way to give insight when onboarding new developers: if something is surprising, they can see why things came to be this way, not just accept the result at face value.
I'd recommend automating it with Fastlane (https://fastlane.tools).
Or perhaps like Gmail: stores the message but doesn't send until a few minutes later, at which point it's no longer editable. This would be easier to implement.
https://docs.github.com/en/pull-requests/collaborating-with-...
They already try to own the entire pipeline for 3D creation, not just for games but anything 3D.
They don't see Fortnite as a game, but as a platform (Errant Signal had a good essay on that topic two years ago: https://www.youtube.com/watch?v=qNukmNDq60Q) and it's only been more visible ever since, acquiring key tools like Sketchfab, RealityCapture, Quixel, and Artstation.
Also could be a source of creative content to generate NFTs, maybe even tie that to licensing of music used in game livestreams.
While the 3D scene is certainly the kind of model we'd have at the time, I'm impressed they have a 3D hand to grab products. The more I look at it, I think it's using the keyboard to walk around and the mouse to move the hand.
Build pipelines don't merely concatenate a few scripts, they're meant to automate the boring parts we used to have to do by hand (like copying assets with cache-busting filenames and update matching references, set the correct image sizes, generate SRI hashes, generate sourcemaps, generate sitemaps, check the quality of pages, etc). This way you can focus on writing the application and keeping it maintainable without having to waste time remembering to use javascript hacks (like `!1` instead of `false`) to save a few bytes like we used to.
It's when people indiscriminately feed them big frameworks that things bloat, same way you won't be lightweight with a junk food diet.