2,848 karma · joined November 11, 2013
vincent.voyer@gmail.com
They should not allow car Manufacturers to sell cars when: - There's no physical knob to open it - The only place to read critical information like speed is a tablet on the side - The speed limit is a constant beep unless you disable it AT EVERY START by touching a screen on the side (their law basically)
My wife got a new Volvo recently:
1. You can only open it with your phone (find it in purse, unlock it, find the app, wait, click) or a card that can only open on the driver side (can’t open the trunk). What was fucking wrong with keys?
2. No behind the steering wheel screen, only a large tablet center of the car. No way to know your speed without looking to the side.
3. No physical buttons aside from the ones on the steering wheel.
4. And the infamous speed limit beep sound. You can turn it off with a shortcut button on the steering wheel. Which is so dumb if you think Europeans spent millions creating and implementing this rule. A friend of mine has no shortcut (kia) so he just starts driving then look away from the road to the screen to tap a few times. I’ve seen this many times now.
Overall cars are more dangerous to drive because of all this shit. Europe is spending millions creating laws to protect us on the road and making driving shitty. While Youtube, social networks and movies keep promoting cigarettes and alcohol.
Ask a colorblind person to explain how to win at candy crush and you'll be surprised (hint: we do not use colors, we use the shapes).
"If you want to partition your data even better, you can introduce some randomness in your key names": https://youtu.be/2DSVjJTRsz8?t=2206
FWIW The optimal way we were told was to partition our data was to do this: 010111/some/file.jpg.
Where `010111/` is a random binary string which will please both the automatic partitioning (503s => partition) and manual partitioning you could ask AWS. Please as in the cardinality of partitions grows slower at each characters vs prefixes like `az9trm/`.
We were told that the later version makes manual partitioning a challenge because as soon as you reach two characters you've already created 36x36 partitions (1,296).
The issue with that: your keys are no more meaningful if you're relying on S3 to have "folders" by tenants for example (customer1/..).
> git(main) x npm add better-auth
to
> npm add better-auth
"git(main) x" looks odd and like an error.
- the AI doesn't know when to stop talking, and the presenter had to cut every time (the usual "AI-splaining" I guess).
- the AI voice and tone were a bit too much, sounded too fake
Is Stainless similar, different?
- https://www.mnot.net/cache_docs/ for a long time this was the best online resource
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching is extremely detailed, and based on the previous link too from what I can tell
https://www.eden-park.com/ down https://allbirds.eu/ down https://www.jbhifi.com.au/ down
- GitHub now requires 2FA
- Author reaction "Greaaaaaat, Microsoft wants to harvest more phone numbers."
- Author has a love/hate relationship with GitHub since 2012
- Author decides to not use GitHub anymore
I am not following the thinking process. And you can use a 2FA app, without giving your phone number to GH.
I can understand the stream of changes at GitHub does not resonates with the author opinions, but the "Microsoft wants phone numbers" is wrong I think.
If you have questions on how this is implemented, let us know :)
Wait, what happened to the missing 225 Starlink spacecrafts?
This is one of the biggest contributor for high performing profiles.
To manage this when using Slack you can:
- set your status as “deep work” and decide to pause notifications for x hours
- use “mark as unread”. when you want to peek something but not act on it yet
- use “remind me” on messages you want to deal later on through the week
- avoid DMs has much as possible, so not just one person can help you, but anyone from your team
- avoid Slack on the phone
Then deal with notifications in bulk.
Slack isn’t killing our productivity, HN and twitter are not killing it either.
Our addictions to notifications is, but we can manage this with discipline and training.
Now making almost $500 MRR with 10 customers.
This is an app to share tasks, duties and manage rotations in Slack. It was an internal tool at my previous company (Algolia), that I rewrote with their permission as a SaaS and sold to them. Growth is slow, mostly driven by Google searches and Slack app store.
One out of 10 signups per month will eventually use the service. For the few ones I've been able to ask "Why did you leave", the answer is: they want a Google Calendar for Teams. Which I am slowly building. This way, the shift scheduling will be more flexible.
Show HN thread: https://news.ycombinator.com/item?id=26025254
I would say:
The true reasons Firefox lost market share is because we, developer & tech people started to install Chrome on family computers instead of Firefox because it was safer & faster (way way faster). And we never came back from it.
Performance is a feature.
Thanks!