• 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: October 15th, 2023

help-circle
  • These definitely exist. They are typically referred to as ‘compliance cars’ - i.e. the manufacturer is obligated, usually by regulations, to produce an EV, but they don’t want to spend money designing a new platform for it - so they take an existing model, rip out the engine, cram a motor and batteries wherever they will fit and call it good. Examples: Volkswagen eGolf, Fiat 500e, Mercedes B Class EV. Ford Focus Electric…

    However, doing this means you are constrained to the shape of the combustion vehicle it is based on. So the aerodynamics may not be optimal to get the best range, you may have a transmission tunnel taking up space in the interior that is no longer necessary, directly swapping the position of the engine and the motor/inverter means you lose the opportunity to repurpose the front of the car for additional storage - ultimately it ends up compromised in one way or another.

    If on the other hand you design the platform from the ground up to handle an electric drivetrain then all of these points can be taken into account.

    (And regarding cars in general becoming rolling computers: this is not an EV specific issue, unfortunately.)










  • I have witnessed companies make this exact mistake before - they have a legacy system written in $LanguageA that they either cannot find developers to maintain, believe is badly written, or does not support some new feature they want to implement (or some combination of the three) - and decide to solve this by taking the existing codebase and porting/transpiling it to $LanguageB (which is more modern, performant, is easy to hire developers for, etc) - without actually rewriting or rearchitecting anything.

    What they are actually doing is substituting one kind of tech debt for another. The existing code that was poorly written and/or not well understood is now just bad code written in a different language. Fixing bugs or implementing new features now takes just as long, if not longer to account for the idiosyncrasies of how the code was ported.

    And now this is being done by AI with even less oversight than usual? Recipe for a maintenance disaster.