Earlier quoted context omitted.
They'll learn soon enough that selling to developers necessitates speaking clearly.
They will sell to their managers
Edit: Actually it may just be aimed at investors. Who cares about having a product?
101–110 of 625 posts
Earlier quoted context omitted.
They'll learn soon enough that selling to developers necessitates speaking clearly.
They will sell to their managers
Edit: Actually it may just be aimed at investors. Who cares about having a product?
Earlier quoted context omitted.
They will sell to their managers
No. With this kind of bullshit they plan to try to sell to C-levels and board members. Edit: Actually it may just be aimed at investors. Who cares about having a product?
The fact that the first image you see has "$60M seed" in big text, I have to agree, this does not feel aimed at devs.
Earlier quoted context omitted.
Exactly ... tired by all the marketing hyperbole talk. Just show what your product does in a simple example / showcase. If it's good, people will like it. You can save yourself a lot of text copy and user time that way.
They'll learn soon enough that selling to developers necessitates speaking clearly.
> Spec-driven development is becoming the primary driver of code generation. This sounds like my current "phase" of AI coding. I have had so many project ideas for years that I can just spec out, everything I've thought about, all the little ideas and details, things I only had time to think about, never implement. I then feed it to Claude, and watch it meet my every specification, I can then test it, note any bugs,…
I am going lower level - every individual work item is a "task.md" file, starts initially as a user ask, then add planning, and then the agent checks gates "[ ]" on each subtask as it works through it. In the end the task files remain part of the project, documenting work done. I also keep an up to date mind map for the whole project to speed up start time. And I use git hooks on the tool event to print the current o…
I'm confused how this is any different to the pretty standard agentic coding workflow?
We went from having new JavaScript frameworks every week to having new AI frameworks every week. I'm thinking I should build a HN clone that filters out all posts about AI topics...
I've long wished for a 'filter' feature for the hn feed -- namely the old trend of web3 slop -- but with little else than keywords to filter, it would likely be tedious and inaccurate. Ironically, I think with AI/LLMs it could be a little easier to analyze.
Earlier quoted context omitted.
Pierre didn't shutdown, they said they just paused signups on the code review app to focus on the code storage service. Productizing the building blocks of the platform seems like the smart play in today's environment honestly.
Sure but I dont want to build my own Github I just want to use a beautiful and faster alternative
Earlier quoted context omitted.
Uses AI to summarize coding sessions tied to commits. Commit hook > Background agent summarizes (in a data structure) the work that went into the commit. Built similar (with a better name) a week ago at a hackathon: https://github.com/eqtylab/y
Which only reinforces someone just lit $60M on fire. It's trivial to do this and there are so many ways people do things, having the AI build custom for you is better than paying some VC funded platform to build something for the average