Automotive actually uses ML in plain c with some inline assembly sprinkled on top run run models in embedded devices.
It’s definitely out there and in productive use.
99 karma · joined January 31, 2019
It’s definitely out there and in productive use.
The tickets often don’t have meaningful information in them apart from ‚for details see the attachments‘
Attachments are often either not uploaded or nowadays we do not have read access as they were created by a different team working for a different customer but forwarded to the ‚central backend team’ and for know how protection purposes we are not even allowed to see the attachments.
Effectively resulting in the information that is available telling us: ‚we did stuff‘
You become the boss or responsible for some product. If you decide at the beginning to start off using Rust or rewrite some ancient, unmaintained library using Rust, then you prevent people like your cowboy developer to mess stuff up with this category of faults.
Either you would not hire him in the first place because he never came to grips with Rust so you only end up with developers on your team that understand and actively chose the tradeoffs that Rust offers.
Adding support to re-flash our control unit „over the air“.
I wanted to prepare for the next interviews sometime mid last year but lost the motivation. It is very easy to skip the interview-prep after a full working day.
Best to do a short programming riddle after waking up when the mind is still fresh.
2.) Raise the regulatory bar to prevent startups from entering your field.
Milk whatever half dead infrastructure you have and people depend on.
Oh and raise prices every odd year while still not investing in the rotten infrastructure. Somehow investors need to see growth and dividend payments.
Due to 1.) there is no competitor left that could offer a better service. People cannot simply switch.
Die to 2.) you are not in danger of ever having to face situation 1.) again.
Job of the government is to not let 1. and 2. happen.
They go the boring path. Work together with regulators. Prove to them that whatever they are doing is actually save to use. Don’t oversell to their customers.
They go the way of building and retaining trust - with customers and regulation bodies.
.de has more weight than .net or .com for most people in Germany.
At some point in time it is just not profitable anymore to provide further FEATURE updates for free anymore.
If you don‘t find buyers/renters how will you manage to pay off your investment credit you took out at 95%credit rate while only covering contract signing fees at ~1% interest with 10year stable interest.
Once interest is adjusted after 10years to 4-5% you (property owner that can’t find any high paying renters) are fucked
This is something I am guilty of too often. I get lost in fixing the minute details and edge cases that might come reality under very special circumstances only.
It is good to step back once in a while and focus on whether the thing you are working on actually has an effect on the user experience or user interaction with your product.
Don’t lose the big picture out of sight for all the small edge cases
Not much has changed over the years ;)
Use whatever headless buildscripts you fancy (make?!) to build your project.
Problem solved.
critical stuff has to be defined per application.
For controlling aircraft engines or car engines I for sure as hell do not accept unreliable packages.
That’s why contracts exist that hold software suppliers LIABLE for faulty software.
It’s horrible. Some good guys but mostly Indian freshers that get burned in 1-2 years.
Time zone difference sucks.
Zero understanding of the product.
To get the proper end result you have to specify the work chunks on such a deep level that you are faster doing it yourself in the first place.
I hope that instead of aiming further down the abstraction layers, they instead aim up and try to get the hang of macro level stuff, metaprogramming, abstractions which I most often put off as "that’s just a fad"
If something like containerization or container orchestration sticks around for 5 or 10 years I'll maybe take a proper look at it.
Until then it is ‚just a trend‘ and takes mental space I feel spent better digging down. Because that’s where software is interacting with hardware (the real world). That’s the abstraction layer where you can 'actually move the world', where goods are created.
Not everybody is capable or experienced enough to move across different abstraction layers and have a proper mental models for each. SOMEWHERE you will probably have to draw a line.
Some people draw the line at 'writing software'. Execution target (understanding the hardware / runtime) are out of focus for effectively all programmers. I think partly because languages, tutorials, bootcamps don't bother to dig deep there because 'the compiler will take care'.
It just is not teached that way. What do you mean with Solaris? Sun? PDP? It is just a computer. Java is cross platform. How it does that? Thats the JVMs job, not my job. I just write the software.
At my place the abstractions start at high level user facing code, reach down into the hardware interface (driver) code and down to the actual electronic circuit design.
EVERYWHERE something can go wrong. In case the circuit deteriorates too fast you need to get the material analysts to "debug"
Rule of thumb is: there is always one layer of abstraction below you where stuff can break which feels like magic to you but is fixed with a glimpse from the lower level guy
If the system gets faster over time, even better. But I cannot imagine huge adoption unless the system gets actually reliable. I am pretty much in favor of the Waymo approach.
Only when the vehicle computer detects a known object on the road that it knows should not be there it is applying brakes or trying to steer around.
I would feel safer if the algorithm would assume the negative case as default and only give the „green light“ once it determined that the road is free to drive on. In case of unknown (not yet supervised) road obstructions the worst needs to be assumed.
That’s where the ‚unexplainable‘ crashes are coming from. Something the size of an actual truck is obstructing the road. But couldn’t quite classify it because the truck has tipped over and is lying on the road sideways. Not yet learned by the algorithm. Can't be that bad, green light, no need to avoid or brake.
In languages like Java that want to hide everything memory related I also was struggling with grasping what a function really is. Is it even allowed to return a function?
Languages that hide memory locations and direct memory access are one of the reasons that some programmers are struggling with functions returning functions.
Each and every build tool should be version pinned so that two build runs today and 4 years ago produce the same (hex neutral) executable.
Otherwise debugging issues becomes a nightmare...
The past 3 years I was able to leave for the day with no unread messages.
The last few months I am unable to keep up. ~20 unread messages and several unanswered Skype chats each day.
Other team members also noticed an increase in the amount of mails.