Merging ISO Designer: Part 2
If you followed my previous blog post you will know that merging ISO Designer project files is something desirable when multiple developers are working on an ISOBUS project, but is …
If you followed my previous blog post you will know that merging ISO Designer project files is something desirable when multiple developers are working on an ISOBUS project, but is …
Conferences are one of those things you hear about and see all the cool swag from those who attended. After hearing about it for years, I finally decided to take …
The ECU-TEST platform, used for automated testing of automotive software, has numerous features that significantly simplify the process of testing the diverse hardware variants that today’s software is designed to …
“The fault…is not in our code, but in ourselves.” A while back, a colleague and I were lamenting the lack of a strong ‘craftsmanship’ ethos across the field of embedded …
My team works with a specific product that is hard to handle for several reasons. First, it has high visibility with the client because it is a large-volume selling product …
DISTek Integration has been heavily involved in ISOBUS development for a long time now. We have helped many clients develop and integrate custom VT solutions for their vehicles and implements …
In my work, I build Hardware-In-The-Loop (HIL) test benches. We connect prototype vehicle Electronic Control Units (ECUs) and their software to the HILs. The HILs replicate the various electronic actuators controlled and monitored by ECUs when they are connected to vehicles. We try to use the actual devices that would be used on the equipment, but there are a myriad of different reasons why this is not feasible for testing. A lot of the devices would take up too much space on the HIL. Some can be rather noisy when operating and others require complicated cooling systems to operate for extended periods of time. That is why I often create electronic circuits that will simulate the current feedback characteristics of the actuators.
Here at DISTek, we value collaboration, teambuilding, and delivering unmatched value. We provide our clients with dedicated engineering teams that provide unparalleled value by freeing our clients’ time up so they can focus on broader business challenges. Our proven approach is not only extremely beneficial to our clients but brings significant value and meaning to our employee-owners, as well.
Previously, in Part 2, we went over Git Branches and the HEAD. Let’s continue by starting off with Remotes and how to get your stuff to other developers or into a project.
When creating an application, one of the most difficult aspects is choosing a language/framework that will meet all requirements. The VT Anywhere team has learned this first hand, hence the title of the application VT Anywhere. VT Anywhere is split into two parts: User interface and Server. The languages of choice are JavaScript and Rust respectively.
There are tons of tutorials out there that show how to use Git, starting with easy things like cloning a repository and committing locally, then pushing your commit to the server. There are lots of sites and videos that will help you achieve a competent level of Git expertise – like this one. However, you may struggle with the interface and if you have problems, you may struggle to understand why and how to fix them. That is why I am going to explain Git this way: inside out, backwards and hard. This three part series is targeted for people who want to excel at using Git and deeply understand it. This is also intended for people who are willing to persevere a bit more than the average person. Lastly, this is for people who like to see the beauty in things and, trust me, Git is beautiful.