They give permission to modify their computer/device, but obviously there's an implicit trust that it isn't going to do something horrifically bad.
Trusting a builder to come in to your home and change things- you'd be pretty angry if they took down a supporting wall to put up a new light fitting (and you'd probably have some legal comeback).
> I would almost definitely struggle to get excited about it without the human element
You'd have teams in "pits" monitoring their vehicles live. Those reactions will be raw and humanistic.
When the vehicle comes in for a "pit stop," the team--in addition to doing mechanical maintenance--could be allowed to tweak the code, e.g. based on strategic observations of other cars' behaviours. To keep it interesting, one could mandate--to make up for the electronics in the car--all "pit stop" labor be completely manual. (Any code changes could be taken onto the track on an unpowered drive.)
I think your post just helped me understand why I never was interested in sports. I cannot get excited watching other humans doing heroic stuff.
This would not change for me if it were AI's with identifiable characteristics doing the activities (driving). With suitable marketing maybe real sportsfans could get behind (hypotheically) Team Waymo's AlphaRomeo Zero. Especially with an e-sports tie-in. Imagine racing, and thereby helping to train your (AI) hero on a simulator.
I like also how the README disagrees with itself several times on what tech it's using :D
> Angular(4.2) E-Commerce front-end framework for spreecommerce
> built with ️ using Angular2, Redux
> built with ️ using Angular 5, Redux/ngrx-store 4
> Current version of Angular is latest release 4.0.0.
I don't mean to sandbag the project at all, it looks good (I haven't really dug into it yet)! But would be nice if the README could decide on what it actually is. :)
Redux is a paradigm for handling data flow / application state in an application, whilst Angular is the framework running the application.
They're not mutually exclusive :)
Without using something like Redux, you can get by just fine for small apps (and arguably it could be more of a hindrance and over-complication than a help), but for anything more serious it can help a lot.
Similar acceleration figures to a litre sportsbike (though the new Roadster takes it to a faster level again, but still in the same ballpark).
The acceleration is mind-bendingly fast at first, but after a while, you get used to it and it just feels kind of normal. I can't imagine the new Tesla being any different.
Not to play down the achievement at all, those stats are amazing! But highly doubt there's a health risk associated with some mild longitudinal G forces, assuming you're in otherwise good health.
A few places have reported this, but it's slightly misleading as what they've actually said is they'll stop making "gas only" cars by that date. So, a mix of hybrid or all electric.
That might have been what you meant, but just pointing out that it's not necessarily "all electric".
I've had all of these problems where I've had to roll my own solution in some way.
Whether that was trying to get source maps to work when compiling + minifying via Google Closure and Webpack, or using Babel and Webpack back when the underlying source map util (I forget the name) didn't support certain things and having to fudge it myself (I forget the specifics).
They worked, but they were fairly brittle.
Now, tooling seems to have been improved a lot and using things like `angular-cli` means I don't have to do any of the setup anymore and I haven't had these kinds of problems in a really long time.
Ok, the delay from output to showing the source map is still an issue, but it's not one I find a problem. A few seconds after page load is acceptable to me before going digging through the source, and any breakpoints set in the source files continue to work.
Overall, for me, the weak point wasn't the source maps themselves, but the idiot setting up the build tooling to make them possible (me). :)
If you're in the UK, have a look at Monzo. Not a credit card, but very useful to use abroad. They don't charge a transaction fee when abroad, and the currency conversion is tracked to the MasterCard rate (whereas other providers tend to do card issuer + their own cut on top).
I'm a Monzo user and really unhappy to find this out. I spend most of my time in mainland Europe and the free transactions and no ATM fees are the only reason I am a user.
Can anyone comment on how Revolut compares? One pain point is that I always get asked if I want to pay in GBP or EUR, or even the cashier selects without asking me, in which case I get massively ripped off if they select GBP. With Revolut will the card look like a EUR card whilst travelling in the Eurozone?
I just used a Revolut card during a two week trip around Iceland. It worked fantastically well. Iceland's interesting as some places charge in Krona, some in Euro, but in either case I was charged the live mid-market rate to the GBP with no extra spread or fees.
You're also allowed to withdraw roughly £200/month worth of cash (any supported currency) without any fees. Beyond that there is a charge, I can't remember how much offhand but it's not too crazy.
The one problem I had with the card was at their petrol stations. Most are self-service and require the card to be pre-authed before the fuel will start being pumped. Revolut doesn't support this so I had to use another card or find stations where I could pay in store.
It's only for ATM withdrawals. If you are in first world country where card payments are well integrated this is not issue for you. Granted, in many developing countries you need cash so this will be issue.
I'm from EU (Slovakia) and not that far from Germany but surprisingly I have never been to Germany (not counting transit when I traveled through Germany in a train/bus or had to change flight) for some reason. I have always wanted to go but somehow I find places I want to go to more all the time so my travel to Germany keeps getting pushed down the list :D
… and bakeries, my god. I haven't seen a single bakery that accepts cards (EC or credit). Wanna buy €30 worth of cake to bring to work for your birthday? Nope, cash only.
From my experience though, Monzo has been much more reliable when traveling. It works in much more places in Asia for example. I traveled around Asia for a while before with my TSB UK debit card and it was getting declined almost everywhere, even in big cities like Hong Kong or Taipei (and yes I called TSB and told them I will be traveling Asia for few months in case they have some restrictions on debit cards in place, didn't help at all).
It got to a point I had to open local bank accounts and do wire transfers from my UK bank account to local bank accounts and use the local debit card. I just couldn't get my TSB/Lloyds card to work anywhere except high end western shops like Apple Store.
Hmm, that's surprising. I have traveled a lot in Asia (never to Australia though) and from that experience I know a lot of Asia is still cash based but Australia I'd expect every coffee / convenience shop to accept Visa/Mastercard.
That is fascinating. As someone who lives in Sydney's outer suburbs, I simply never need cash. For anything. It's almost the exact opposite of Germany, where I lived for most of the last 5 years.
For sure many coffee shops and convenience stores accept card, but I definitely find myself having to pay cash quite often (just for instance, the laksa place on Hunter street).
From Dec 18 Monzo will start charging fees for cash withdrawals abroad though. Which is relevant for people traveling to cash based countries (many in Asia) where cards only get accepted in high end stores and restaurants.
Testing the change is one thing, but if the original people were hired and asked something very similar, you have an existing group selected based on that characteristic and so will likely do well.
e.g. if you have always done a whiteboard interview, then you've selected for people that do well in that type of scenario. Changing the question but keeping the format will likely just prove that those people are still suited to that type of task, but not that an otherwise good hire will be filtered out.
I'm not against whiteboard interviews or similar, but just pointing out that selection bias is an important factor here if you're judging effectiveness by comparing it to results for existing employees.
I disagree that there's no positive effect. A difference in code styles can introduce cognitive load, though naturally the actual effect will depend on the individuals involved, and the actual differences (for some, I agree it could be a non-issue).
> Hopefully, you feel as passionately as I do about your own stylistic choices. My approach works best for me; but, it's not for everyone. And, clearly, other people's choices don't thrill me. It's a completely subjective matter.
I do not. I do have preferences, but I'll let them go quickly in favour of following a standard convention for a given project. I care more about consistency than my own subjective opinions on code style.
I would agree that manual code style checking is painful. I've previously used jslint, eslint, tslint, etc. and I always forgot to run it locally, and then get frustrated when it inevitably failed during CI. There's tooling to address that (syntax highlighting in editors, git hooks, etc.) but it doesn't completely alleviate the problem.
Personally, I quickly adapted and the initial friction of adjusting my workflow (and co-workers theirs) meant a more consistent code base. I was pretty happy with that.
Lately, I've been using Prettier.js that runs on save, and frankly I think it's fantastic. I don't always agree with the specific format it's chosen, and there's at least a few things it doesn't handle (e.g. superfluous new lines), but for the most part I no longer need to think about what my code looks like (stylistically, anyway).
A lot less cognitive load, more consistent code base.
Trusting a builder to come in to your home and change things- you'd be pretty angry if they took down a supporting wall to put up a new light fitting (and you'd probably have some legal comeback).