717 karma · joined August 18, 2015
https://en.wikipedia.org/wiki/Ode
An ode is not a tribute, it is a particular form of verse. I guess people get confused because the word sounds like "owed", or something.
"It was a cold Wednesday, with the wind blowing from the north..."
I'm curious if this is commonplace, and if its native audience find it irksome in the online medium. I can understand this style in print, but very often I click an HN link, and hit back before finishing the first paragraph as it becomes clear the article is not written in the pyramid style.
Sometimes one needs to be specific about the nature and severity of the slur used.
Given that it's HTML/Markdown, it's great to use in a team with version control. I know folks that have extended it to allow SVG animations.
I cycle through the streets of London every day, BTW, so I'm not suggesting that it's lack of recognition ability is a good thing.
Autopilot 2 keeps you in lane, does traffic-aware cruise control, and can do lane changes. That's it. No more, no less.
It sometimes gets spooked by shadows. I've had it brake sharply when going under bridges on the motorway, because of the shadow on the road. I've had it mis-read lane markers (in understandable circumstances; the old lines had been removed but the marks they left still contrasted with the tarmac).
If anything, I find Autopilot 2 to require too much hand-holding - literally! I rest my right hand gently on the bottom-right of the wheel when Autopilot is engaged, resting my wrist on my knee, which is also how I drive regular cars on the motorway. This isn't enough for Autopilot to think I've got my hands on the wheel, so it's constantly bugging me, and I have to wiggle the wheel to tell it I'm there.
Apparently some Model 3s have been seen with driver-facing cameras. Eye-tracking seems like a much better solution to me.
I love Autopilot. I recently had to drive ~500 miles on motorways in a thing that explodes ancient liquidised organic matter, and it was an absolute chore. Autopilot is ace when used as intended, and great in traffic jams.
The Mercedes S 350 is so much more sluggish than either my Model X or my Renault Zoe. Put foot down, wait half a second, and make a ridiculous noise in the process. I have to use the brakes way more often because of the lack of regen, too.
I am utterly convinced after 4 years of EV driving that 90% of drivers would switch to EVs for life, if they got to try one for a few weeks.
Driving the Merc feels like using an HTC Vario compared to an iPhone.
https://en.wikipedia.org/wiki/Solar_power_in_China
also:
My Tesla Model X charges in similar amounts of time, as whilst the supercharger outputs more power, the battery is bigger.
If that's really accurate, then I'm staggered at how much energy folks must be using to keep cool, and makes my efforts at saving energy seem paltry in comparison.
I've only been able to get the Model X because I've been irresponsible with money, and because we IT folk get paid more than we're worth to society.
That gives the Zoe a charge-time of just over three hours (as we have a 22kWh battery) versus over 13 hours for the Model X. That's 35 miles of charge an hour for the Zoe, and 21 miles of charge an hour for the Model X.
The Zoe can fast-charge at up to 43kW on motorway service stations, whilst the Model X and charge at 120kW. In the UK there are way more locations with fast-chargers the Zoe can use than there are Tesla superchargers.
People get far too excited by Tesla's brand, when there are really competitive EVs out there.
Feel free to AMA about EVs or how mine compare.
BDD in particular is tricky, because beyond the level of abstraction of the engine, you don't really know what you're building. How do you express that a thing should be fun, or weapons reloads feel punchy, in a BDD spec? How do you automatically test that?
Games code exists purely to elicit reactions in human brains. We don't have the technology yet to examine the desired state change in the target system.
Regular apps have the same problem, but with less expensive assets and less iteration. "As a user, I should feel that the login transition is slick" is a spec I can imagine that is UX-related. However, we can probably all agree on what slick is, and failing that you could user-test it to prove that the implementation is acceptable. A game is made of many complex adaptive interacting systems, so every change needs subjective validation.
On the subject of complex adaptive systems: many games feature them and so exhibit fundamentally unpredictable emergent behaviour. This can be hard to test for.
The most testing I've done in a games project is to figure what it is you're trying to build, then unit test the implementation when you've worked out if it's fun.
https://github.com/EngineerBetter/concourse-up
It'll give you a working, upgradable, auto-healing Concourse in one command.