cyode

+1 re the login/location gripes.

Also, I immediately thought this would violate Wikipedia's "No original research" policy, but looks like images are exempt[1].

[1] https://en.wikipedia.org/wiki/Wikipedia:No_original_research...

> Experience shows the best approach is to “just do it,” when a confluence of indicators occurs like now. Accomplishing the "buy low" objective successfully means not attempting to "buy lowest.”

Language like this really does sound like a gambler explaining their slots/roulette strategies to me.

It's been a few years since I read this (when I briefly considered switching from software engineering to management) and the one thing that stuck is the advice to "start with heart" during your crucial conversations.

Trite indeed, but it's not a bad phrase to have bouncing around in your head before you have to deliver critical feedback or resolve an interpersonal conflict. Never forget you're talking to a fellow human.

Bit off-topic: can anyone recommend resources (videos/papers/tutorials) that could help me learn how QR barcode detection and scanning itself is implemented?

I've been thinking that building a basic scanner from scratch (i.e. only using vanilla cpp/python/whatever + image processing libraries, but nothing barcode-specific) could teach me a lot.

My mind is blown. Reflecting on a lifetime of getting declined filling web forms in with a wrong CC number, billing address, expiration or CCV, I...don’t think I’ve ever misspelled my name.

Trying this out on my next purchase for sure.

What's a hood experience?

+1 exactly what I was wondering. And if it is, what’s stopping a company from defining the culture as, “It’s ok if you want to talk about this at work, and it’s also ok if you don’t want to.”

While I didn't learn anything useful from the article, TIL the idiom "old chestnut". What an excellent expression!

Nice, I love Minesweeper. By the way, the link to your blog post is incorrect in your README.

> There are many ambiguous date formats, but this is not one of them.

The comment you've replied to is a counterexample to this claim.

If you have remote teammates or may have any in the future (i.e. if your company allows remote engineers), a culture of writing things down is imperative.

Having a button to toggle on/off rounded e-notation (e.g. 1.2365479e+45) could make comparison easier as well.

Nice job with this, I learned something new today :)

They could be paired with wireless headphones distributed to attendees, similar to silent discos. You could even pipe music to the masses, along with explosion sfx synced with the drones.

Lots of comments here about what this means for CircleCI. Found it interesting that CircleCI's CEO has a testimonial in the "What our community is saying" at https://github.com/features/actions:

“CircleCI has been building a CI/CD platform since 2011, and GitHub has been a great partner. GitHub Actions is further validation that CI/CD is critical for the success of every software team. We believe that developers thrive in open, connected ecosystems, and we look forward to working with GitHub to lead the evolution of CI/CD.” Jim Rose CEO of CircleCI

Human drivers today reliably stop for jaywalkers. I imagine jaywalking rates in a total self-driving car world be about the same.

Nothing, unless they aren't interested in being and carrying out the duties of a project manager. "Soft skills" like developing team processes, improving internal documentation, and even helping other engineers on the team can make a different and valuable impact when they're coming from the engineer themself, rather than a PM or engineering manager.

Ideally, whatever criteria used for the different rungs of the engineering IC ladder should call these out as contributions that are taken into account.

When I first learned about W3W, I immediately wondered if this same process of mapping n-word tuples across a discrete space could be applied to time. Similar to GPS coordinates, Unix timestamps like 1293432531 don't communicate much to a human developer about when in history they occur. Just use 2010-12-26 22:48:51 then, right? Sure, but then my brain has to worry about timezones, DST, etc. I feel like a unique English name for each second could be useful in some cases, like 1293432531 but (easier, to, pronounce).

Of course a lot of the shortcomings about W3W would apply to to this system too (offensive phrases, lack of relation between nearby points, etc.) Anyone know of something, open source or otherwise, that exists?

Surprising to me is seeing that some of the papers cited here were published in the mid-90s. That's 5 or 10 years before when I would've guessed.

Makes me think of Ada Lovelace and how awesome the mind can be when grappling with the abstract (though I'm sure non-quantum computers were still some help here to researchers for fiddling with quantum algorithms).