Readit News logoReadit News
prasoon2211 commented on Lina Khan points to Figma IPO as vindication of M&A scrutiny   techcrunch.com/2025/08/02... · Posted by u/bingden
prasoon2211 · 25 days ago
As others have said, this is classic selection-effect. Lina Khan isn't coming out and telling people about

- the companies that died because acquiring them was too much of a hassle

- the companies that died or never got funded / started because the investors couldn't see and exit path

- the companies that got acquired piecemeal (Windsurf, Inflection), leaving the early employees with NOTHING simply to avoid the ire of anti-trust hawks at the FTC. This has irreversibly damaged the SV bargain - early startup employees work hard in case of an acquisition, they get rich.

So Lina Khan can keep patting her own back but there's a reason founders, early-stage startup employees and investors disagree.

prasoon2211 commented on Writing a good design document   grantslatton.com/how-to-d... · Posted by u/kiyanwang
mtlynch · 25 days ago
>Amazon meetings start with the presenter passing out copies... of a prose document... The meeting starts with everyone sitting in silence, reading the document, and adding notes and questions in the margins with red pen.

I've never worked at Amazon, but I've heard this a lot, and it always strikes me as an odd practice. Odder still is that it apparently works and everyone I hear talk about it seems to love it.

You're squandering precious meeting time by having everyone sit and read a document together. They could easily do the same thing ahead of the meeting, and you'd have much shorter meetings.

And doing it synchronously means everyone either sits idle until the slowest reader is ready or not everyone gets to finish in time. And "slowest reader" isn't even just about reading speed. Presumably, some people can understand the document more quickly because they have more context.

In design reviews at Google, it was obvious that the majority of attendees came unprepared and were reading the docs for the first time while their teammates were discussing the doc. I suspect that the reason was that Google just didn't have a strong docs culture, and leads/managers quietly tolerated people coming unprepared (and sometimes, they themselves were unprepared).

I've never seen it done in practice, but I don't think it would be hard to have the best of both worlds where people review docs ahead of the review meeting, but there are strong cultural norms around reading docs ahead of time so the meeting is just for discussion, not just for reading or pretending that you've read.

prasoon2211 · 25 days ago
I worked at a company where we copied this from Amazon for a specific type of meeting (bi-weekly review). But we also had the other "normal" type of meeting.

People never read the documents before the meeting in those "normal" meetings.

The challenge with your suggestion is that people will half-ass the doc reading before the meeting - we tried doing this for the "normal" meetings. It was obvious the people skimmed the doc before the meeting. You're also now relying on the manager (if there even IS one for everyone in the meeting!) to care about this.

So, in practice, giving people dedicated 10 minutes at the start of the meeting works far better.

Besides, in most "normal" meetings, the main presenter often ends up discussing background / context for 10 minutes interspersed throughout the meeting anyway. In the "pre-read" meetings, you're just compress that to the first 10 minutes while increasing the amount of information transferred.

prasoon2211 commented on Show HN: Whispering – An open-source alternative to Superwhisper   github.com/braden-w/whisp... · Posted by u/braden-w
prasoon2211 · 2 months ago
This is really cool! Just started using it today. It's missing some of superwhisper's ease of use but other than that, 10/10
prasoon2211 commented on Gemini CLI   blog.google/technology/de... · Posted by u/sync
prasoon2211 · 2 months ago
I tried using it for something non-trivial. And:

> 429: Too many requests

Mind you, this is with a paid API key

prasoon2211 commented on The German automotive industry wants to develop open-source software together   vda.de/en/press/press-rel... · Posted by u/smartmic
niemandhier · 2 months ago
They will have to fix their attitude towards the people who build software before they can be successful.

In a typical German corp software developers even in RnD are not seen as an asset but as a mixture of line workers and support staff.

The problem is: The world best assembly line worker will not boost your companies performance in a measurable way, but a better dev will make a heavy impact in his project.

Nice example:

A friend of mine worked in RnD in a German DAX corp. C-Level regularly had them fix bugs in other projects. Why? RnD is the only department that can adapt its planing fast enough to fit in stupid side tasks. As a result the best people left, were replaced and the average skill of the department regressed to the mean.

prasoon2211 · 2 months ago
Exactly this. In Germany, the median software developer is treated (and paid) pretty much the same as a blue collar worker, both by their company and by society at large.

From calling it "IT" to paying peanuts, no wonder no one smart and ambitious wants to get into CS here. All the smart kids seems to want to go into consulting and finance. So, of course Germany doesn't see the kind of outsized success in the Tech industry like the US or even the UK.

Volkswagen's (and in general other automaker's) software sucking is simply a fact downstream of that.

prasoon2211 commented on SourceHut moves business operations from US to Europe   lists.sr.ht/~sircmpwn/sr.... · Posted by u/DyslexicAtheist
prasoon2211 · 2 months ago
This makes sense. And this is only accelerating - I talk to businesses in Germany and there's a genuine, non-insignificant number of people who want their data to be /physically/ in Europe.

Take this to its logical conclusion and basically, every company will need to segregate their data in regions. Most cloud platforms aren't really designed this way but it's coming.

There was a data locality law that India passed and Stripe had to do this massive migration project to segregate this data. I shudder to imagine what a more complex system would look like under such data locality laws.

prasoon2211 commented on Stripe Reader   stripe.com/terminal/strip... · Posted by u/lachyg
posguy · 4 years ago
The frontend (what authorizes the transaction with the card network, like Visa, Pulse, Star, Mastercard, etc) and backend (settlement bank that ACHes the cash around and usually takes the underwriting risk (unless the independent sales organization, eg: Stripe or Gravity decides to do this themselves)) are generally called a payment platform in the industry.

This platform can get wrapped with many different payment terminals (Verifone, Pax, Dejavoo, Ingenico, etc) or processing interfaces (Authorize.net, PayPal, Stripe, Square, et all).

Square does look to be a bank now, but it appears the only products they are underwriting risk on are loans to businesses, which they immediately try to sell off to third party investors: https://www.cnn.com/2021/03/02/tech/square-bank-business-len...

Kinda surprising, I would expect them to have underwritten their own payment processing, but it might be the case that they don't want to have the outsized liability of chargebacks on their books if a client business goes bankrupt, all to save 2 cents on a $100 transaction.

Perhaps once the US economy slows its rapid economic shift they will consider handling their own underwriting and batch settlement.

prasoon2211 · 4 years ago
This is tangential but you seems really knowledgeable about the payments industry. Can you perhaps recommend some sources to understand how the payments infrastructure works (POS but also web/online/mobile)? I only seem to have a broad idea and would love to understand the nitty-gritty of it all!

u/prasoon2211

KarmaCake day237February 18, 2014View Original