Hacker Newsnew | past | comments | ask | show | jobs | submit | davidoduk's commentslogin

True, that's exactly how startups are, even before AI. It's not until they start getting big that they realize that they need to invest some time and create some processes to help them save time in the future

So when we think we're looking at Andromeda today, we're actually seeing Andromeda as it happened 2.5 million years ago. That means someone/something? in Andromeda today, with the ability to see Earth clearly, would see some of our ancestors, like Homo habilis. I've always wondered, if we end up being able to travel faster than light, we'd technically be able to look into the past depending on how far we go. 1000 light years away and you can see your ancestors on earth.

In some sense yes, but I'm not sure there's enough photons coming from Earth 1000 light years away to see anything, even with a fantastically sensitive telescope. It would be very cool, though.

A good enough lens would make it straightforward to solve murder mysteries, provided the murder happened outside on a sunny day.

The problem is that a lot of people who use agents to code nowadays, or Vibe coders, did not start from traditional engineering organizations, so they have no idea what best practices are in DevOps. Personally, I have a rule in every one of my tickets to update documentation when done. Ever so often, I would ask an agent to audit all the changes that have happened since the last audit, compare with the technical documentation and update whatever is stale. And occasionally, I would just have an agent do a pass and tighten the language, remove redundancies, and fine-tune it for human reading or agent reading.

Yeah, this is true—insufficient engineering experience to even recognise these issues is part of the problem. +1 to "fine-tuning" specifically the language or a workflow, too. I did it in the article and many people around are doing the same, apparently.

But still, in my experience, even in places with good engineering expertise and culture, there is also pressure to ship really fast, so systematic approaches to these things get overlooked, and gradual slopification happens. No perfect answer as to what to do with this, but I think it's important to name the problem and offer at least some easy solutions.


Break out implies that the agents are bound by the sandboxes. Are they really?


In 3 years Robotaxi allies with Uber to slow Hovercar rollout In 7 years Hovercar allies with Robotaxi to slow teleportation pods rollout


AI companies would lobby hard against such a law


And they all have the same tone, same inflection


Isn't there an international process to these things? Shouldn't google and apple be following that process?


No. Naming bodies of water is regional. It varies by language and country. If you look up these two bodies of water from different countries, they will have different names.


A point I have been trying to get across. There are too many examples to list of places with differing names. But renaming due to politics often has a history of being temporary.


I like the concept. If it's truly offline, does it use AI? Do users have to download a local model?


yes it downloads model, and runs it locally.


Working good so far. It's slower than wispr flow


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: