I agree fully. Having tried to get my mind around d3.js, there are *a lot* of leaps of understanding in coming to up to speed. Watching someone who provides a narrative how they get from a to d by verbalizing b and c will help immensely. The docs really go just from a to g.
As a viewer, it's about learning technique and thought processes. Identifying issues, attempting a particular thought process, only those that provide a strong narrative to the work they are doing will be likely "stars". Watching how good programmers (assumption) deal with their environment and the typical problems they face. Seeing how people top down or bottom up write code is very interesting (within limits).
As a broadcasting coder, it takes a fair amount of personal confidence to do it, particular in this field. Having to verbalize what you are thinking and how you are considering the problems in front of you is actually quite challenging. Those that do well in the broadcasting scene will most likely be strong professionally as well.
That said, I personally don't understand the fandom about broadcast games to the level that it has taken. I get the benefits, but I don't get the market.
Tin foil hat on. It came to me last week.
Google has recently released Project Fi. A project/product (is project a codeword for beta now?) that will allow seamless transition between 2G/3G/LTE and *WiFi* for increased coverage and strength.
Project Fi is bandwidth charged, independent of data link being used - so while the underlying carriers (T-Mobile & Sprint) may charge wholesale for data, google will effectively get the bandwidth at "Google WiFi" for free - meaning that the data charges are a lot more profitable when going past a Starbucks, in NYC, etc. Although unproven, google might actually have meaningful alternate revenue sources from this model.
This is not fundamentally different than Xfinity's wifi sharing - except google is going for the Free WiFi in the Starbucks, NYC, etc. B2B is a lot more pragmatic, and a lot easier to enable.
Now if only Project Fi worked in a phone that was in the $2-300 range, I'd probably give it a go. But the Nexus 6 is too big and too expensive. Hopefully the invite won't expire.
From TFA, it is a design patent - aka Trade Dress.
From http://www.theglobeandmail.com... , the actual complain seems with merit. The frets (metal lines), key shape (rounded corners) and space bar seem to be pulled entirely from the Blackberry Q10. It's as blatant as the typical Chinese typo-based (Sony vs Somy) ripoffs.
If you saw a phone with a the Typo keyboard, it would be reasonable to assume that its an extra tall Q10. That's what Blackberry has sued about.
tricked into viewing a piece of American culture ruined and rewritten right in front of their very eyes.
It's an Australian movie, set in Australia, with Australian actors, Australian Director, Australian Writers.
Piece of co-opted Australian culture... They even drive on the left side of the road - check out IMDb for shots of the yellow interceptors...
Hollywood never co-opts other cultures do they...
EU privacy laws are fairly painful for US companies to comply with. To do business with EU individuals, Personal Identifiable Information needs to be handled according to a set of rules - http://ec.europa.eu/justice/da...
It is often simpler for Amazon deployed companies to set up in the Ireland AWS zone.
As others have mentioned, most foreign SIGINT/COMINT agencies can't gather intelligence domestically, so it lowers barriers. Ironically US companies that want to deal with EU customers may end up moving everything to Ireland. However this allows the NSA to gather intelligence indirectly on US citizens.
AT&T does - phone support has their playbook, which doesn't go very far. Their online customer support actually was very helpful.
My story getting IPV6 on AT&T - http://use-cases.org/2015/01/1...
If your router enables IPv6, your devices have IPv6 access - no endpoint changes necessary. Current versions of most Operating Systems actually prefer IPv6 but fallback quickly. So it is likely to be turned on transparently.
There is no INTERNAL_IP6_ADDRESS, there is just an IP6_ADDRESS. The firewall blocks or permits dynamically (likely stateful connection management). The
The biggest issue for home networking is the lack of management of the router/firewall itself. You can't port forward (no config UI), you can't permit specific ports in most current home router implementations. However, configuration of ports and so on are not something that the vast majority of users know or care about.
With the current incantation of Amazon Web Services (VPC),
IPv6 support is currently not available for load balancers in Amazon VPC (EC2-VPC).
So there goes lots of the internet....
2: Attackers can view your entire IP space. A simple nmap scan, then choosing what zero days to use... instant pwn-ership.
Hmm... Non-direct allocated IP on your subnet, 64 bit subnet, pwn-ership aint that trivial. Scanning a 64-bit address space (AT&T allocates a full
Welcome back to the internet of the early 1990's we all lived on the internet with real IPs, but were protected from firewalls... This whole concept of everyone on a Class C/B/A private subnet thing has only been around for a couple of decades.
The main difference tech people will see is that they can't ping an IPv6 address from memory. mDNS (as in xyz.local) will become the only way to access another machine with any sanity.
Monitoring DNS at home, most services are already mixing (with a preference, but quick fallback from IPv6). So I'd say that the major websites are already primarily accessed via IPv6. You won't notice it.
It'll just take years...
I have IPV6 at home (took some calls to AT&T Customer Support). I don't have it at work, the migration will probably start small network endpoints (phones (apparently t-mobile has already switch), and home networks).
Link local IPV6 is already fairly broadly available - it's the fe80 prefixed address on your ifconfig output. You should be able to ping other ipv6 addresses on your network (*nix to *nix).
Google's IPv6 stats page indicates this too... https://www.google.com/intl/en... has a peculiar comb effect for the last few years. Zooming in seems to give a bit more insight. Google's count of IPv6 connections has a full 1% swing over the weekends vs the week days. Due to IPv6's addressing method, each unique device on your network appears as a unique device on the internet, vs the NATed IPv4 that we all know and love. This would also have an accelerating increase in the number of unique IPs that are visible on the weekend. I know I use more devices over the weekend (chromebook, phone, laptop, table) vs during the week.
Open to other insights, but our homes will be likely IPv6 before our offices are. (Of course aggressive tech companies like google and facebook are likely already IPv6).
The same thing happens with the hope for the "next generation" product solving all the ills of the current generation. Or the assumption that the code you have inherited was created by fools a number of years back.
The reality is that software has a set of maturity related bugs and a set of structural, intractable issues that are related to the design and architecture of the system. Each piece of software has it's unique set of intractable issues.
Software that has been in production has typically reduced it's maturity related bugs. The software built on top or that integrates with it is built around those intractable issues. When you move to a new piece of software - either a new architecture or the "groundbreaking ng version of XYZ", you end up with swapping a set of *known* intractable issues, for a set of *unknown* intractable issues plus a set of maturity related bugs.
Similar to TFA, the risks of old+known vs new+immaturity+unknown needs to have another factor similar to "value-add". If the value-add *really* adds a lot of stare the risks in the eye and march forward. If the value add is marginal, make sure the meta-benefits (performance, maintainability, etc) are clear and understood, otherwise you may be facing a train wreck of an upgrade.
Seen it many times, always wary of the ngXYZ project...