I believe that driving an old car for longer has a smaller environmental impact than consistently driving newer cars as the bulk of emissions is during the manufacturing process. I have no data to support my statement, it's just my hunch. I'd be very keen if someone with the right knowledge can approve or disprove my statement.
If we take as given that "decent quality ICE vehicles are proven to last at least 320k km", then after accounting for both vehicles that are less than decent quality, and vehicles destroyed due to accident, malicious damage or poor maintenance long before they reach that figure, then a fleet average of 200,000 km doesn't seem out of the question.
The same factors would seem to apply to EVs (except perhaps poor maintenance, but I am not knowledgeable enough about EVs to be sure), so for the purposes of comparison, I figured apples to apples would be comparing expected lifetimes of both assuming they are not abused or neglected.
It seems to me that they are using an expected lifetime (in the "expected value" sense) of 200,000 km for both types of vehicles.
If those factors apply equally and dominate the reasons vehicles reach EOL, then the expected lifetime not varying significantly between the vehicle types looks like a reasonable assumption.
Using the real expected lifetime taking into account the circumstances that tend to render a vehicle permanently unserviceable in the real world looks like the correct approach to determine how manufacturing costs are amortised over the vehicle lifetime.
the same busted (and hard to repair) body parts will occur in both. Think AC, window motors, lamps and switches, etc.
plus, none of the manufacturers seem to be investing in easily replaceable batteries. They'd rather you buy a new car. May as well right? the batt replacement is 60% of the cost!
The opposite is true - the manufacturing process is responsible for an average of 7-10 tonnes of CO2, while the same vehicle over its lifetime will emit more than 50 tonnes from the exhaust.
Moreover manufacturers have been reducing their carbon footprint lately. As an example VW reports that 70% of the energy the use in plants is provided by renewable sources.
That being said while emissions rules have been getting more stringent over the years, they're increasingly being followed through introducing EVs, not improvements in engine efficiency.
> As an example VW reports that 70% of the energy the use in plants is provided by renewable sources.
This is a great start, but not where most of the carbon embodied in a new vehicle comes from. The energy used by the VW plants keeps the lights on, air conditioned, and powers tools for assembly. Most of the carbon embodied in a car comes from the energy it takes to mine raw materials and process them into useful metals.
This pales in comparison to the 20 tonnes of fuel a typical car is going to work itself through throughout its lifetime. And all this fuel has to be first extracted and refined.
This seems to be the crucial bit that is always missing from these discussions. I don't doubt that the CO2 emitted in the assembly of the car is less than in the driving. But I'm curious about all the other environmental impacts (of which CO2 is just one small bit). The destruction of wildlife habitat, the poisoning of ground water, etc, that's involved in the retrieval and processing of the raw materials, on up through the chain.
It's about right if you grew up poor in that time period, and bought something secondhand. I was part of a small club out in the (impoverished) country where we were learning on DOS computers using Qbasic in like the early-mid 00s.
If I had to give an introduction to programming to someone with absolutely no prior knowledge, I might still use QBasic (or rather something like QB64 or an online interpreter) for it. The simplicity of the syntax and no required boilerplate for getting started really lends itself to it.
Author claims the computer had Windows 98 on it so I would assume it is second hand since you couldn't buy a new computer with W98 on it in 2008 either. Or as you say a typo or mistake.
Until 2012 I was using an old laptop, Celeron with 760mb RAM, running Lubuntu and Windows XP. It was very crappy, but allowed me to do some web freelancing (thanks Sublime Text, I miss you) and browse web in general (sure, one thing at a time. Sometimes I couldn't listen to music on Banshee and have a heavy RAM tab opened). That's what I could afford at the time. Today I got a powerful Dell laptop, don't care anymore about these micro optimizations. I feel like I'm betraying my old self, hah.
This has really annoyed me recently, I've had interviews with companies that expected me to do a test before even seeing them in person (following a phone interview) and their tasks mentioned I should spend around 8 hours on the test. I think this is definitely unreasonable.
I prefer longer interviews where you're working alongside your potential future colleagues. This way you can also find out if you actually want to work with them or not. Interviews should be a two way affair.
The phone and online coding exercises are called pre-screening. Their goal is not to find out if you're a good programmer, but if you can write code at all. This is to save time and see as many candidates as possible.
Yes, i get the screening process; but asking a candidate to spend 8 hours on implementing a client library for their API at the beginning of the application process is definitely unreasonable. It's not a coding exercise, but a full blown deliverable.
I'm really looking forward to this. After 10 years of programming in PHP and maintaining loads of legacy projects I've come to greatly appreciate explicit definitions and strong typing. IMHO being explicit always increases maintainability.
Wow. I've got 8GB high speed 4G for £30, and I had the phone thrown in for free (Pixel 2)! Incredible how data varies so much in price from country to country.
It is a simple solution for very common problem: styling a CSS button. There are many CSS buttons libraries but they usually force you to use their style or size. That is why this is interesting and simple solution born with my necessity not to recode and reinvent the CSS button for every new project.
