jcoder

I can’t tell if you mean they included `.DS_Store` in their ignore file or left it out, but including it is just good practice.

What sort of solution would you suggest

Those are all sites with 1000s of engineers, real-world use, and actual evolutionary pressure driving their features. You want to compare to essentially static sites with some light user statefulness.

  I hand-rolled my own authentication on this site. But I had a good reason! Remember all the talk above about making things super fast by collocating the node servers and databases close to users? Well, I'd kinda undo all that work if I used an authentication service.

This is a great example of how fundamental architecture decisions limit your subsequent decisions, and it’s your job as a designer to make sure that the final result makes sense and reflects good tradeoffs, not just the state as you go. Hand-rolling auth (a real risk) so you can use this unnecessary distributed deployment scheme (no real value) is a bad decision.

  Currently I do not fail the build if the E2E tests fail. So far, I haven't been worried about deploying something that's broken and I didn't want to hold up a deploy because I accidentally busted something for the 0 users who expect things to be working.

I’m having trouble forming the words for how I feel about an apparently influential author promoting the sort of Rube Goldbergesque overcomplection in the rest of the article, while downplaying the single piece of value this CI pipeline could be delivering.

That “distributed” quality itself is a choice that introduces complexity. There are many sites that deliver the same or greater level of value to users, and use a “boring” architecture and deployment.

To be fair, the about page says who made it https://browser.kagi.com/faq.html#about

Reading this I was thinking I would wake up tomorrow and go back to using `docker-machine` and a separate VM for development on my work mac. Interesting timing that they started the work to deprecate/remove `docker-machine` three weeks ago: https://github.com/docker/roadmap/issues/245

Unfortunately, it looks like work is also underway to deprecate and remove `docker-machine`: https://github.com/docker/roadmap/issues/245

Totally, it’s a great solution. Using the env var is nice for the case where you only need to vary the email. Especially nice if you have multiple orgs to commit under, but the rest of your config is just how you like it for all projects.

This is cool. In this specific case, you can also (1) not set the email in .gitconfig, and (2) set an environment variable `EMAIL`. Git will pick it right up.

I use direnv for this.

Isn’t this a bit like saying Ruby collides with a gem, python with a snake, or Java with an island?

I honestly can’t tell which model you’re arguing in favor of.

A lot of people are trying to solve for etching and engraving here, but if I wanted to personalize a glass piece that already (kind of, in some world) looks like it belongs in a lab, I think I’d try an enamel paint process instead.

May have a nicer result than a label maker, depending on taste.

The downvotes might be because you responded to a request for more detail with:

> I don't think I need to explain what those are...

Why don't you humor us and give some examples anyways?

I feel like the author's prose right underneath that heading explains it really well:

  If you silo yourself to only learning within your company, you are missing out on a world of experiences and expertise different than yours from the external community. Technical leaders realize this and place importance on learning from the larger world of computing than just their solo.

New ideas get introduced to orgs in many ways. In my experience, it's primarily through hiring new people, but making it an expectation of distinguished eng is clever, because you can also expect them to practice and apply discernment.

The non-bt version does this too

I fly into and out of PDX regularly, and there's no scanner that you have to gaze into. Parent is talking about cameras at a high angle in a hallway—no one is there to make you look up. Are you talking about the millimeter-wave scan in security? Your eyes can be closed while doing it—no one complains.

And you can kill that under "restrictions" if you want to...

Because that's the right way to leverage social media: Meet your audience in the places they exist, so they can use and share your content, natively. They also posted this to Twitter, and perhaps other platforms.

Considering the ambiguity of "Sold Out", maybe the original headline, "Amazon Sells Out of Echo Speakers in Midst of Holiday Rush", would be better?

I do integrate every so often. By fetching master and rebasing on it ;)

Rebasing isn't just about a clean project history, IMO. I'd much rather find out about a merge conflict I've created when applying a small commit to the tip of master, than when smashing two development histories together.

There's no reason you couldn't rebase your feature branch work atop the commit it shares with the master branch, and push it. You would not be rewriting anything that the remote knows about.

Another option you might consider, if you need more flexibility, is doing your work in a branch off of your `feature-branch`, e.g., `feature-branch-wip`. When you're happy with your progress on `feature-branch-wip`, interactively rebase atop `feature-branch`, merge in, and push. Their process is satisfied, and they'll never be the wiser.

Did they ever start using HTTPS? When I tried it a while back, it was HTTP-only.

Two months ago I received an itinerary, directly from the airline, that made two connections before reaching the final destination. At each connection, my arrival was scheduled to land 30-60 minutes after the connecting departure. I'm not concerned at all about the airlines becoming an omnipotent big brother.

Absolutely right, my upvote FWIW.

Neat. Any reason not to use 0️⃣1️⃣2️⃣3️⃣4️⃣5️⃣6️⃣7️⃣8️⃣9️⃣?

Ah, thank you. Still wrapping my head around the new architecture.

So, the bar for contributing to the wiki has been raised from "has access to a computer" to "has access, knowledge, and resources to run a wiki server"? I hope one or more WaaS (wiki as a service) providers will emerge where a user account == a fed wiki node.