EPITEC’s Post

🚗💻 The two key aspects that #opensource must facilitate for the #automotiveindustry are fostering collaboration and advancing code that generates value for multiple product companies (OEMs). The Eclipse uProtocol has the potential to achieve both of these goals. Check out this article and learn about the Eclipse uProtocol project, an initiative that aims to provide a unified approach for integrating diverse technology domains within SDV architectures. Join the fast-growing developer community and be part of shaping the future of SDV ecosystems. 🌐🔧 👉 Read more here: https://bit.ly/4c2i8Tg #SDV #EclipseFoundation #uProtocol #SoftwareDevelopment #TechnologyIntegration

#Sitecore #Headless #Development #Tips & #Tricks with #NextJs:  - #Vercel automatically supplies you the #GeoLocation along with a request #NextJs will use the NextRequest object when passing around request objects. You will probably be familiar with it if you have used route handlers: export async function GET(request) { // request param is the NextRequest return Response.json('...') } On Vercel you automatically get the geolocation added to the request: - request.geo.city - request.geo.country - request.geo.region - request.geo.latitude - request.geo.longitude P.S. If you find this useful, please save and repost this tip to help colleagues!

Did you know that you can automate processes using scripts in Bluebeam Revu? With a click of the mouse, you can add stamps, delete pages, and flatten markups; you can even do all this at once! In Bluebeam Revu, scripts let you automate complex processes and multi-step tasks. Revu offers a variety of default scripts, but you can also make your own to perform any function needed. This article will cover how to use Script and Batch Script to automate processes using Bluebeam Revu. #bluebeamrevu #bluebeam #revu #scripts #pdf

#Sitecore #Headless #Development #Tips & #Tricks with #NextJs:  - #Vercel automatically supplies you the #GeoLocation along with a request Next will use the NextRequest object when passing around request objects. You will probably be familiar with it if you have used route handlers: export async function GET(request) { // request param is the NextRequest return Response.json('...') } On Vercel you automatically get the geolocation added to the request: - request.geo.city - request.geo.country - request.geo.region - request.geo.latitude - request.geo.longitude P.S. If you find this useful, please save and repost this tip to help colleagues!

Are you looking out for solutions to execute cross platform automation where context switching between different platforms is of paramount importance?  Our Automation Test Lead, Zahid Umar Shah, shared his expert insights on how with the help of Ranorex Studio you can stop draining your QA bandwidth and embrace a paradigm shift in software quality.  Check out the full article for a detailed look at transforming software testing with the #Ranorex automation toolkit. https://bit.ly/41X7Yi5 Raghuveer Alapati, Nagaraju Asamani, Srinivas Alapati #TestAutomation #SoftwareTesting #IntelligentAutomation

https://lnkd.in/dXrZzd57 Very handy peace of codes for structured logging with Serilog.

#Labyrinth Global SOLUTIONS (USA|UK|UAE|INDIA) now at your tips...!!! #REST API #Polarion 22 R2 brings support for the greatly expected REST API. In this initial release, we #focused primarily on the support for the #REST API in the Polarion core, making sure we can deliver a robust new API that can provide a much-needed way of connecting Polarion to your #organization’s toolchain. #Covering Polarion’s features with REST API will be a continuous process. In this release, we worked mainly on the Work Items artifact. #Work Items with links, attachments, and comments are the most frequently used objects in #Polarion. So the REST API endpoints we are delivering cover these #frequent use cases – and enable you to utilize the #Polarion REST API right now in its very first version. #On top of this, we are also providing REST endpoints that cover selected use cases from the Live Documents, Live Reports, Projects, and User Management topics. In the next release, we #plan to focus on extending the covered use cases for Live Documents and Enumerations with Plans and Test Runs closely behind on our top priority list. For a complete list of available #REST API endpoints, you can use the Polarion SDK to access the Polarion REST API documentation, or you can #explore the Polarion REST API User Guide (available on Support Center) and enable not only the REST API itself but also our dynamic #Swagger UI documentation tool that allows you to visualize available endpoints and interact with the Polarion REST API directly – giving you the #ability to test it directly without the need to set up a development #environment. The #Polarion REST API v1 is based on the JSON:API specification. It #supports #OpenAPI and uses URI versioning and JSON Web Tokens (JWT) for authentication. #Siemens #plm #Application #polarian #Appdevelopment #Testing #Coding #Validation #healthcare #aerospace #medicaldevices #siemenspartners #automotiveindustry #manufacturing #lgs #siemenspolarionalm

#KubeCon EU 2024 here we come. DM for a live demo of what an automated developer portal can do for your engineering team. #platformengineering

🔔 𝐄𝐦𝐛𝐫𝐚𝐜𝐢𝐧𝐠 𝐄𝐯𝐞𝐧𝐭-𝐃𝐫𝐢𝐯𝐞𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: 𝐔𝐧𝐥𝐨𝐜𝐤𝐢𝐧𝐠 𝐑𝐞𝐚𝐥-𝐓𝐢𝐦𝐞 𝐚𝐧𝐝 𝐒𝐜𝐚𝐥𝐚𝐛𝐥𝐞 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 🌟 In the dynamic landscape of modern software development, Event-Driven Architecture (EDA) has emerged as a powerful paradigm that enhances responsiveness, scalability, and flexibility. But what makes EDA so useful? 𝐈𝐦𝐩𝐫𝐨𝐯𝐞𝐝 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐯𝐞𝐧𝐞𝐬𝐬: ⚡ EDA allows systems to react to events in real-time, making applications more responsive to changes and user interactions. This real-time capability is essential for applications like financial trading platforms, live analytics, and gaming. 𝐃𝐞𝐜𝐨𝐮𝐩𝐥𝐞𝐝 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬: 🔄 By decoupling components, EDA promotes loose coupling and high cohesion. Each component can evolve independently, which simplifies maintenance and enhances scalability. 𝐄𝐧𝐡𝐚𝐧𝐜𝐞𝐝 𝐒𝐜𝐚𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲: 📈 EDA supports horizontal scaling by allowing components to handle events concurrently. This scalability is crucial for handling large volumes of data and traffic in distributed systems. 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐚𝐧𝐝 𝐄𝐱𝐭𝐞𝐧𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲: 🔧 EDA enables easy integration of new features and services. Since components communicate through events, adding new functionality becomes straightforward without impacting existing systems. Example: Implementing an Event-Driven System in TypeScript Here's a quick example of how you can create a basic event-driven system using TypeScript and Node.js: Install the necessary packages: npm install eventemitter3 @types/eventemitter3 Create the Event-Driven System: 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧: Event-Driven Architecture (EDA) is a game-changer for building responsive, scalable, and flexible applications. By leveraging EDA, developers can create systems that are more adaptable to change, easier to maintain, and capable of handling real-time data efficiently. #EventDrivenArchitecture #TypeScript #WebDevelopment #RealTimeSystems #SoftwareEngineering #ScalableSolutions #DeveloperCommunity

Absolutely, the industry is leaning towards a more open-source model. This shift can already be observed in the approach of many large tech companies. Open source allows for increased collaboration, accelerates development processes, and encourages the sharing of valuable insights. A compelling example of this movement in the industrial automation sphere is the Ignition Exchange by Inductive Automation. It's a platform where users can upload resources for others to download freely. Vertech, for instance, participated in the build-a-thon organized by Inductive Automation a couple of years ago, where we created a dashboard application that is now accessible to everyone on the Ignition Exchange. There's a growing trend of professionals leveraging forums for knowledge sharing and code distribution. However, we are yet to see a full-scale MES application shared openly on platforms like GitHub. Given the trajectory of the broader tech industry towards open-source ideologies, I believe industrial automation will follow suit. This trend is advantageous as it saves substantial time in the long run and benefits the larger community, particularly in software development, where similar patterns recur across different manufacturing contexts. Despite this, we often remark at Vertech that industrial automation lags about 30 years behind the rest of the software industry in terms of procedures and methodologies. Source control, for example, is almost non-existent in our field. Unlike traditional software development that has used GitHub or similar storage repositories for decades, this is still a novelty in industrial automation. Over time, I expect this shift towards open-source practices will occur as more organizations begin to recognize its long-term benefits. On a platform and module integration level, I anticipate more open-source practices. However, highly regulated sectors such as power utilities might resist this trend due to legal and security concerns. Another important aspect to consider is the potential for reusability and the sharing of pre-existing solutions within an organization. For instance, when designing an MES system, engineers often go down a path of creating something new, without considering whether a similar solution already exists within the organization. Encouraging engineers to think about reusability and sharing solutions can increase efficiency and save valuable time. But this requires a shift in mindset and a commitment to treating solutions as reusable components rather than isolated, single-use code. This clip was taken from Manufacturing Hub Episode 119 - https://lnkd.in/egY9-x7J With guest - Addison Waege #manufacturing #automation #data #industry40 #digitaltransformation