kadhirvelm

5 ms·

31.
by kadhirvelm 4mo ago
We’ve added collaboration and communication as big facets in our hiring loop rubrics, and reduced the complexity of our questions. We also tell candidates this ahead of time - been honestly working pretty well so far, it indexes more on tho
32.
When building is free, what do we build?(productnow.ai)
3 points by kadhirvelm 4mo ago|1 comments
33.
by kadhirvelm 4mo ago
Disclosure: I wrote this as a founder of ProductNow. The last couple of sections highlight what we're building, so I wanted to be upfront about that. Though the broader thesis that software is becoming a utility and the physical world
34.
Show HN: A rich, HTML-native document canvas for human <> AI collaboration(app.productnow.ai)
2 points by kadhirvelm 4mo ago|0 comments
35.
by kadhirvelm 5mo ago
The single file is interesting, we’ve been observing something similar too. Do you have a specific prompt that you load in by default to make this work? Are these react files, or just pure HTML/JS/CSS? Aka do you compile it via Es
36.
by kadhirvelm 5mo ago
Sad
37.
by kadhirvelm 5mo ago
What are people doing with prototypes afterward? Do you end up shipping it as is to production? What about at work? Are the prototypes useful in that context?
38.
by kadhirvelm 5mo ago
I think we need to look past software and spend more time and energy on the physical world. Let the digital world just be a means to an end, and we spend more time and resources on problems that matter. Reallocate societal attention to the
39.
A Dose of Hope for the Future(productnow.ai)
3 points by kadhirvelm 5mo ago|0 comments
40.
Ask HN: How are people getting feedback on prototypes?
1 points by kadhirvelm 5mo ago|0 comments
41.
by kadhirvelm 5mo ago
I’ve been thinking about this one a lot! Wrote a post on it a little while ago: https://productnow.ai/blogs/write-for-human-download-time But I really agree with use AI to make your communication sharper. I think a lot
42.
Good Code, Wrong Feature: The Handoff Problem(productnow.ai)
2 points by kadhirvelm 5mo ago|1 comments
43.
by kadhirvelm 5mo ago
Btw these posts are embedded documents from ProductNow. Been experimenting with more 2-way communication between writers and readers. What do you think? Useful?
44.
The unspoken cost of bad communication(productnow.ai)
1 points by kadhirvelm 5mo ago|1 comments
45.
by kadhirvelm 5mo ago
Curious how other's have been driving alignment on their teams. We've been finding as AI sped things up, keeping people in sync has been increasingly challenging. We personally have found a doc-driven culture has been super helpfu
46.
I tried to build a LitRPG sandbox with on the fly generated sprites(app.productnow.ai)
1 points by kadhirvelm 5mo ago|1 comments
47.
by kadhirvelm 5mo ago
Didn't quite get around to open sourcing the code, but I have some code snippets in there in case someone else is inspired enough to try. Curious what other's think? Seem like a fun genre?
48.
by kadhirvelm 5mo ago
Whoop sorry, should be back now
49.
by kadhirvelm 5mo ago
Yeah I like that, there’s probably something to this full stack builder persona that could keep people motivated long term. So long as they feel ownership, seems like that’s a pretty good bet for long term engagement
50.
by kadhirvelm 5mo ago
Curious what other teams are doing to keep encouraging people to think critically about their code? I’ve been finding it harder to keep people motivated, keep them engaged with all the changes coming in. And I can’t blame them, it’s been ov
51.
by kadhirvelm 5mo ago
Totally agree, we wrote our own piece similar to this: https://productnow.ai/blogs/teams-that-coordinate I really think as code becomes cheap, misalignment between people, teams, and organizations is going to hurt a lo
52.
by kadhirvelm 5mo ago
Honestly I kind of feel for them - their traffic must be spiking like no tomorrow. Though still annoying when the team takes down time because GitHub is down...has anyone transitioned to something else successfully?
53.
by kadhirvelm 5mo ago
We don’t think AI vs human authorship is as much of a problem at slop vs not slop is. To break through the noise, we’ve started optimizing our docs on human download time
54.
by kadhirvelm 5mo ago
I can't imagine going from reviewing code in Zig to letting Claude code handle it in Rust. Seems like a lot of change to deal with in a short amount of time. Wonder how much the bun team culture will change? We've been really liki
55.
Doc driven engineering prioritizes team coordination(productnow.ai)
1 points by kadhirvelm 6mo ago|1 comments
56.
by kadhirvelm 6mo ago
As AI wrote more and more of our code, we found the speed came at a steep cost: we were constantly misaligned even as a small team. It was just too much to keep track of. So we switched to a doc driven development culture and found a lot mo
57.
by kadhirvelm 6mo ago
We are a doc-driven development team. No major feature ships without a clean RFC attached to it. It sounds like overhead, but in practice it's been one of the highest-leverage investments we've made.
58.
Our doc-driven engineering playbook(productnow.ai)
5 points by kadhirvelm 6mo ago|1 comments
59.
by kadhirvelm 7mo ago
Honestly my hope is the arbitrage that allowed big tech to make the kind of margins it does on software starts to go away because it’s sooo cheap to build software. In other words, defending the technical moats that we rely on today doesn’t
60.
by kadhirvelm 1y ago
Well the thing that’s infuriating for me is feeling like there isn’t a good, well supported alternative for writing an enterprise grade React app that will be continue to be around. I used to rely on create-react-app, but now that that’s de

More ›