jtchang

> we broke up 2 months ago

Let's talk how that actually works in a business sense. Did you leave the company? Relinquish all control? Did you boot the cofounder out or did you buy out their portion?

What type of arrangement is this? Partnership? LLC? How did you register the entity?

"Broke up" doesn't really say anything.

Assuming you were in a partnership and you both have authority to make decisions on behalf of the company then you are free to just pay the contractors. So is your cofounder. Unless your governance documents indicate otherwise this is 100% valid.

Don't underestimate lobbying costs in dense urban areas. Whenever you have to deal with people the alternative is often easier.

If you have source mapping you can do basically what C compilers perform which is symbol mapping. If you are trying to map the HTML content to source you have to "tag" each of the steps in the process so you can figure out where the content came from.

Instead of transferring the cluster can you transfer the application(s)?

This is a very clever move by Microsoft. In essence they are painting a giant bullseye on their back to any lawsuits that may arise. The idea being that they have the resources to challenge them (they aren't wrong).

The way AI is going I'm sure we'll see some landmark cases very soon. It is very much in Microsoft's interest to grow this market as fast as possible and be at the center of it. This removes one of the key impediments to adopting generated code for smaller orgs: "Will I get sued if this product generates code that is copyrighted?".

Does Discord charge or have some type of contractual agreement with you? It does seem odd -- they must have some checking on addresses and personal information and what you posted just happens to match that regex.

> Although we use Typescript to mitigate these types of bugs, when we're working with external systems, it's easy to find yourself in a situation where the types are lying to you.

What does this mean? If you use typescript doesn't it prevent these types of bugs?

The ramifications of the inflection point we are currently at is mind boggling. I had a hard time explaining this last night but we may very well be witnessing the beginnings of a technological transformation era much like when the p-n junction was invented. From the 1940s standpoint it would be hard to envision all we had today.

- Lossless transport of energy - Batteries that don't take any time to recharge - Faster CPUs. Much faster with no heat to burn your lap.

Can I have my flying car now?

There is some really good advice here. I've been on both sides of this: pricing new enterprise service as well as negotiating them.

$49 per seat. Is that per month or per year?

Concretely look at the market and the value you are providing. Split up the user count to occasional users and permanent ones.

From the other side of the table I am expecting some type of volume discount because I am not spending 250k a year if the tech is not core to my business. I'd expect discounts for multi-year deals. You need to come in at a price point that makes sense to them depending on the market.

For cases like this email is not enough. You need to do trial shutdowns where you disable access to the db unless someone acknowledges via web. Do it for maybe 24 hours so you know you catch everyone.

What problem specifically is the away team solving? It sounds like DLL dependency hell except at a higher scope.

The fact you can cancel online is a good thing though. Some places have you send an email which is terrible. Honestly a unified API endpoint for all this would be a godsend.

These are fantastic!

Why don't I hear about these incidents with AWS? Is it just less common or different business takes on quotas and rate limits?

> disincentivizes the desperate from becoming innovative

People who are desperate are generally quite incentivized. They want to get out of their current situation. Being innovative does not require someone to be desperate.

Only circumstance? How about when people are looking to live a basic human existence but are unable to find a job?

One thing you should get out of your head is that there is zero risk. Even keeping it all in cash in a checking account has risk.

CD ladder isn't a bad choice. A treasury bill ladder could also work and might actually fit as well. The risk is in a rising interest rate environment the t-bills you buy now will be worth less in the future. You'll still get the dollars in absolute terms but it might buy less. Too bad you can't buy I-bonds past 10k a year.

Also the biggest risk in your plan is the "leave alone and not manage". There is manage a little, manage a lot, or pay someone to manage it for me. Leaving it alone and not managing it has its own risks.

I wonder what game this was for.

To me this is validation that going the SQL route in almost 99% of new apps is the right way to go. It will be a rare case that you won't be able to scale out given how mature some of these technologies are.

I can't believe I am alive to witness this.

I can imagine 100 years from now a SpaceX plaque will be in some museum timeline with this very event being one of many "failures". It's so hard to put that into perspective when you are actually living these events. I think partly because society has been conditioned to expect success out of all things when in reality true technological progress is rarely a straight line.

Wow -- something I didn't know I wanted but actually not too bad an idea. At least it is a starting point for conversation. Have to keep in mind that not everyone understands the technical lingo associated with shopping for broadband so it makes sense.

At its core the business fundamentals aren't great. However 130MM in revenue annually could mean there is something there.

I agree the number one thing to figure out is strategy. 24 to 36 months is a non starter in this environment. The company will die before you manage to pivot.

Figure out how to make the company sustainable and pitch that vision.

What state?

How many bits are in a gameboy rom? How do you even take a picture of a rom?

I see. But still after the initial TLS handshake. So clients can still connect over and over and force your server to do TLS handshakes all day long.

How does one force exponential backoff of clients without taking in any load on themselves?

Is it some sort of TCP window congestion control futzing? But even that wouldn't work since the client can do whatever the heck it wants.

It's like a NOP slide for viruses: https://en.wikipedia.org/wiki/NOP_slide

Just kidding...sort of!

If you hold a large amount of bitcoin your threat model should be way above the average person. It sounds like his infrastructure was specifically targeted. It can be very difficult to protect against targeted attacks from adversaries.

Many of us are well aware of how difficult some of the prerequisite CS classes can be so he definitely has my respect.

The canonical answer for the first problem by the AP board seems kinda bad stylistically. It encourages the use of a deep nesting structure which doesn't seem to make sense.

It's like a positive loop where we are learning how to train the AI to learn. This is getting scary.

> For stable funding, what you really need is retail deposits

I would disagree. For stable funding what you need is the belief that the underlying currency will continue to have value. The fact that BTC hasn't gone to zero means there are some people who still believe it has value.