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’
Lots of software talks about money, keeps records about money, does calculations about money, but can't *touch* money.
So you generally push work to the operator.
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.
There is some software to write but it is not rocket science.
But let me speculate a bit:
They can automate its operations.
We made it *better* for your users than many business bank accounts.
"When do I get my money?"
Can you imagine needing to email Google to ask when that email that you know was sent will arrive?
Why is money *so slow* and *so opaque*?
In the U.S., you’ll often be blocked on the ACH network. Fast compared to stagecoach; slow compared to email.
Stripe has an arrangement with the banks that ultimately hold the business users’ funds.
(We are working on making that even faster by default. It’s not called HTTP 200 Check Back In An Hour.)
Putting together fintech products is historically a pain in the keister.
Then your engineering team receives the spec, and the *real* fun begins.
No negotiation required. No bespoke legal work. More of the necessary levels of complexity in touching money businesses depend on; less of the overhead.
You can build all of that on Stripe APIs now.
It is managed at most banks as an offshoot of personal banking, because the userbase is basically the same people who show up at the branch.
But the needs are quite different.
(Narrator: This is not, in fact, an adequate spec for a checking account.)
So do graveyards. And hotels. And landlords. And spas. And tutors. And yoga teachers. And...
Not enough dentists pay not enough dollars for banks to put software teams against dental practice UX.
We can then take that package to leading banks. That reach is *very interesting* to them.
A pizzeria can't walk into Goldman Sachs and walk out with a bank account.
A software company serving pizzerias could if they had, uh, a lot of dough.
And so our partner banks have made great products available, at pricing and terms that small businesses just don't usually get in direct banking relationships.
I know exactly how many times I paid the $14 account maintenance fee for my software businesses, ten years later. That’s how much I hated them.
One way to think of it is that banks have huge expenses to attract SMB deposits, including marketing campaigns and branch networks, and those drive the pricing of SMB banking.
Nationwide advertising, branches, and sales reps aren’t as cheap as cron jobs.
I'm very excited to see what software people do with the Stripe Treasury.
No. This was my number two. You're welcome to your guess at the number one. (Though, who knows, I heard of a new project last week and might steal the zeroth spot for it.)
Part of the needle threading is making sure that one is still developing some things which are uniquely exciting to developers and smaller shops.— Patrick McKenzie (@patio11) September 23, 2020
Which: I can\u2019t spoil it, but one thing in the pipeline is maybe my favorite Stripe product since Stripe Atlas if we do it right.
More from Patrick McKenzie
Here's how I'd measure the health of any tech company:— Jeff Atwood (@codinghorror) October 25, 2018
How long, as measured from the inception of idea to the modified software arriving in the user's hands, does it take to roll out a *1 word copy change* in your primary product?
How long does it take, measured from initial expression of interest through offer of employment signed, for a typical candidate cold inbounding to the company?
What is the *theoretical minimum* for *any* candidate?
How long does it take, as a developer newly hired at the company:
* To get a fully credentialed machine issued to you
* To get a fully functional development environment on that machine which could push code to production immediately
* To solo ship one material quanta of work
How long does it take, from first idea floated to "It's on the Internet", to create a piece of marketing collateral.
(For bonus points: break down by ambitiousness / form factor.)
How many people have to say yes to do something which is clearly worth doing which costs $5,000 / $15,000 / $250,000 and has never been done before.
For candidates: evaluate prospective employers accordingly.
For startups employing e.g. engineers: given that your candidates should evaluate you accordingly, be *extra special* careful to operate like professionals with regards to e.g. interviewing, offers, and negotiation.
"Can you be more explicit about 'abusive' here?"
Not without violating a confidence, but as someone who has been on hiring side of table and is a capitalist, there are *clearly* things you could do which would be "sharp operating, but we're all sharp operators" in some contexts.
Hiring employees is often not one of those contexts. The nature of the relationship, the asymmetry in power, and the social contract strongly counsel you to be a lot better there than you are minimally required by law / contract.
A thing which aesthetically frustrates me is that a lot of the things I've heard companies do here serve *no legitimate business purpose.* In some cases it's getting tens of dollars of advantage. TENS! On an engineering candidate!
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.)
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).
“Why do people care about stablecoins then?”
A mix of “they encourage dollar-denominated liquidity in the cryptocurrency ecosystem and discourage withdrawal of the same” and “they’re good for money laundering.”
“But they make value transfer between exchanges much faster!”
This was a solved problem in traditional finance, too, mostly through the extension of credit. (It doesn’t matter how long settlement takes if there is sufficient trust to enable credit.)
The Bitcoin ecosystem is *positively allergic* to credit, so you have to call it a coin for them to accept it. And after you call it a coin they ignore everything the world has learned about credit, like risk management.
“Stablecoins aren’t credit!”
They’re pretty much exactly credit? A tether is a zero-coupon Bitfinex bond with a non-functioning call option. I
More from Software
Firstly, I made use of the auto-rigging feature in Mixamo to give my character a skeleton. This allows you to use the Mixamo animations for the character in Unreal Engine.
In the Animation Blueprint, I tried to add a punching state to the character. The problem I faced initially was that the character glides while punching. This occurs because multiple states of the animation are active (as their transition conditions are satisfied).
There are a couple of solutions for this:
👉Blending the punch and idle states (character can punch while running) by using the Layered Blend Per Bone node.
👉Disabling input while the punch occurs.
I didn’t like the outcome when I blended the animations. as the hip rotates more than we’d like it to. This leads to the character punching upwards and to the left. This isn’t favorable as the enemy is usually straight ahead. Disabling the input worked way better!
DEAD PEOPLE SCORED FOR BUFFALO!
A truck delivered off a suitcase full of points at halftime from Canada for Buffalo.
I’ll be submitting sworn affidavits from Steelers fans than they saw the Buffalo rigging the game but I want to emphasize that I’m not under oath.
There are multiple security vulnerabilities associated with the various versions of JIRA software which are exploited in wild and is one of my personal favourite 3rd Party apps to hunt.
1. CVE-2020-14179 (Information Disclosure)
a. Navigate to
b. It leaks information about custom fields, custom SLA, etc.
2. CVE-2020-14181 (User Enumeration)
a. Navigate to
3. CVE-2020-14178 (Project Key Enumeration)
a. Navigate to
b. Observe the error message on valid vs. invalid project key. Apart from the Enumeration, you can often get unauthenticated access to the project if the protections are not in place.
4. CVE-2019-3402 (XSS)
a. Navigate to
5. CVE-2019-11581 (SSTI)
a. Navigate to
6. CVE-2019-3396 (Path Traversal)
7. CVE-2019-8451 (SSRF)
a. Navigate to
8. CVE-2019-8451 (SSRF)
a. Navigate to
STEP 1. Create a head
create a triangle and rotate it so that it looks like a head
STEP 2. Create smile and ear
We have a pseudo elements in CSS, so we can create smile and ear using head::after and head::before
STEP 3. Create eyes
This is the most trickiest part because in order to make an eye we have to create
- One bigger white circle
- then a small black pupil inside white circle
- then a small white reflection in black pupil
Let's create a outer white circle first
STEP 3(I). Create a black pupil
We can create pupil using pseudo element
You May Also Like
For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.
The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.
This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.
"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.
Rules of thumb that simplify decisions.
• If unsure what action to take, let your 80-year-old self make it.
• If unsure who to work with, pick the person that has the best chances of breaking you out of a 3rd world prison.
• If procrastinating on an item, you only have 2 options:
1. Make the pain of not doing it greater than the pain of doing it.
2. Make the pleasure of doing it greater than the pleasure of not doing it.
• If stuck with 2 equal options, pick the one that feels like it will produce the most luck later down the line.
I used this razor to go for drinks with a stranger rather than watch Netflix.
In hindsight, it was the highest ROI decision I've ever made.
• If someone brags about their success or happiness, assume it’s half what they claim.
• If someone downplays their success or happiness, assume it’s double what they claim.
The map is not the terrain.
There are three factors that suggest that the recent stability could evaporate and that equities are "about to enter a sustained bear market", Oppenheimer says.
First is the fact that growth, inflation and interest rate outlook is unfriendly for equities.
Second is that greater volatility, such as multiple corrections and new peaks (which we've seen in 2018) tend to presage a full bear market.
Here is Goldman's data showing how falls and bounces tend to come ahead of "the dramatic final fall".