It’s underremarked upon that stablecoins accomplish basically all of the original design goals for Bitcoin qua a transactional mechanism (instant free value transfer anywhere), but that nobody cares about this because nobody ever cared about that part of the pitch.

Some people really benefit from hearing advice that everyone knows, for the same reason we keep schools open despite every subject in them having been taught before.

In that spirit, here's some quick Things Many People Find Too Obvious To Have Told You Already.

Your idea is not valuable, at all. All value is in the execution. You think you are an exception; you are not. You should not insist on an NDA to talk about it; nobody serious will engage in contract review over an idea, and this will mark you as clueless.

Technologists tend to severely underestimate the difficulty and expense of creating software, especially at companies which do not have fully staffed industry leading engineering teams ("because software is so easy there, amirite guys?")

Charge more. Charge more still. Go on.

The press is a lossy and biased compression of events in the actual world, and is singularly consumed with its own rituals, status games, and incentives. The news necessarily fails to capture almost everything which happened yesterday. What it says is important usually isn't.

Companies find it incredibly hard to reliably staff positions with hard-working generalists who operate autonomously and have high risk tolerances. This is not the modal employee, including at places which are justifiably proud of the skill/diligence/etc of their employees.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

Bitfinex files discovery in "Yo bro, where did our $800 million go?" action and it is every bit as interesting as you'd expect it to

Here's their CFO describing their agreement (which we know from other litigation was never contractualized because, presumably because money launderers hate paper trails):

Bitfinex's CFO was shocked, shocked to learn that the money launderer they engaged to provide money laundering services while I-swear-to-God-this-is-an-actual-quote "we learned to bank like criminals" may have from time to time lied to banks.

"Institutional constraints" means, here, "We were attempting to avoid velocity checks placed by our banking partners to detect fraud and money laundering, which would have detected our fraud and money laundering."

Money at the speed of code, yadda yadda yadda, the Bitcoin economy is surprisingly blasé when several hundred million dollars is in an interstitial state for months.

In a situation never before encountered by a financial institution: the check was not, in fact, in the mail.

The payments wars in Japan are heating up and one of the battlegrounds is convenience store coffee.

“Coffee? What does that have to do with payments?” I’m glad you asked.

Convenience stores are low net margin businesses, which sell some high gross margin goods/services but a lot of low ones, and have high fixed costs and a low ticket size. The typical transaction is under 500 yen ($5) and many are about $1.

They need repeat custom.

A few years ago, all of the chains had a good idea for increasing frequency of use: make a minor capital investment in automatic coffee machines. Sell access to them for the price of a cup / ice; customers self-serve with the machine.

The price point is $1 to about $2.

Coffee quickly became one of the most frequently repurchased items at convenience stores, in no small part because it’s the one thing they can sell which is phameceutically habit forming but totally unregulated. (Just telling it like it is.)

But the coffee is not very defensible

The problem, such that it is, is that competing chains are everywhere and *all* of them serve Thoroughly Adequate Coffee at similar prices, so you’re back into the brutal economics of “Who is 3 meters closer to 40 customers at 1 office?”

Enter payment apps.

So, I want to talk about how sexual harassment and fair pay are linked at Google (and beyond), because I think that's an angle that isn't being highlighted enough in the coverage of these walk-outs. I'm going to frame it largely around my personal experience there. Thread.

When I was sexually harassed by the director of the area I was working in, I was afraid to report it because I was worried that "getting him in trouble" would result in the subtle retaliation of missed leadership opportunities.

I wanted to continue working on the team I was on, because I'd gained a lot of very deep knowledge and expertise in that area, as well as reputation and camaraderie with the other folks working in that area. I didn't want to make the situation more "difficult."

To get promoted at Google, several need to happen: 1. you need opportunities for ownership and leadership above your current level (basically, opportunities to show you're working at the next level you're trying to get promoted to). The work you're "assigned" has a big impact.

2. You need glowing reviews from peers, *at or particularly above the level you're hoping to get promoted to.* Basically, you need people a lot more senior than you to say you're doing awesome work.

Mark Zuckerberg on NYT story: "To suggest we weren't interested in knowing the truth or wanted to hide what we knew or wanted to prevent investigations is simply untrue."

Facebook says it will take a couple of questions on the article but wants to focus on (looks at notes) its transparency report.

Good luck with that folks.

Now Mark Zuckerberg is running through all the tactics it's deploying to clean up the platform (you know like they should have years ago).

What every Facebook user should be reading in the

Please please please take your cyber security seriously even if you don’t consider yourself a high risk person. Here are a few easy things to start with. 1/n

Switch from WhatsApp to Signal and enable disappearing messages. Most of us cannot stop using WhatsApp entirely but at least turn off back ups to Google Drive or iCloud. 2/n

Do not have private conversations using the messaging service on any social media platform like Facebook, Instagram or Twitter. 3/n

Switch from Gmail to ProtonMail or any other secure email service provider. 4/n


Switch from Google Docs to CryptPad or RiseUp Pad.

When you complain about an open source project's management you'll get the reply, "Use something else if you don't like it!" That'd be true except for the tiny problem that *many* projects also strive for complete monopolistic dominance.

Let me tell you about Java in early 2k:

I was programming in Java since it's release, and all through the late 90s into the early 2000s. At first Java was very determined to unseat C++ and it used various propaganda tactics to turn C++ and malloc into a weird enemy for all of us to hate. This worked great!

Everything was fine though because there were plenty of jobs in tech because of the dot-com boom, and then suddenly there were not jobs because of the dot-com bomb.

Overnight it seemed as if the *only* way to get a job was at giant companies, and they *loved* Enterprise Java.

Now, this is the golden ticket for many open source projects and corporations. They all want to be the top dog #1 in the industry for their particular use, and once they gain that position they become abusive by ignoring user needs and extracting wealth from them.

With Java the dominance was so insane that *every* language had to copy Java's weirdness to survive. If you wonder why a language has some odd CamelCase things it's because early Python, Ruby, and others had to copy Java's semantics and style to even be considered "serious".