You don’t get that back unless you somehow fire everyone so you can offset income and expenses without more amortization.
2,535 karma · joined March 31, 2010
You don’t get that back unless you somehow fire everyone so you can offset income and expenses without more amortization.
This change taxes you on profit you never made, and specifically targets software companies.
It’s insane.
If they don’t fix it a lot of companies (and their owners) are going to go bankrupt.
Office Manager: 100% expense.
Software Engineer: 20% over 5 years (actually only 10% for the first year).
If they’re international then 6.67% over 15 years.
Not only that, but the effect “stacks” over the years.
So year 1:
1,000,000
- 100,000
————————-
900,000 Profit
Year 2:
1,000,000
- 200,000
- 200,000
- 100,000
————————-
500,000 Profit
Year 3:
1,000,000
- 200,000
- 200,000
- 200,000
————————-
400,000 Profit
Year 4:
1,000,000
- 200,000
- 200,000
- 200,000
- 200,000
————————-
200,000 Profit
Year 5+:
1,000,000
- 200,000
- 200,000
- 200,000
- 200,000
- 200,000
————————-
0 Profit
By the time you get to year 5, you’ve paid tax on $2,000,000 of phantom profits you never had.If you’re a C Corp that’s $420,000 in extra federal taxes (plus whatever state tax).
If you’re a smaller company you’re probably a S Corp and federal and state tax could be ~50% passed through to your personal return.
How any owner survives that, I’m not sure.
Don’t waste your time “negotiating”.
I wonder how much they spend on multi-AZ redundant architectures...
If I was picking today I'd move to New Zealand.
Optimize your life for happiness instead of money.
I always laugh when Americans say eyeRaq or eyeRan.
But apparently this incorrect pronunciation goes all the way back to 1943. Wild.
I think Sen Gillibrand has a bill to address this called the STOCKS Act which she introduces every Congress but it never goes anywhere.
Unsure what the point is here.
And there are plenty of workloads which are easily parallelizable across cores. Like compiling things. Or just running multiple programs at once.
Which you can see by typing “ps”.
The people writing the code, the people designing the cars, the people allowing the testing, etc etc.
What we're seeing in these videos is basically unusable and will never be cleared to drive by itself on real roads.
It's just the "the last 10% takes 90% of the time" adage but applied to a situation where you can kill the occupant of the car and/or the people outside it. And that last 10% will never be good enough in a general way.
I personally know a CEO who moved to SV, was worth something like $100m+, and the bank wouldn't give him a home loan because he didn't have the right credit score yet.
He was literally building his credit with an Amex using their global transfer system.
On the other hand, FICO scores are so easy to game that once you get a couple of cards going, you can leverage those to get more cards, etc, etc and optimise your score that way.
But maybe things got loosened up a little bit lately, pre-Delta, plus we don't know where Urs has citizenship.
Asking for a friend, who's me, also trying to move to NZ. :)
The funny thing was that it starts sending you random notifications from people you don’t even follow or have the bell on for as a dark pattern to get you to come back.
What I realized is — like how I quit reading the news many years ago — everything on Twitter is pointless and ephemeral.
From one outrage cycle to the next, never relenting. Everyone always mad about some meaningless minutiae. If it was actually important it would surface by some other means so I never missed anything.
Then I’d go outside and everyone’s living their lives like Twitter doesn’t exist.
It’s easier to do than you think. Lock your account, turn off notifications for the whole app, and do literally anything else.
Fun.
You can also see which credit card issuers run an inquiry on The Work Number if you pull your file, but you don’t get any sort of notification and there’s no way to monitor it.
I just don't see how something like this actually works in a way where you can reason about transaction ordering without global serialisation of requests against the writable database, which I presume isn't happening behind the scenes?
Basically, this would seem to work great if every request did INSERTs only and you based no logic to run INSERTs on anything you SELECT'ed from the read only replicas.
But you could have situations where, e.g., you DELETE or UPDATE something in a request to one region, and it goes to replay that against the writable region, and in "replay gap" another request modifies the same rows or objects, and based on various factors such as latency etc, a DELETE ... WHERE or UPDATE ... WHERE clause might no longer hold. Or you UPDATE the wrong objects, or DELETE the wrong data, etc.
I did read the post, but I guess I need to re-read it. I have written a globally distributed database before so I'm always intrigued by how these work. :)
I don't really see how a transaction that performs reads and writes can be replayed like this with any sort of guarantee about anything, though.
And there's no opportunity to build any sort of conflict resolution in there because the replay is automatic.
Maybe I missed something though?
Why are you moving on from the first round when you don't have all the absentee votes (~120k outstanding votes) counted yet?
I get that it's their first time running RCV and all, but this is basically a non-issue when SF runs elections.