I’m poking around while on an airplane, so the network speed is pretty slow. The site crawls to a stop with each character I type into the search box. As a performance booster, perhaps consider adding a short delay before firing off queries to update the results or decoupling the the search box from the query result?
Crazy idea: provide a search box, and when the user hits "enter", POST the data to the backend, which queries the database, and then returns the relevant results.
It's possible to make autosuggest performant on poor Internet connections, it just needs a little more thought put into optimizing for it:
1. Debounce!
2. Use WebSockets to minimize unnecessary round trips
3. Cache previous results and use them when the input is a superstring of a previous input (e.g. results for "Android mobile dev" will always be a subset of the results for "mobile dev")
They ask it where the next eclipse is, and where best to watch it. They got the date right, but the suggested locations of Timor and Australia are not in the eclipse path. https://www.timeanddate.com/eclipse/solar/2024-april-8
That also doesn't look like enough almonds for 15 grams worth of protein. 10 almonds have approx 3g of protein, requiring 50 almonds for 15 grams of protein, I don't think there's that many in the video.
Makes you wonder about the veracity of the AI (or the accuracy of the demo). Looks like a cool product either way.
Related to this quote, I don’t think we’re guaranteed access to better content. I think we’re guaranteed to more prolific cheap to produce content. Think Instagram era relative to Flickr era. Less about the art, more about fast fashion, or fast art, to capture your ever more brief attention. Certainly the next chapter of Tim Wu’s book, The Attention Merchants.
You need to keep your head on a swivel walking around Hoboken. My son got hit in his stroller in a well marked crosswalk by someone improperly passing a car that had stopped for us; I couldn’t even see it coming. Luckily he was not injured but it was extremely close to severe injury or death.
The last paragraph rings absolutely true for me. Me and my wife stagger walking in the street now, or I walk out first and the pull the stroller behind me if I’m alone.
I do commend them for making safety improvements, it is clear there’s been investment in pedestrian safety … but stay vigilant.
Directors and/or VPs of the various service organizations. It’s not a matter of it being a technical problem. It’s a business problem. The reported status has business consequences.
Well now you have to tell us why and how 600 people are sharing a repo! That’s a lot. Granted at Microsoft thousands of people worked in the same codebase. But in my recent experience we’ve generally been working on a repo per project, which typically maps to a small team.
> Well now you have to tell us why and how 600 people are sharing a repo
Any answer you could possibly get from this question will eventually boil down to project repos vs monorepo. There are pros and cons to each, which are more or less meaningless depending on the amount of developers working in parallel.
I figured as much, and just wondered about the challenges of trunk based development with a large contributor pool. If so many teams are working in different subtrees of the monorepo, it seems like trunk based development could be just fine.
It’s a train of people up Si with a slammed parking lot… I think that’s the point. It is difficult, but it is also highly pedestrian as far as trails go in WA. We are lucky to have such high standards here where even the most accessible and trafficked trails are incredible
