Anyone thinking of adding a feature or separate tool for exporting existing gitlab/github issues to this Ticket or Beads? Looks like in the Agentic Era having issues/tickets managed using this kind of tools and kept in folders side by side with code and documents is much more desirable than separating them to web based git servers
Very good then, and sorry for my skepticism! Indeed you’re making good use of LLM on all aspects of your professional life. I’m curious: the same applies to your hobbies and personal life? Any use of LLM that changed also those?
The author’s LinkedIn profile is also crafted by AI (and the person invented I guess). I’m asking myself if this is a joke, an experiment or a sort of a scam.
This thread is becoming huge and so searching through the comments is not easy. Nonetheless it’s my impression that little or no attention was directed to the regulatory compliance needed for vehicles to be marketed under the rules of UN (known as UN/ECE Regulations and approval scheme) and similar approaches worldwide. Which means that roughly speaking that the security and safety of the car being sold today rest assured until I don’t change (upgrade) the software governing its functionalities. It’s totally unclear how it might be possible at least in Europe to upgrade major parts of vehicles software without breaking its approval. Comments on this?
This is really at the boundaries of my comprehension of physics but it’s a remarkable achievement of Italy, Europe and international Academic institutions at large - we need them all!!!
Promising. Looks like it can leverage existing requirements if included in the git repository as ReqIF exchange format files. I’m currently not able to verify with an experiment because I’m dealing with huge sets of requirements and I easily reach the limits of API (I guess), need to trim down. Any experience by others?
The point (as discussed now within interested parties) is that Technical Standards, and namely Harmonized Standards in the realm of the so called "New Approach" to products compliance, are now cited as recommended and voluntary technical measures for reaching compliance to some EU Directive or Regulation. Up to now, technical standards are discussed and published in sort-of private organizations, although sometimes funded by governments. Here the court expressed the opinion that these Harmonized Standards have somehow lawful relevance and should be freely available (not paywalled) to all EU Citizends.
On this topic (certified libraries) I suspect an interesting evolution might happen: by observing how you guys at Ferrous achieved this milestone while keeping a consistent openness, other actors (companies, consultancies and academic institutions) start seriously thinking about the possibility of contributing with high quality and certified libraries for a lot of scenarios. In other words I’d look at this as a milestone that opens to new and disrupting ideas
This is a milestone and a landmark achievement. And the reasons for this are not limited to the availability of a qualified and vendor supported toolchain for the use of Rust in Functional Safety concerned embedded designs. The goal has been reached while maintaining openness and shared results, which is an industry first.
The data breach announcement is a bit vague on the meaning of “login pairs”. The best practices of breaches databases of the like of https://haveibeenpwned.com/ is to maintain records of login matter (username, email, password etc) in a strongly hashed format. This still enables searching and comparing but not extracting for later use. Why the database here looks like plain text is totally unclear. Or maybe the passwords are hashed here also (which anyway exposes email addresses)?
This is my collection of Friday newsletter and blog post where I list 2-3 suggested readings (occasionally podcasts or videos) on technology/innovation/management and 1 on climate change.
Great!!! A big part of the value here is the clear and complete explanation, with pointers to external references. May I ask you how do you perform the part:
“All these artifacts are commited back into the master and a version is applied. I also have a CHANGELOG.md which is automatically filled from commit messages (I used conventional commits to format my commit messages)”
Although all vulnerabilities affect cloud services and/or mobile apps (SaaS and similar areas) looks like this eventually leads to closely interact with the single vehicles. Which raises questions about the recent Cybersecurity UNECE Regulations R155 and R156 that any new vehicles manufacturer must take into account while submitting a new model for approval in Europe and other areas. Those regulations explicitly cover the vehicle itself and not connected cloud services. Should an urgent revision extend coverage?
Totally agree with oriettaxx: nothing beats the supervision of an experienced professional. Automated tools are much like AWS... when automation fails, cost start rising again!
Our experience is exactly the same as per your suggestions: we eventually switched to a set of properly configured (by a highly skilled and not so expensive pro) bare metal servers at a well known EU data center, and a few additional VPCs for commodity services that we might want to change more frequently. Was a new life both for money and peace of mind. Each time a receive a bunch of emails from AWS for the billing of a very small service still hosted there my heart starts beating fast. Because they like writing looong messages and duplicates, with plenty of details about your service and bill, and many thanks and everything so difficult to understand. I'm not blaming AWS of course: it's a legit business model, I don't particularly like.
Your mileage may vary... but not so much actually unless you're in a highly variable type of business, with real need for constant change of configuration or resources.
ZF is among my favourite companies in the realm of automotive and transportation in Europe, when it comes to transition to EV: used to be mainly into mechanical transmissions, had to switch to electronics with an impressive speed, now trying to leverage their mechanical background in new paradigms. If everything goes as expected this will become the next management model to be studied and narrated!
Worth noting that Zeppelin heritage of inventions and mechanical systems still lives in a few corporations, notably the multinational ZF (https://www.zf.com) that serves transportation industry with mechanical transmissions and electronic systems