HN user
67% is good enough for me. I am not using it as a medical device, and I am not an elite athlete. I just enjoy doing exercise, and every now and again I like to review the stats from my watch.
CRA has been a maintenance burden for my team for the last couple of years due to security vulnerabilities and incompatibilities in old packages.
We have several React apps (created with CRA) to support, embedded deep inside ASP.NET Web Forms apps (its legacy all the way down).
We decided to switch from CRA to Vite. It has worked great so far.
I am happy to see these docs recommend Vite as an option for adding React to existing apps, because at the time this decision was made on my team, it wasn’t very clear what the correct path was for replacing CRA. I don’t think we could have as easily switched to a framework like Nextjs.
If you are in a similar situation, I would recommend Vite.
Similar to wanting to start a blog, but instead of writing a post, spending significant effort building the platform. First post becomes ‘how I built my blog’.
Are these types of repos trust worthy, or is it best to download straight from Signal’s site?
Similarly, I noticed Signal is on Flathub [1] for installing via Flatpak, but the developer account is ‘unverified’. It’s always put me off installing via this method.
I struggle with reading speed, and concentration in general when reading. No idea why. However, I love listening to podcasts, audiobooks, videos etc. at 3x speed.
Using text to speech has also helped. No longer do I delay reading long messages from coworkers, or dread reading boring documentation. I just use text to speech. It works really well on Windows (my current work laptop), but unfortunately not so much on Linux (personal laptop) or mobile (too fiddly).
It’s great that Google is extending the support, and that GrapheneOS can benefit from it.
I bought a Pixel 4a specifically for installing GrapheneOS. I used it happily for almost 3 years, until EOL firmware support. The phone worked fine, but I wanted the reassurance of firmware security updates.
I was going to get a Pixel 6/7 (I forget which was available at the time) to use GrapheneOS again, but I was so annoyed at Google for only supporting firmware for 3 years, that I decided to switch to an iPhone SE.
Shortly after this, I believe the next Pixel came out with 5+ years support. I had some regret, but the iPhone SE is OK, and I didn’t want to buy a new phone just for the sake of it.
I will probably switch back to GrapheneOS for my next phone, as it really is a great mobile OS. Hopefully the project is still going strong by then.
True for the OS, but you won’t get firmware updates/security patches once the upstream vendor stops support.
Smaller companies have less traffic, need less expensive servers, and have no need to spend money optimising the language. They can focus on that when they make billions of dollars, like Shopify does.
Very interesting! How this data was acquired?
The resource to be deleted should be identified in the URL, so there is no need to pass a body. This is the same for `GET`.
He admits the company will die if advertisers pull out, and his solution is to document it and let the world know that the advertisers were the reason the company died.
Curse you advertisers for ruining his company!
I’ve been using NewPipe for years, and have not experienced issues as you described.
Make sure you are using their own f-droid feed.
Oops, link seems to have lost part of its path.
Should be https://www.kevinwmcconnell.com/aws/faster-referer-service-c...
I think you could run this service on CloudFront Functions, if you didn't mind using a Refresh header instead of the meta tag.
(CloudFront Functions can't generate body content, but it looks like this service works by responding with a refresh meta tag. So if you change that to a Refresh header you wouldn't need to write the body.)
CloudFront functions run on the 200+ edge locations of CloudFront and, according to the docs, have sub-millisecond startup times. So might be a viable option?
You can also set Lightroom to write sidecar xmp files, which means every edited raw file will also have its own copy of the edits kept alongside it.
Coupled with using a good directory structure, that significantly lessens the impact of losing a catalog file.
I think the difference may be in the "They’re easily revoked and expired" part.
Passwords are usually one-per-resource, e.g. a user has a single password. If that password is compromised you can reset it, but all the consumers that used it will need the new credential.
Whereas tokens are typically one-per-consumer, so if one is compromised you can revoke/expire just that token, without affecting other consumers.
Same with expiry times -- you can set that on a token without it expiring all access to that resource.
Not sure if that's what the author had in mind, but it's a difference in how these things are often used (even if fundamentally they are otherwise very similar).
While this probably doesn’t completely solve your problem, have you tried using conditional includes in your .gitconfig? I’ve been using that to ensure that anything under ~/work uses my work email for user.email, but anything under ~/projects uses my personal email. It’s quite handy.
As a Scot, I find that a bit sad. We’re really not that far away!
Does that also mean you never learned about Rabbie Burns in school?
pubsub would also be misleading, given SQS does not support the pub/sub pattern. It's a queue where each message is processed once by a single consumer; it's not a pub/sub system where multiple consumers can subscribe to messages of interest.
many payroll softwares will test decently
That's certainly the impression I got from working in this field for a while. I've worked on one of the products on that list of UK payroll providers, and it has one of the most extensive test suites that I've seen. And some of my colleagues there had previously worked for its competitors, and they mentioned similarly good test coverage there.
I'm sure the quality & amount of testing varies a lot between different products, and I have to imagine there are some dreadful ones. But at the same time, I don't think having thorough test coverage for this type of product -- especially for the parts of the product that deal with monetary calculations -- is particularly unusual either.
I've been an engineering manager for a couple of years. I'm still expected to do 50% engineering and 50% people management. As the article describes, it is a struggle to do both well. I don't see this responsibility split changing in my current role. I do often wonder what it would be like to be 100% people focused, and whether or not I would miss engineering too much.
When my role first changed, I was very intimidated by doing one-on-ones. I never felt satisfied with the one-on-ones/catch-ups I had with the managers throughout my career, and I wanted to make sure I was doing a good job with that aspect of my role.
I initially did lots of research on how to do one-on-ones, but it was only after getting experience talking to people that I finally felt comfortable. I started getting some nice feedback from my lines, so I wrote some thoughts about how I like to do one-on-ones:
[link redacted]
I think good one-on-ones are very important to keep people happy and productive. I'd recommend any new engineering managers to spend time learning how to do them.
Arcivr | Senior full-stack engineer | Contract | REMOTE | https://arcivr.com/jobs
Hundreds of artists, celebrities, and teams rely on Arcivr's platform to deliver unparalleled VIP experiences. We build products to create and operate VIP events in the music and entertainment industries, from virtual meet & greets to streaming concerts.
We’re looking for a few experienced engineers to help us build and improve our recently-launched virtual event platform, Arcivr Live. We’re a small, enthusiastic team, where everyone has a significant impact on everything from technical strategy to the bottom line.
Our current tech stack is React/TypeScript, Go, PostgreSQL, AWS. We all work on all parts of the stack, although we do also specialize a little to suit our individual strengths and preferences.
Full job description: https://arcivr.com/jobs
Arcivr | Senior full-stack engineer | Contract | REMOTE | https://arcivr.com/jobs
Hundreds of artists, celebrities, and teams rely on Arcivr's platform to deliver unparalleled VIP experiences. We build products to create and operate VIP events in the music and entertainment industries.
We’re looking for a few experienced engineers to help us build and improve our newly-launched virtual event platform, Arcivr Live. We’re a small, enthusiastic team, where everyone has a significant impact on everything from technical strategy to the bottom line.
Our current tech stack is React/TypeScript, Go, PostgreSQL, AWS. We all work on all parts of the stack, although we do also specialize a little to suit our individual strengths and preferences.
Full job description: https://arcivr.com/jobs
One of the ways to apply this inverted thinking is to conduct a "pre-mortem" at the start of a project. By deliberately imagining that something has failed, and speculating about the reasons, you can sometimes uncover useful steps that prevent those imagined failures from actually happening.
I've found this can be quite useful, both for minimizing risk, and also (interestingly) as a source for new product/feature ideas.
No, it's not an alias, they are distinct types. You can't use the types interchangeably (unless you cast them).
Your playground example didn't try to pass a UserID to a function accepting a PostID, but if you do that, you'll see the error:
Visual Studio Code has a "peek" operation that does something like this. It is indeed quite handy.
https://code.visualstudio.com/docs/editor/editingevolved#_pe...
The dev experience you get with Netlify and Zeit will almost certainly never be possible with AWS.
For static hosting, AWS Amplify is already a very similar experience to Netlify. Each is slightly better than the other in some ways, but overall they are really very similar.
If you're in the UK you can report it to the ICO (Information Commissioner's Office): https://ico.org.uk/make-a-complaint/.
They have a form specifically for reporting concerns with websites' use of cookies, see https://ico.org.uk/make-a-complaint/cookies/.
That's interesting, thanks. I haven't really used Cloudflare Workers for much myself so it's interesting to hear folks' comparisons.