I have a feeling that he wasn't carrying the USB-C cable because he expected some kind of guerilla-connector-change suddenly on the iPhone in his pocket, but it is being used with another device.
Even crazier - outside US its massively easier to find usbc cable compared to lightning. I hope those frequent days when some (usually the same but now always) colleague is running desperately around the office interrupting everybody looking for one will be finally over.
I don't understand this. When traveling internationally I've never had a problem locating a Lightning cable.
Though I have to mention, you shouldn't really shop for cables when you're traveling and need a new one. First stop by the front desk, they usually have a huge pile of charging cables people have left behind.
Anyone who has worked in an office outside of the USA has experienced the annoying iphone user asking everyone for a cable to charge his phone because he lost/broke/forgot it.
And not all the offices are close to a shop selling those kind of things nor do these persons feel they might be better off going shopping for one directly instead of disrupting a non negligible amount of workers.
I don't even know why people have to charge their phone midday and can't wait. Even when I am going out and extending the night until dawn, I usually have battery left until I go to bed.
Hi. Just looking at the site. Under "adopted projects" you list Light Table. But the link just goes to the old, unmaintained repo. It would be great if you could also link to the maintained versions of repos.
The list has repos that Code Shelter has access to (ie ones that you can request to join). We don't have access to the new Light Table repo, so it wouldn't be apt to add there.
Apologies if I'm being dumb, but I'm confused. I assumed "adopted" implied that Code Shelter has some alternative repo that it (Code Shelter's community) is maintaining. Is that not the case? If not, then why list it at all?
No, "adopted" means that you gave Code Shelter permission to add contributors to your repo (the same repo you've always used). Otherwise, there wouldn't be a need for CS, since anyone can fork any repo.
CS is there to ensure continuity for the original repo (and releases).
Reading the posts doesn't require an account. Seems fair that other functionality (voting, reading list, custom blogs, etc.) would require an account.
Edit: I got an account. The "blogs" page is a mix of blogs you follow and default blogs. I guess that shouldn't really need an account to see the default blogs.
Probably didn't think of it. If you were using Audacium it's because you were looking for Audacity forks in general, so you would already know about Tenacity too.
I forget where I heard this, but someone put it this way: to the markets, 10% is a positive signal that a company is cutting some cruft, but 25% is a negative signal that a company is in trouble.
After the first dotcom boom I survived two layoff waves of 7%, about 6 months apart. Our branch wasn't loosing money but every office had to report enough employees to headquarters so the 7% can be met because that's the number that was used in the press release and earnings call. As others wrote at the same time company was still hiring (at least engineers) and some marketing positions just moved to an agency which then billed us per hour for the same person.
It draws attention to a problem that a lot of people have created for themselves by not reading the documentation (or not recalling it if they read it). I guess the author could have just linked the documentation but then they couldn't have added the additional context of the github search demonstrating how common it is.
I must have looked through the docs for create_task a dozen times while trying to figure out how async/await works in Python but still managed to overlook this part.
The author doesn't go into much detail on that point: this warning should be present in documentation of many Python libraries that use create_task and return the result to the user unless that library stores those tasks in a collection as is recommended -- at which point the library author had better roll their own garbage collection!
