CiaranMcNulty

I don't believe a pendulum's period is affected by its momentum at any point in its arc, just the length and its mass.

Given Tesla announced a 90kWh pack yesterday I tend to agree

You kids... I was the king of <MAP> back in the day

The website gives zero information about which areas this is available in (Unless it's Columbia from the TLD?)

Maybe you are supposed to guess from the area code?

This article is just plain wrong on a number of points. They are wildly extrapolating from a tweet. "Ending range anxiety" could be anything from performance improvements, to more accurate routing, to a better system for finding charging points.

"Tesla similarly upgraded its Roadster electric cars last year, expanding their range to almost 400 miles between charges via an over-the-air update"

While that would be incredible if true, it is not. They have announced the availability of a physical battery upgrade for the Roadster that includes a complete battery swap, drive train improvements, and other stuff derived from the Model S research.

This is ridiculous, CNN aren't even reading their own linked articles.

By regularly redeploying or re-imaging. Exploits can only live for a certain timescale + you can lock down nearly every entry point (no need for SSH access for instance).

I'll try and summarise it.

Ubiquitous Language is a term used in BDD and DDD and just means 'the shared language that you build with non-technical people'. It largely involves using business terms as much as possible, but often you have to try and agree some naming when talking to non-technical folk to resolve ambiguities. UL is not a technical concept, it's a way to focus on how you're expressing concepts in conversation.

In BDD we use this shared language to have conversations with customers about requirements, in the form of examples. In DDD we use a shared language to have conversations with customers about business process and rules. This article is bringing those two approaches together.

The stuff at the end is showing how the internal domain modelling (class naming, method naming, argument choice) can be taken directly from the conversation you had with the customer when you've had that conversation effectively. The significance is that the 'modelling' effort happens less in the developer's realm and more in the collaborative realm of customer communication.

Disclaimer: I work with the author of the article, use these techniques, and profit from their adoption

Even if it's not stored at their end in plaintext it's a security issue that it's emailed in plaintext.

It also stops most Polish people using their surnames as passwords ;-)

Slack is IRC expanded, rather.

I actually use Slack via an IRC client sometimes and there are a lot of benefits.

As mentioned in the article, the USA spends more per capita on healthcare than France, so it's not as if they're achieving this better service by being incredibly lavish with spending.

Nothing aside from the UI, really. Well, as long as you're not using Basic auth).

If browsers handled HTTP logout nicely, by displaying a prominent logout button somewhere, then developers' jobs would be far easier.

He's hopefully using screen width (window.screen.availHeight) rather than browser width (window.screen.height)

That's not the case, you have to either come back and pick up your battery on the way home, or you pay for the new one.

It is however very encouraging for people worried about battery performance that you can get a new one pretty easily.

It's hard to do key removal that way, you end up reasserting all of the other fields in that subdocument, whose values may have changed since your last retrieval.

There's also some value in the patch format looking somewhat different to the main format, to avoid confusion.

Well said.

It's in some ways quite anti-RESTful for a consuming client to start to try parsing a URL semantically. "URL building" is not something a client should be responsible for, it should be (semi-)blindly using URLs the service has provided for it.

People are way overreacting to this.

HTML already lets arbitrary applications register themselves as protocol handlers at the OS level, so for instance spotify:// links get handled by the correct binary.

All this does is let a website register itself as the handler of a particular protocol. This has obvious uses for instance letting mailto: be handled by Google Mail if the user wants it to be.

I'm not sure why HTML5 has to have a whitelist of protocols that allow websites to register as handlers - it seems like an overhead.

Throughput to S3 is ok if you initiate a multipart upload and then do several parallel chunk uploads.

", I can't push my changes for others to review, or review pull requests. I can't update and pull in the latest changes, or checkout branches to help someone with a bug"

You can do all of these things if your colleague has that branch checked out - it does require remembering some pretty poorly-named CLI flags though!

Historically, you can't serve multiple sites from one IP address (i.e. named virtual hosts) and use HTTPS. The reason for this is that the hostname of the site is included in the HTTP request from the client:

  HTTP/1.1 GET /
  Host: mysite.com

By the time the server has decoded and read this header, you have presumably already started the secure connection, so the server has to have already selected which certificate to use for the session.

Workarounds are to have multiple IP addresses on your box with one cert per IP, or run the server on multiple ports with one cert per port. In both cases this enables the server to know which certificate to use from the underlying connection properties, and not wait for the encoded traffic to start arriving.

SNI (Server Name Identification) is an extension to TLS (Transport Layer Security) that essentially adds the hostname into the SSL negotiation, so this cert can be selected by the server in advance. It made it into OpenSSL implementations in the mid-2000s and is reasonably widely adopted.

Legacy libraries, Internet Explorer <=7, and Windows <=XP won't support it so it's not quite ready for mainstream use. Give it 5 years or so...

It would be interesting to try the same attack via email attachments, i.e. get Bob to check an image with a contract, then forward it to Alice saying 'this is approved' but the wording of her contract is different to the one he read.

Out of interest, do you tell people in advance?

I've interviewed a person with a stammer and the recruiter had mentioned it beforehand, so we got over the initial discomfort very quickly and carried on as normal.

And yes, £15k with 3 years experience is LOW.

Can you explain how remote working would work out in the Engineering jobs? They mostly seem to be Brooklyn based so how would you feel about applicants from, for instance, London?