Strava (a running tracking app) provides two helpful controls you can set as your default:
1. “Hide the start and end points of activities that start at SPECIFIC addresses.”
2. “Hide start and end no matter where they happen.”
Then it can be useful to add your home/work/routine locations.
If iNaturalist doesn’t have a setting like that, it’s a nice approach — especially if it’s included as part of initial onboarding flow — so it helps people without needing to remember to make visibility choices each time.
> Treating it like a stop sign also doesn't work very well when there are huge amounts of pedestrians. As a pedestrian that yesterday meant I got the right of way all the time. For cars it was mayhem downtown.
I’ve long been curious if people in S.F. who are used to Waymo “behavior” – including myself – behave differently when a Waymo is involved. For the most part, Waymos are extremely predictable and if you’re on the road as a pedestrian, cyclist, or car, are you more aggressive and willing to assert your turn in the road? Curious if Waymo has done a psychological study of how we start to think about the vehicles. I know many runners, for example, that’ll stride right into the crosswalk in front of a Waymo but wouldn’t dare to do that in front of other cars. Similarly, anecdotally people treat public transit vehicles differently than a civilian car: folks are more willing to let them drive even if out of natural turn.
Prior to reading the article, I assumed Waymos were stuck due to an Internet connectivity issue. However, while the root cause is not explicitly stated, it sounds like the Waymos are “confused” by traffic lights being out.
While reading through https://news.ycombinator.com/item?id=23729160, discussions around Signed Exchanges came up. This is a really neat idea (that’s been around for a while); however, a lot of it depends on the user experience in the browser. Users cannot be expected to know the technical details to get (or understand) the benefits—and we must be wary of some major drawbacks like the cache site seeing the traffic instead the origin.
I’d second this. In fact, I think the README should be the first thing (potentially in collapsible form so you can easily see the file list without scrolling too much).
Intuitively, I’d bet most people landing on the front page of a repo are consumers of the library looking for a README with info on how to get started or where to look for information on how to get started. Again, this is only intuition—no data to back it up. Project maintainers are most likely interacting with the issues and PR sections or code on the command line.
Life happens! With all the disruption and WFHing related to COVID, it's important to remember to back up your workstation even if you're not in the office!
> You are right, but talking about whether to use k8s or not would make the article 2-3x longer. It is a totally different topic.
Sorry—my comment was written poorly. I think the article is good as is and agree k8s or not is a different topic. My comment intended to be a reminder for all of us reading it that we should ask more questions before choosing a technology.
I’ve found a trend in engineering (including with myself), we sometimes forget to take a step back and see the forest.
This was my thought exactly. The article is great assuming you need to use k8s, but does leave out the important question: does your project or product require k8s and all the overhead it unavoidably entails?
Amazon's Elastic Container Service (ECS) on Fargate deployment type is probably a better option much of the time. Until you maintain your own k8s cluster (including the hosted variants on AWS, GCP, etc.) you might not realize how complex configuring k8s is.
While the AWS's ECS service may be more limited, I've found it leaves less room to do the wrong thing. Unfortunately, the documentation on ECS and the community support is inferior to k8s, but I'll accept that if I don't have to spend a whole day researching what service mesh to use with k8s and how to configure a load balancer and SSL certs.
If you're looking for some alternatives to play around with, I'd also suggest TypeScript (w/ React) or Elm (https://elm-lang.org/). If you like Haskell—and can work fluently in it—Elm is a joy!
A frontend does not require JavaScript. I've made quite a few useful MVPs and internal tools whose frontend solely consists of dynamically generated HTML pages served via a Python Flask server with Jinja for templating or a Go server with its native template/html package for templating.
If you want to polish the UI a bit consider throwing in some simple CSS—either handrolled or prebuilt with Bootstrap or Semantic UI.
This reply assumes the project serves the UI over the web. For applications that are not hosted apps, I've had CLI tools just spin up a local server with the UI for a quick proof of concept UI.
I'd recommend trying a virtual board game hour (or two)!
My coworkers and I have played Carcassonne a few times on https://boardgamearena.com/. While playing the game, we have a group video call going to keep it social. (If you use this site, I'd recommend playing a few rounds by yourself to get accustomed to the UX which can be a bit cumbersome at the start. When you do it with your coworkers you can help explain some of the nuances in the site itself. The game has a 7 minute video explainer that does a great job explaining the rules of the game.)
Carcassonne can handle at most five people. For larger groups, a virtual game of Codenames can be fun: https://codenames.plus/.
If you're looking for an alternate read to a math paper, checkout the NYTimes article titled "To Divide the Rent, Start With a Triangle"[1] or the online implementation of the algorithm[2].
Anyway, my point is that centralisation isn't bad if it's painless to decentralise again.
I'd love to see GitHub (and GitLab) offer a custom domain name option which would proxy HTTPS and SSH clones via a company's custom domain (e.g. code.example.com) to GitHub's hosting. That way, if a company needs to move away from GitHub (or GitHub goes away), developer's references to some company's code is not stuck pointing to some stale github.com domain.
Hosting such a proxy (and the repos) takes infrastructure, time, and experience to secure and make available, so from a user's perspective it's great if a company does this as a service as long as you provide the domain.
1. “Hide the start and end points of activities that start at SPECIFIC addresses.” 2. “Hide start and end no matter where they happen.”
Then it can be useful to add your home/work/routine locations.
If iNaturalist doesn’t have a setting like that, it’s a nice approach — especially if it’s included as part of initial onboarding flow — so it helps people without needing to remember to make visibility choices each time.