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

Personally I think security is far ahead here compared to normal observability tools. I decided to work on a side-project to try and add SIEM like functionality to a clickhouse backed otel platform; by the end of it the thing I came to believe the tooling blue teams use should be used in observability generally, not just security. Incident/event management is a very powerful concept, and provides a clean framework to hang all of this information on. Then your solution for mechanically finding the neighborhood in k8s is one way to add observations to an event. Some SIEMs have started having agents recommend stuff to be added to an event, which is a nice middle-ground of having agents help but not completely control the discovery and diagnostic effort (as well as providing a clean feedback loop for training data synthesis).

That's all to say, have you considered that framing, and if so, have any opinions on why more general observability tools haven't gone that direction?


Are you saying that if everything became an event, its easier to correlate because the event is more free form and it's easier to add custom metadata?

In theory, I agree with you. But you can't eliminate 'joins' all together, IMO, because it's not practical to know beforehand what context will be useful.


I also think BDD is a really powerful tool for UI acceptance tests! I've now worked on adding it to two AI codebases (one engineered, another vibecoded), and so far it has been mostly positive. Having non-engineers be able to see what effects their code changes have in the UI is nice; and I find having high level API and UI tests is forcing the first layer of cleanup (standardize access to DB through models/services, and a single API SDK).

I am also really interested in standardizing the REST interface with typespec, and the database schema with DBML. I think creating these closed-loops with high-level specs is one of the best ways to make an AI project ownable by a team.


How are you doing that? Is the Playwright usage a hidden detail or do images appear in the spec?


Basically I'm designing a two layer interface, the first layer speaks app UI specific language and runs playwright directly (signin, dismiss toast, go to dashboard), and then the second speaks product language ("user opens dashboard" in Gherkin would translate to signin, wait for app to load, go to dashboard; for example). The translation from product level language to app level language is the step definition files bddgen uses. I'm building up a little skills library to try and force Claude to stick to these separate levels of abstraction; then also do deduplication and cleanup after implementing new specs.

We don't really use images for acceptance testing, it's more functionality. I don't really care where the button is, just that if I click it, it does what it says it does. To that end, we already have multi-tenancy in the application (I highly recommend every app build this in, if only for testing; then you don't need to do the Postgres template1 seeding hacks), so we spin up a tenant for a test, do all the setup with the API (all the Given statements), playwright to do the validation of a feature (the When statements), and finally validation is a mix of Playwright and API (the Then statements).

Sorry if that isn't super clear; maybe I could put together a little demo repo or something if people have any interest; I'm hoping to do that after I introduce typespec and dbml (basically spec/{acceptance,api,db}).


Yep, I've been experimenting Playwright with CucumberJS and Deno for the last 3 months and it's super effective


I think we need a new area of study around UI/Agent connection. It can kinda be done with tools, but I'd we need much deeper primitives to allow the UI to inform the Agent and vice-versa. Right now we've just given up, replacing the UI with an Agent message view, but I think that's just because nobody is thinking about how the two can compliment each other

I've been playing around with using a hidden markov model informed by a UI state event stream, with the end state fed into the Agent as a hint on each message turn. Then the Agent can make a tool call to add events to the HMM. This has been really interesting, but I haven't struck the right balance to make it actually feel good for the user yet


Isn't this the direction Claude on the web is going towards? It's a mix of message view on the left and specific interactive UI on the right panel. There is also MCP Apps spec now


Love TUI apps, hate that there isn't a clean way to control native scrollback. It leaves you stuck between manually managing it via awkward hacks on the current visible screen, or not using it at all. I've been working on an LLM harness TUI for a little while, and this specific part has been the most frustrating (in conjunction with tmux).


I've been working on a graph database in Rust this year actually! I'd love to hear anything you can talk about wrt the query planner and/or how you decided to do cardinality estimation. I decided to go with an EAV graph which makes CE pretty complex, and it's been an interesting challenge to balance quality and speed and expressiveness in the query language


I don't have hard data, but I own 3 air gradients and they've been going strong for years. I don't think it's unreasonable to think they just got unlucky


>they just got unlucky

then let me ask you: as an ethical person trying to write a review, how do you handle that situation? It seems like that's an angle to this that we're not exploring, and that's whether the review is epistemologically justified rather than whether it's objectively correct. The way I see it, as a reviewer I get a product that fails well sooner than I expected it to and I have three choices:

1) Don't report the failure

2) Report the failure

3) Report the failure but try to contextualize it (basically, trying to solve for sure whether they got unlucky or not)

1 is obviously unethical, and 3 seems like it's well outside the scope of a reviewer's duty (and could be seen as carrying water for a particular brand. after all, do you think the person who wrote the OP would be okay with it if his product's failure was considered typical but another product's failure was determined to be atypical, regardless of the truth?). The only ethical approach is to report what happened, and not speculate as to cause.


Your 2nd option is what I would like to see. And I do agree that it is not perfect, but as you pointed out, it is the least bad option.


Do what Linus Tech Tips has done (when they're doing it right): report that they got the device, tested it for a while, and it broke, so what they currently know about it is not the full picture, and that they might revisit the product when they have confirmed that they've worked out the kinks with the device in question.

Easy


That feels like exactly what the article did. They disclosed that the thing broke and on what time frame, alongside details about the degradation of functionality. As far as say that this isn't the full picture, is it definitely not? If we owe someone the benefit of the doubt if their device breaks while being reviewed do we owe the reader the deficit of the doubt if it doesn't break? What if they just got lucky?


Yes.


Definitely not. Repealing section 174 (or not extending it, as it were) helped pushed us into a new normal for the market. Adding it back doesn't in and of itself push the market into another new normal, we'd need a lot more. It might take the edge off though, hopefully.


Agreed. Consider that we're in a big tech bubble right now (AI) and have been for at least a couple years. And yet tech layoffs have been way up, and hiring way down. Part of that that could be attributable to 174, but there are other issues that contribute more. One would be that there are vanishingly few people with actual experience in this narrow part of AI (LLMs) - I know people working in AI that have been laid off in the last couple of years because they were in the wrong area of AI (vision & CNNs). Secondly, it turns out that not that many people are needed to work on this stuff (mostly concentrated in large companies like Meta, Google, Microsoft & Amazon). And thirdly, folks in the C suite became convinced that AI is going to replace software engineers so they've quite hiring them.


> And thirdly, folks in the C suite became convinced that AI is going to replace software engineers so they've quite hiring them.

I think this is the real reason for much of the layoffs.

The other reason is simply that the market isn't punishing layoffs. You get rewarded as a CEO for laying off employees and saying "It's because AI makes them obsolete"


I don't know anything about electronics design, but I'm really into backpacking so a high efficiency battery system with a solar panel is really interesting to me. I came across this project[1], and wanted to improve upon it for my usecase. I want to add the ability to have multiple 21700 cells in a lightweight charger, instead of a single cell with a builtin USB charger. I want to learn more electronics, but it definitely feels like a multiyear process, and it'd be nice to shortcut it for the projects I'm interested in.

1. https://www.reddit.com/r/myog/comments/1k3stln/ultralight_13...


Learning just enough for your needs is a valid approach to learning electronics design, unless you're planning on becoming an actual EE.

It provides a huge amount of self-motivation and as much as I hate to admit it (as a one-time electronics design engineer), you can skip a lot of the middle-layer concepts. Sure, you should understand Ohm's law and what basic components (resistors, capacitors, transistors) do, but you can jump from that right into understanding how a battery charger works without having to understand how the components actually work.

The hard part is finding good tutorial material that starts at the right level: most of the professionally written stuff presupposes that you're either already an EE, or have one at your disposal to translate things for you.


Such is life in STEM.

Edit: And EE is genuinely involved.


It's true, Gaussian Splatting is just an alternative to meshing a pointcloud for companies which currently rely on photogrammetry or lidar (Lidar works well as a basis for splatting when there's reference images taken as part of the scan). But I think that misses all the new opportunities that exist with Gaussian Splatting, which really just don't with existing techniques.

Gaussian Splats are able to handle more heterogeneous information sources, allowing more sources to help splat an environment. Devices like drones, surveillance cameras, or autonomous systems can be used to create or incrementally update a Gaussian Splat; and there's interesting work to allow them to locate themselves within the splat, not just to show themselves but also to place vision ML outputs into it (such as object detection or segmentation results).

Up till now nearly all digital representations of physical environments are either based off the original designs (by things like CAD or BIM files), or are an approximation of the environment (from photogrammetry or Lidar scans). CAD and BIM files suffer from drift, the real environment almost never perfectly matches the design files, small (and large) changes are made; and many times those files aren't even available if the structure isn't new. Photogrammetry and Lidar scans struggle because their output is a pointcloud, and it's very difficult to accurately mesh a pointcloud (Matterport only partially solved this problem and sold for $1.6B). Gaussian Splats overcome these issues; they're comparatively easy to generate for any environment, and allow for very accurate and easy viewing from any angle.

I think the Digital Twin space will be turned upside down, and they could potentially even cause huge changes in autonomous and semi-autonomous factories, warehouses, and depots. A single Gaussian Splat could be the source of truth that many autonomous vehicles update through their separate SLAM systems. Operators then would have access to this splat (and it's history) as a source of truth for the environment. Then, using techniques like iComMa[1], it may be possible to directly align XR devices into the Gaussian Splat; allowing operators direct access to location-based information generated by the environment.

That's a lot of words to say: Gaussian Splatting is a very neat new technology that could really underpin many future technologies, I'm really excited about it

[1]: https://yuansun-xjtu.github.io/iComMa.io/


I do agree that new use cases are emerging and it will probably enable tons of new businesses. I'm very gung-ho about the technology myself as well. I guess what I'm trying to say is that the new businesses that emerge because of this are not necessarily going to advertise that they use gaussian splats to do it, it's not a buzzy enough term, and many of the industries it serves just care about the results it delivers. Your average tech person is unlikely to hear much about it. Your average graphics engineer will have probably heard about it, but not know about all the use cases that are leveraging it. And your average person in the industry it is changing won't know what is causing the change (they will probably assign it to the nebulous ai bucket). I fully expect gaussian splats to be a quiet revolution.


Yeah, I see your point. I'd be surprised of Gaussian Splatting didn't make it into the advertising for Digital Twin services if/when they add it (like Bently's iTwin or Dassault's Virtual Twin). Whether that translates more broadly into the market, I don't know.

On the other hand, I'm playing with the idea of a platform which provides a Gaussian Splat based Digital Twin of an environment so other systems can utilize it to share location-based information. Even though I don't think it'll be possible to build without utilizing Gaussian Splatting; splatting may not end up in any of the pitches or advertising directly.


This is conflating splatting with more general pointcloud data.

Splatting is fundamentally about viewing pointcloud data. That's great. But it doesn't deal with all the other functions virtual twins need pointclouds for (e.g. design vs real world conformance).

Pointclouds themselves are proving hugely useful in a number of fields but vary considerably in form and application often based on how they are captured (e.g. LiDAR vs SfM photogrammetry)

Visualising pointclouds effectively has been a major problem which splatting really solves elegantly so it will be a major practical advance when splatting is added to cad software and javascript map visualisation libraries.


this is very interesting and thought-provoking; thank you

what exactly do you mean by 'digital twin'? do you mean any kind of computer model of a real-world phenomenon, including sets of differential equations, as i've sometimes seen it used? presumably you mean something narrower, but how narrow? do you mean, for example, specifically cad models of parts that are going to be manufactured?

i guess this sounds like i'm nitpicking but actually i just want to know the scope of the space that you expect to be turned upside down


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

Search: