So if you specify work the right way, you can move at incredible velocity. If you have the confidence in your setup and ways of working, you don’t need to look at the code being put out.
Genuinely seeking answers on the following - if you’re working that way, what are you “understanding” about what’s being produced? Are you monitoring for signal that points out gaps in your spec which you update; code base is updated, bugs are fixed and the show goes on? What insights can you bring to how the code base works in reality?
Not a sceptic, but thinking this stuff through ain’t easy!
Is there a way to link to the Tip Jar, or do you have to direct people to your profile? When I've seen people offer tip jars, it's at the end of a long thread and takes people to a payment service. I wonder how "Tip Jar is on my profile" would perform against a link in a tweet.
I saw a tweet yesterday about having to leave the screen on, but it turns out the source website was updated to remove that line, and that's not how the app works. However, there are also screenshots on Twitter of lock screen notifications saying that the app needs to be open so I don't know any more...
They made it to generally available to everyone, but still had a (*beta) tied to it for a while. Maybe that’s gone now, but it’s still missing a lot of essential features and they know it.
Salesforce use this in their Lightning Framework. I've not gone beyond the surface of that framework, but I've found its use of proxies adds friction to development. Trying to debug in the browser, anything other than a primitive results in a looking at an empty Proxy object - I believe this is a deliberate choice behind the framework in the name of security. But it makes it much harder to discover what's in an object - if you don't know the name of a property, good luck getting it.
Note that this is either due to how the framework uses Proxy, rather than Proxy itself, or I'm doing it wrong and should do more reading up on it. It really could be the latter - given my level of experience and knowledge, I thought hard about posting this comment!
I was recently playing through Super Metroid on the SNES mini, and I ended up watching a "World Record Progression" video on YouTube. Turns out there's a series of these videos[0] done for a number of games - they're pretty well done, and it's fascinating to hear the level of effort people put in to shaving time off a World Record.
Oh, Super Metroid is such an amazing speedrun. Over the last week's time, Zoast has been setting new WRs at least 3 times and there's still at least 10 seconds to be saved with the current route + optimal RNG.
Sorry to pick on your response, and you're right, a factory reset might be worth a shot, but factory resets on Android are a PITA. The last time I did it (my last 3 phones have been Nexuses), it literally took half a day to get the phone back to the point it was at previously - I had to install OS updates, re-install apps (which also reset to 0 in many apps), re-download music (I admit, I could copy files over from my laptop). It makes setting up a new iPhone for the wife look like magic.
I wouldn't mind, but even with Nexus phones, my experience of issues is that you end up crawling Google, and the answers are the technical equivalent of doing the hokey cokey in the hope of curing a cold: "Uninstalling Snapchat made the problem disappear!"; "Install this app and use it to work around an issue", etc.). And then the last resort - the factory reset. I'm not doing anything particularly exotic with my phone, the thought of the hassle of a factory reset is just depressing.
I bought a Nexus 5X at launch, after my replacement Nexus 5's power button died. And it has been a laggier experience than the 5 (I admit the latest update seems to have improved things (though it's still not equivalent to the 5 IME). But looking for other people with the same problem you see the same responses, like a repeating background in a roadrunner cartoon - "Mine runs buttery smooth"; "Maybe yours is faulty, RMA?"; "Tried a factory reset?". Sorry, I don't enjoy this detective work/maintenance.
I doubt the iPhone experience is perfect, but it can hardly be worse, can it?
Ahhh no. Factory resets don't do ANY OS upgrades. All they do is wipe the data partitions. Unsess you downgrade the firmware no OS needs to be upgraded.
I've wiped my n10 many times. Wipe boot and let it reinstall. Takes a while to reinstall but hands off.
The n10 is problematic hardware wise. Mine will do random reboots and always has. Boots fast so not a huge issue but annoying.
Thank you for this. I don't understand why other posts are so heavily weighted with arguments of "Oh, so they didn't solve the homeless problem, so now the whole problem is their fault?" Amazon either took advantage of the scheme, or rushed in - maybe even with the best of intentions - without thinking through or committing to what was actually required to make it a success.
> It's the failure to follow through and provide the promised stability.
What evidence is there of failure to follow through? Temporary-to-permanent does not mean someone is guaranteed a permanent position, it means they have a chance at it. The permanent positions might be relatively small in number, and highly competitive, so some workers will not get it. Who is most likely to be interviewed by a newspaper and have an axe to grind?
The article would be more informative if it shared data about what percentage of workers were hired as temps, and how many full time positions were expected to be hired afterward, and how many of the homeless hired as temps made it into full time, and so on. Without that information, the article is just an anecdote from a person or two.
The nature of temp work is that it's not permanent, and no one hired into a temp job should have the disillusion that they will definitely get a permanent one. Temporary-to-permanent work means that there's a chance to stay on if you're good - you're not definitely going to get fired, nor do you definitely get to stay.
Genuinely seeking answers on the following - if you’re working that way, what are you “understanding” about what’s being produced? Are you monitoring for signal that points out gaps in your spec which you update; code base is updated, bugs are fixed and the show goes on? What insights can you bring to how the code base works in reality?
Not a sceptic, but thinking this stuff through ain’t easy!