The repo doesn't contain what the doc says it should contain
Readit NewsFlundstrom2 commented on Show HN: NZ1 new compression for embedded systems and games · Posted by u/Forgret
The similarities between the universe beginnings and the formation of black holes, is to me, veryyyyy similar.
Yep. From the viewpoint of an given photon, it touches both its origin and its final destination - even if it is at the edge of the universe - at once. So, from the photons' point of view, we still live in the Big Bang and time does not pass, never has and never will.
This Guide is intended to contribute to a better understanding of EU product rules and to their more uniform and coherent application across different sectors and throughout the single market.
This Guide applies to the EU Member States but also to Iceland, Liechtenstein and Norway as signatories of the Agreement on the European Economic Area (EEA), as well as Switzerland and Turkey in certain cases. References to the Union or the single market are, accordingly, to be understood as referring to the EEA, or to the EEA market.
This Guide discusses non-food and non-agricultural products referred to as industrial products or products whether for use by consumers or professionals.
No contact in formation, ToS and Privacy Policy basically empty, no customer support links, no company information apart from a name.
Regarding jurisdiction of the ToS only states "These terms shall be governed by and construed in accordance with the laws of the jurisdiction in which Nimrobo AI operates"
Where is even the company registered, where is the data hosted, what about GDPR?
No thanks, I'll pass on this one.
Maybe consider using EU-based alternatives such as Mistral Le Chat, and StackIT. That at least gives privacy and transparency mandated by law.
But yeah, migrating the core business systems to cloud surely adds risk of lock-in, as well as juridical and geopolitical risks.
Flundstrom2 commented on Product as Code: Version Control for Product Management mantcz.com/blog/introduci... · Posted by u/iamflimflam1
Interesting concept.
Although, when we get above the epic/ticket level and onto product management, we inevitable get into the process, product and project parts as well, and eventually we also get into the division of the R&D department into teams and what not, which makes a standardized format challenging. Not impossible, but challenging.
However, there are a few fields that wound benefit from having a stricter - but customizable - definition through some additional configuration file; and specifically status, priority, type.
There's also inevitable going to be different roles needed for different companies, such as creator, owner, assignee, sponsor, so those distinct fields (except maybe assignee) would rather be an array of key/value for the roles.
Only looking at the proposal as-is, I lacked a closed_at field.
The labels and estimate are also challenging; what to accept? Some prefer t-shirt, others story point and some actual durations. And who is allowed to define those?
One thing I've had issues with in all kind of system, are the separation between mandatory, optional and useless fields. In many cases the useless fields are way too many compared to the fields that are actually used for a specific team. Generally, fields tend to lack clear guidance in the tools on who owns them, what to populate them with, and why they exist. Elon Musk once stated that every single requirement must have an owner, and IMHO, so must every single field in the ticket tracking system.
Those things are both company/project/product and team-specific, just as the transitions between the states.
And speaking of transitions, the interesting thing to track against, is rarely the current snapshot of the currently know the requirements, but the changes to the scope, which in turn reflects (from) the company's launch plan.
To generalize, the scope is either increased, decreased or clarified, and that changes all the way from the initial vision statement to the "final" delivery before the EOL and decommsion project has completed.
But, as I mentioned; an interesting concept!
Then, there's a small MIDI-utility hardware built on a small Adafruit featherwing that I intend to rewrite in embedded Rust.