HN user

4lx87

98 karma
Posts3
Comments38
View on HN

Huh. The sales team at my company is the one who closes millions in ARR and all the enterprise contracts - not the CEO. I’m sure being the “conduit of information and a representative element” is very important though. Someone has to attend investor meetings…

What's the moat? I asked the same question to Google, "What materials do I need to build a fence?" and I get an LLM-generated answer + ads. If I do the same with duckduckgo or Siri I get the answer without the ads.

LLM inference is a commodity. Do people care where it comes from?

If the PDS URL is dead, is there a way to find the new canonical PDS? I guess you can theoretically index every log from everywhere and just look for new entries signed by the same key? But there would be no way to know if you have the latest posts without the PDS address.

IMO code/service owners. Orgs can be scaled by splitting code ownership into teams owning different services. And if someone isn’t competent enough to ship code on the service they’ve been assigned to work on, they aren’t qualified to be employed working in that thing. They aren’t providing value to the organization (probably net negative).

PRs don’t actually solve the “but what if someone ships crap” problem. Taking capacity from competent engineers to review and correct other employee’s code defeats the purpose of employing people: to add capacity.

Juniors/employees in training should be shadowing or paired with someone who is competent until they are competent, and assigned work at their level.

I think it’s becoming more and more performative. We’ve never been less focused on the actual product — the software — than we are now. The focus is increasingly on how someone generates code, despite that not having much to do with the product.

The software is not getting better. Generating code faster does not result in better software. Software continues to be slow, unreliable, complex, and counter-intuitive. AI has not improved on the metrics that matter.

AI, as amazing as it is, has not actually changed the process of software development and as a consequence, the resulting software has not changed. The job hasn’t either, except insofar as you’re judged for tokenmaxxing.

From a user’s perspective: To use Bluesky I need to create an account, and to create an account I need to choose the server where that account is hosted. Once I have an account I can follow any account even if hosted w/ someone else. That’s the same UX as Mastadon (leaving aside that moving PDS might be easier in ATProto than ActivityPub).

If it quacks like a duck... An account has a single Personal Data Server (PDS), right? The DID links to a PDS which is the canonical data feed for a user, and where a user's writes go. Data can be replicated but the PDS is treated as canonical. That's much closer to client/server architecture than distributed architecture. There's no P2P database. There's no writes into a DHT or peers. You write to your PDS, then those writes are optionally mirrored. Also discovery happens via DNS, so you don't even ask peers for data. You connect to a relay not as a peer but as a client asking a server for a copy of data that's canonically hosted by the PDS. I don't think it's a stretch to call the PDS an instance and the relay a mirror.

Right, and do you spend so much of your time doing that your net LoC is negative? If that's the case it implies people are writing code only for other programmers to clean it up. Programmers solving a problem created by programmers. That's dysfunctional. Effective engineering as I see it would be putting the processes in place to prevent having to constantly rewrite code.

Because they were added doesn't mean they were needed and even if the same person added and then removed them, it doesn't mean they are digging ditches to fill them.

Huh? If LoC weren't needed then adding them was unnecessary and a waste of time. Someone who is known at an organization for removing unnecessary code screams inefficiency to me. It's paying one person to create a mess then another to clean it up.

The most effective contributors at your job remove more code than they add? That doesn't sound effective that sounds like digging ditches to fill them. Every line of code removed is a line that was previously added.

Nobody wants to hear "no". The way you say "no" without saying it is by turning "no" into an option, and attaching costs to options.

"no, I won't be able to make it in time" would be "I can confidently deliver in time if I have X, and we save Y and Z for later."

It is insane, but my past experience with GCP is they suspended all service only days after a failed payment, after years of paying on time. It's a major factor in why I don't use them anymore. I'm not waking up to angry customers again because the CC is expired and I missed an email.

I'd be curious to know why Railway's account was suspended. Was it a similar payment issue or something else?