7,092 karma · joined May 6, 2019
Scalpers are the problem that you have to accept. At the time of purchase, there's no way to tell the difference between a legit purchaser and a scalper or even someone who bought it and simply can't go and needs to resell.
IDs, ticket limiters, CCs, etc, etc. All methods can be circumvented by someone dedicated enough. You can only make it "not scalable" but the tickets still need to be transferable, securely.
Unless we're willing to go ID checking at the gate, there's not going to be a true solution.
So instead of controlling flags from a website, you get the benefits of git merge, PR's, reviews, documentation etc without having to rebuild it.
I like the concept since it brings accountability. But it's just a need that larger orgs have, but by that point have likely internally built a flag system and so transitioning is difficult.
This is addressed in the article:
> This is a relatively compact engine, which would be suitable for a final kick stage of an orbital rocket.
It has lots of real world application, just not currently as part of a lift stage since you're right it's a pressure based one as opposed to a pumped engine.
I think this argues the opposite of what you think it does.
Monitoring != driving and if you had humans pesudo driving, the experience would be insanely bad cuz the human would be interjecting way too much.
This adds a lot of cold start overhead? Instead of directly invoking a handler.
Yes, but this comes with the assumption that Sam writes and reviews the website copy, PR statements and S1 form submissions, which any organization of significant size, the CEO does not.
I could believe Elon does though.
Granted it was 2013, don't sweat yourself.
The code reads correct, compiles just fine, and it runs! No clear error to hone in on.
These are some of the most difficult bugs with the "omg that's so dumb" response out the otherside. When everything appears correct, stepping through the data can take a long time because we know something is wrong but don't know which layer it's at.
To me, this fundamentally isn't cynicism - it's burnout. Perhaps one could argue, cynicism is burnout on a longer time scale.
If you call someone a cynic, most won't really understand; mildly offended. But when you identify it as "it looks like you burnt out 10 years ago in that project at XYZ and never recovered". I really identify with that.
Humans are weird creatures and "undoing" internal narratives we've built for ourselves is very hard.
Largely agree with the rest of the article.
Ooof this is me on Sundays - the only day allowed screen time, but man yea, if our girls are by themselves then a screen for them and a screen for me and we're all happy.
I understand geopolitics can change things as Israel is in the hot seat right now, but doing it regularly seems wasteful.
https://www.youtube.com/watch?v=qy8MdewY_TY&t=67s
Still possible, but increasingly unlikely due to the narrowing size range in which these black holes are allowed to exist in.
Tuning that sucker must have taken so much time in going for the absolute fastest speed.
The guy's face of accomplishment tells me pressing GO is nerve wracking and that risk of it exploding is non-zero.
It leaves too much to subjectivity.
My wife is an educator and we have long discussions about this. I believe lessons need to be upgraded to require AI and how to interact and prompt it for deeper meaning of more than just "Find the value of the hypotenuse". Something in the form of controlled modules?
Testing can stay exactly the same, i.e. no computers/ai, but learning has to be completely shifted.
But Lambda can't accept multiple connections to the same instance, so it's allowing multiple pg servers connect to the same data source.
Mentally this is the cheapest w/o all those egress costs, but I'm not sure. Combine that with we don't like managing resources outside AWS unless absolutely forced.
I really wanted this because RDS serverless v1 could do zero compute, but v2 has a minimum compute requirement.
If I can run my Postgres reliably on AWS Lambda, the costs drop to near zero for non production instances, which is where a lot of people play.
Overuse of dynamically generated functions is possible in any high level language. The worst offender that I had seen was a PHP wordpress plugin that stored a custom function per row in the DB brought to life via `eval`.
Those were the days.
Pure guessing, but, the employees are likely to trade the stock because of RSU's so the "hiding in plain sight" tactic.
> Having two people involved doesn’t preclude kickbacks, it makes it easier. One of them submits the spending request, the other one approves it, they both share the kickback.
Possible. Maybe the CTO brought in a relationship, maybe AI?, and the SVP caught wind of a kickback and got "cut in" as a result (Lord of War?).
Still, I'm not fully convinced because kickbacks, the speed is just too fast.
> People trying to get away with insider trading don’t use someone else at the same company, they use friends or family.
I wouldn't use friends or family that's what everyone else does and it becomes super obvious to the SEC. Someone within the company is not unlikely to trade the stock.
Is my best answer?
Having a CTO and SVP axed in the same statement means rather specific circumstances. Realistically rules out harassment, performance, even "kickbacks". These you would only expect one or the other to be terminated. Whether you agree or not, a company does not want to terminate immediately (she was just on stage as key speaker) two such key positions at the same time in the same department. It's a very large gap in the org that represents a material risk to the business. So their actions have to be so "huge" to match.
Stealing, but more likely some form of colluded insider trading.
I'd wager that the SVP was helping perform trades of expedia stock on behalf of the CTO. They got caught before the SEC and were fired.
Had a few friends who went to civil eng and two eventually joined city planning. Was fun to discuss their problems. Lack of funding really was the common thread. It's always lack of money.
This isn't 100% true. There are many small, rarely traveled, residential streets (i.e. only the people who live on the small street come/go from there) that feed into high traffic, multi-lane arteries.
Parent comment's scenario is pretty common due to detection based switching. 99.99% of the time this is desirable because it keeps the artery flowing.
If there's a crosswalk button across the artery, you'll many times find a person running out of their car to hit that to force the light change.
I like the wagon of smart phones attack[0]. Seems more fun and easy to do. I'll bet you could get all of Waymo's cars to reroute or force them to funnel into one street. THAT would be a cool show.
The problem is you don't like the customer service/sales voice because they "pretend to be your friends".
Let me know if I didn't capture it.
I don't think people "pretend to be my friend" when they answer the phone to help me sort out of airline ticket problem. I do believe they're trained to and work to take on a "friendly" tone. Even if the motive isn't genuine, because it's trained, it's way a nicer of an experience than someone who's angry or even simply monotone. Trying to fix my $1200 plane ticket is stressful enough. Don't need the CSR to make it worse.