Thanks for the repo link! Gave you a star :) I got the resilient builder ending. I guess my current experience in a startup has been quite useful haha. I know the pain of a million things to do and not enough time to do them all.
Ecosmic is on a mission to reduce threat exposure in space by building software for Space Situational Awareness. To achieve this, we built a team of flight dynamics engineers and computer scientists to build & package in-house algorithms into easy-to-use, reliable, and secure products. As an example, our platform recently allowed us to identify a series of close approaches in GEO involving Russia's Luch/Olymp-2 and a Western telecommunications satellite, possibly attributed to SIGINT activity.
We're hiring a Senior DevOps Engineer (mid-level candidates are welcome too!) to aid the effort of unlocking on-premises deployments of our algorithms with Kubernetes, and to contribute to the evolution of our platform.
Our stack includes Python for backend services and high-level algorithm tooling, C++ for performance-critical components, AWS for cloud infrastructure, and Terraform for IaC. We currently use managed serverless services, and we’re beginning a gradual migration from C++ to Rust for its reliability guarantees.
You’d join a team of three software engineers who love working in such a fantastic domain. I currently take care of most of the infrastructure work with the team, and we’re looking for someone who can help us tackle this new challenge.
Thank you for making this! I found the UI initially off-putting as I commonly associate it to vibecoded UIs, and I felt the same with some specific dialogue structures, but I had a lot of fun playing it all at once until the end.
You might be interested in Pixi: https://prefix.dev/
It uses uv under the hood for Python dependencies, while allowing you to also manage Conda dependencies in the same manifest (pixi.toml). The ergonomics are really nice and intuitive imo, and we're on our way to replace our Poetry and Conda usage with only Pixi for Python/C++ astrodynamics projects. The workspace-centric approach along with native lockfiles made most of our package management issues go away. I highly recommend it!
(Not affiliated anyhow, other than contributing with a simple PR for fun)
Messing with EEG headsets, like the ones by OpenBCI. Being able to perform some operations by just thinking about them sounds so incredibly cool - I've been thinking about this for several years, but it looks like quite an expensive hobby.
Loved it! I immediately thought of a survey we do at work monthly as a check-in for HR purposes, to gauge how we feel about the company, our work, the workload and so on. Right now we do it with a simple Google Form with a mixture of a score based question and an open-ended one. I'd probably like it a lot more from an employee perspective if the questionnaire was served with a system like yours. I imagine it would be cool for a HR member to have a set of metrics derived from the conversation, like a dashboard. Just my two cents. The only negative point is that it feels like the conversation never ends - as others said, it felt like the assistant asked similar questions to points already established before in my mind. It'd be nice to have some sort of progress bar, not sure. Amazing idea anyway, I wish you luck!
I have been using this site: https://artificialanalysis.ai/ . It's still about benchmarks, and it doesn't do deep dives into specific use cases, but it's helpful to compare models for intelligence vs cost vs latency and other characteristics.
Looks nice! I was curious about the effort needed to replicate this result with the Google Wallet API and it ended up being a nice evening project to pull off. Sadly with a demo account you get an ugly [TEST ONLY] tag in the card title with a non published account, and the customization options of the card itself don't allow much leeway. One thing I miss is being able to change the font color.
The other day I found this: https://www.vantage.sh/
I haven't had the chance to try it, but it seems to cover all your feature needs and the pricing looks reasonable, perhaps check it out.
I've used Zola (https://github.com/getzola/zola) for a static project homepage a few years ago to showcase examples with a simple description and a wasm app embedded in the page, it worked perfectly for me and the docs was clear on how to use it. It was very easy to set up along with a GitHub action to automatically update the wasm binaries when needed. It is definitely a tool I keep in my mental toolbox as a good default.
Known password managers such as Bitwarden don't simply communicate the master password from client to server in plain text: https://bitwarden.com/help/security-faqs/, the master password is salted and hashed client-side, then salted and hashed again when stored in Bitwarden servers. Even if you managed to perform a MITM attack, you'd only be able to download your encrypted vault data, which would then require your master password to decrypt (locally). I believe talking about security consideration requires specifying a threat model, but for the average user such a setup would definitely be considered secure enough. A local only setup would definitely be more secure, but then as you said you'd lose QoL feature such as ubiquitous access, or nice UI/UX, no setup hassle, easy usage of hardware tokens and so on.
If one were to attack Bitwarden, he would either have to crack the encryption scheme to attack a specific user/business or target it through other means. Ultimately I think it's a small compromise of a small security sacrifice versus a big gain in terms of usability and availability.
If I understood correctly, you are referring to applying some sort of tag component to a set of entity to be able to query it in a separate system. Am I correct?
For cross system data flow, I think a mechanism similar to what Bevy does is the way to go. A specific event bus where the developer can send any type of struct, which can also allow passing a set of entity ids. I have briefly used it for my project and I think it's clear to reason about. The only catch is that you need to be careful about timing (the time between sending and receiving an event might take one frame to propagate).
I wrote a thesis for my bachelor's regarding the development of an agent-based simulation framework in Rust where I managed the visualization side. The project takes inspiration from other frameworks such as MASON (in particular for the architecture), NetLogo, Agent.jl and others. I initially developed the visualization subsystem with Amethyst, after my thesis Amethyst was discontinued and, since I was already following Bevy since it went public and it looked like it was gaining a lot of momentum, I refactored our framework to switch to Bevy. Our project is open source: https://github.com/krABMaga/krABMaga . Being my first approach to Rust and my first serious greenfield project, I think there are a lot of parts which can be improved, but I was able to get by with my extremely limited knowledge of both Rust and Bevy and obtain decent results. The things I loved the most of Bevy was the low amount of boilerplate code needed, the WASM+WebGL support which allowed me to easily let guests run simulations from our github.io site (https://krabmaga.github.io/) at near native (sequential) performance and, just like the whole Rust ecosystem, the friendliness of the community. Even though I bothered quite a bit on the Discord server since the documentation wasn't the clearest for me back when I started (Bevy 0.5), both the team members and users always led me a hand. I also think the ECS approach is extremely useful for our usecase, by defining agents as entities with the Agent component, along with a system which acts as an event loop by executing a simulation step and triggering the agents' behaviour rules.
I also noticed the Bevy team might be interested in the simulation field (https://github.com/bevyengine/bevy/discussions/1678), I am sure more projects of this kind would be hugely appreciated!