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.

One of the big promises of software is composability. You can build rich, powerful experiences out of basic building blocks.

APIs add new things to the toolbox. For example: Treasury, which lets an app/platform store, move, and track a business’

I've been a small business owner and can talk at length about SMB banking, and will later, but let's put on the software developer hat right now.

Lots of software talks about money, keeps records about money, does calculations about money, but can't *touch* money.

This is extremely frustrating when you're building SaaS apps for businesses, because you have total control over your UX right until your app needs to touch money... at which point all data about it lives in a silo you can't access.

So you generally push work to the operator.

For example, suppose you’re writing a business-in-a-box system for electricians, including an invoicing feature.

You need to be able to read bank transactions to reconcile. You probably can't. The owner can. So you ask the owner to do mind-numbing work a computer does better.

It sure would be great if your business customers had bank accounts you could actually introspect and operate on their behalves! You could just get the list of incoming payments and match against the invoices.

There is some software to write but it is not rocket science.

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.

My friends @robwalling and @einarvollset just launched TinySeed, an accelerator for software companies where a successful outcome is a healthy, sustainable business rather than attempting to ride the rocketship trajectory. https://t.co/LSHqZNcVid

I have some thoughts:

As somebody who bootstrapped ~4 companies, I feel like I had to make some clearly suboptimal decisions early in them for lack of what is, in hindsight, not all that much money. But there's a huge gap in the product space for investment options.

It's weird: you can get $25k from Amex trivially, and angels are very willing to write a check for that much, but you have to make representations about your goals/ambitions/market/etc which don't really apply to everyone.

And so you see the traditional angel/VC ecosystem fund companies where honestly the returns are probably not there, and this is knowable pretty early, but the chase of them will wreck what could have been a perfectly happy business.

(To make the math work for traditional VCs the company has to at least have a market-appropriate shot of $100 million a year. There are a lot more $10 million a year companies than $100 million a year companies. That is *not* a bad terminal outcome for founders/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.

This lunch is 500 yen ($4.80) at Sukiya, a Japanese fast food restaurant which belongs to a category with about three big competitors.

I love the aesthetics of this category and they’re under remarked upon.

I think people underestimate QSRs in terms of social utility, but Sukiya et al describe themselves as mission-oriented enterprises. I believe this is largely sincere, and goes back to the 60s and 70s, when the clientele was primarily manual laborers who had migrated to work.

Japan was not a rich nation at the time, and day laborers in particular were both unlikely to be able to cook for themselves and unlikely to have much of a food budget, and so the chains sprung up offering an honest-to-goodness cooked meal delivered in under a minute for cheap.

This heritage continued over the years, even after Japan became a much more wealthy nation, and these chains function as social support and dignity for folks in diminished circumstances.

They also are a wee bit of a cartel, and I appreciate the aesthetics of the cartel:

Back when I was first in Japan, in the mid 2000s, there was an increase in the price of beef.

And the heads of the three chains got together, and decided that the price of the basic beef bowl needed to increase, but given the economic circumstances how could they hold the line.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.

🚔 HUGE #Tesla SERVICE PROBLEMS THREAD🚔

You might remember my 3 prior threads on how
TESLA. TREATS. ITS. CUSTOMERS. LIKE. TRASH.

Here's the 4th installment.
@tomkeinan @jonsey_lisa @jwmooc @tchanpoker @bryanthediamond @EconomicManBlog
$TSLA $TSLAQ 1/22

Welcome to Greta's 4th edition of #Tesla customers getting used and abused. Because that's the Elon Musk way.
@coffeebreakls @KocgibiHarun @omaragha @JayGhahari
$TSLA $TSLAQ 2/22

"The best service is no service." - Elon Musk a.k.a. #SpaceKaren
@briansaziz @FarSha998899 @thinktankfour @Billoday1
#Tesla $TSLA $TSLAQ 3/22

These #Tesla customers represent just the very tip of the iceberg. They are ones who have Twitter, have decided to complain about their #TeslaServiceIssues publicly, and were found by yours truly.
@yanismydj @hajelatweets @AlanHeldman @francislongo5 $TSLA $TSLAQ 4/22

Dear #Tesla customers: In California, if your vehicle has been out of service for >30 days total, it's a lemon. You can get punitive damages and attorney's fees. Don't sit around and take Elon's abuse. @13arm13arm @cecimar12 @richardson_skip @shootinglee $TSLA $TSLAQ 5/22

Hey, who wants to read a story about @Upwork fucking over freelancers in order to upsell their clients on unnecessary services the clients don't want and can't afford? Strap in!

So after my marketing agency closed I started freelancing again. A marketing company that wanted to work with me only hires freelance writers through @Upwork. So I signed up. I wasn't thrilled about it, but that's who they contract with and it's their marketing company.

I've been receiving regular assignments from this company, thru @Upwork, for over a month now. I've written dozens of articles for them. My work has been exemplary. I've been handling repeated rush jobs and delivering. The client was and is very happy. That's coming from them.

While I was wrapping up several assignments this week I was contacted by the marketing company. They asked if I had taken a new full-time job and wasn't available anymore. It seems @Upwork's talent group told them I was no longer available to take assignments.

I was very surprised. Nothing had changed on my end. I still needed the freelance work very much. I told them so. So the marketing company pressed @Upwork and were told there were "compliance" issues that were preventing the marketing company from giving me any more work.

(1) Since some people laugh at Cardano project and it's peer review aspect, let me share a story from work for all of you
(2) There is company called Databricks and they open sourced recently a technology called: https://t.co/gpZyKKiMVD . This technology is super important

(3) In BigData delta allows one to perform DELETE and MERGE operations contrary to Hadoop + Hive where this is not possible, seeking through many partitions finding customer data to remove and then rewriting it is not only expensive as an operation but also very dangerous

(4) This promising technology is something that many companies, which have big data turn into as they need to be GDPR compliant.
(5) I was always reading and accepting all details from their website as given and the "truth"

(6) There is however an amazing Principal Developer at our company that found some of the claims from their website as dubious, e.g. ACID claims on such a distributed file system
(7) It turns out this is not the first time this company advertises something that is simply not true

(8) on another occasion this company made untrue claims about Cassandra database and this then became source of disputes e.g by dr. @martinkl - my fave expert in distributed systems
(9) All professional developers also know of course famous Jepsen tests ->

A thread about Eastshade's bike mechanic!

When I originally thought of putting a bicycling in Eastshade, I was pretty sure it wasn't going to work, for the simple fact that if it was easy, we'd see a lot more rideable bikes in games. Well, I was wrong. It took a mere week.

Its essentially a first person controller with extra momentum, resulting in the the movement direction lagging behind your look direction. Then I used the angle between the look and the movement to dictate camera "bank" and handle bar rotation, and voila! Game changing feature!

The look of the bike was harder than the movement. Bicycles are fairly modern, so it was tricky to fit it to the setting. I took some artistic liberties and settled on a penny farthing (but wooden), ignoring how impossible that would be to ride on the rugged terrain in Eastshade.

Surprisingly, the hardest part was sound. It didn't feel like riding a bike until I found the right sounds and how to trigger them. For a while I was stuck thinking too realistically. A penny farthing is fixed gear, pedaling sounds nothing like a regular modern bike.

Finally I abandoned realism and went with sounds normal people would associate with biking. We're all so used to modern bikes that we strongly associate the distinct ticking of a freewheel mechanism (think of the sound when you stop pedaling and coast on a modern bike).