• 0 Posts
  • 47 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.)






  • If I’m not going far, not driving or not planning on spending much then yes, wallet stays at home.

    Otherwise, if I’m driving then I’m taking my driving license with me (you never know), if I’m making a purchase over the contactless limit then I need to take my actual card with me anyway, or if I’m away for a longer period then I might need cards that I don’t have linked to my phone (like my corporate card - like fuck am I putting that in my phone).

    And for all that, I’d rather have a wallet instead of just a loose amalgamation of plastic in my pockets.










  • 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.


  • As others have said, 100% a leak.

    I would advise to stand on a chair or stepladder underneath the ceiling and check to see if it is still level. If you see an obvious deformation around the stain, this will be being caused by water pooling on top of the ceiling plasterboard. In which case, once the leak is sorted, you will likely need to drain the pooled water, cut out the damaged section, replace it, then replaster and repaint.

    We had exactly the same issue in our last house. It was in a difficult to see spot hidden behind our kitchen cabinets. We only realised the severity of the issue when the ceiling boards gave way and fell on my head.



  • I’ve switched both my laptop and desktop over to Linux (Bazzite and Fedora respectively) in the last 6 months.

    The last time I tried to daily Linux (over a decade ago) I ended up switching back eventually, but this time I really don’t think I’ll need to. All of the games I play most often work perfectly, the dev tooling is even better than it is on Windows, and the hardware compatibility side has been completely flawless.

    Gone are the days of having to hunt down obscure Linux drivers for your touchpad or webcam. Everything just works out of the box.



  • The main issue was a catastrophic failure of the VC_FRONT module which is one of the critical onboard computers that manages things like the 12v battery and low voltage power distribution (basically a “smart” fuse box). Without it the car is bricked and cannot be driven.

    That took several weeks and some back and forth around the extended warranty to resolve, and then even after that module was replaced, on my first drive after the repair it went straight into limp mode and then spent another week at the service centre having that diagnosed.

    During this time I decided it might be time to start looking for a new car, ended up selling it a few months later and took delivery of a new Polestar 2.