Cloud console does nothing.

They should host their support services on AWS and vice-versa.

If it's satire, it's brilliant: because most of the comments I see (here and elsewhere) are clearly written by people who tried agentic coding before Opus 4, and haven't given it a fair shake over the ensuing five days.

IMO the most important engineering skill in 2025 isn't low-level programming, or the craft of debugging, or even having a firm grasp of system architecture. Believe it or not, I truly believe the vibe-first juniors will learn that stuff too, over the course of their careers, just as we did: through necessity (As an aside: if you don't think they'll encounter such necessity, then it's inherently not one any more than the countless other once-honored, fastidious hallmarks of craft that have since been rendered obsolete. And if you don't think they'll learn even upon encountering a true necessity, then you underestimate them.)

No, the most important engineering skill in 2025 is non-attachment: constantly update your priors, and hold your opinions very loosely. Because those opinions could be fully wrong before the essay even gets shared.

Comments URL: https://news.ycombinator.com/item?id=28607126

Points: 2

# Comments: 2

For users of Fabric/Crashlytics/Answers, is there a TLDR somewhere for the new terms? (specifically, the delta between their new terms preview and the old terms)

For your article, you may be interested in a piece I wrote about Demo Day pitching specifically:

https://keen.io/blog/41079734225/how-to-write-your-demo-day-...

You're right: practice really seems like the key to getting this stuff down. One can have a clear intuitive understanding of their vision long before they have a clear way to express it in English.

It's validating to hear from an industry veteran that our thesis isn't totally off base :)

Keen IO takes an API-based approach to the problem, which means:

- developer abstractions are higher level than rolling your own

- scalability is as easy as "my bill went up" (as opposed to "my ALTER statements stopped working!" or "I need to leave mongo and buy a book on distributed system engineering!"

- ability to cover new/emergent use cases is a lot higher than you would get with an off-the-shelf analytics product

Now that I've pitched 80-90 additional times, I must say PG's approach in this video is above average, if anything, when it comes to giving the entrepreneur the benefit of the doubt -- so in my opinion it's really not on him.

Question: What's missing from our API? Are there any qualitative or quantitative limitations that got in your way?

I don't mind being called out when I'm out of order, because I see it as an opportunity to become a better community citizen. But it's hard to become a better community citizen without some corrective advice.

Would you please point me to the code of conduct (and ideally to the specific rules I've broken), so I can be better in the future?

Comments URL: https://news.ycombinator.com/item?id=8075406

Points: 11

# Comments: 5

Comments URL: https://news.ycombinator.com/item?id=7847688

Points: 7

# Comments: 1

Couldn't agree more about the four hours per day piece. The best work I did in my career as a dev was the year I worked 20 hour weeks.

You may be interested in an upcoming feature we currently have in private beta, which does this:

    your events  ---->  Keen IO  ---->  your S3 bucket on AWS

I wonder: would that feature be interesting to you? Would it have perhaps allowed us to win your business?