HN user
Feel free to email me at david.brandt@gmail.com
Kinesis isn't a good idea for low-latency queueing. It can handle high throughput, but it can often take anywhere from one to ten seconds for a message to make it through the queue.
Given that DynamoDB can reliably write in the 4-5ms range, a kinesis queue may not be necessary. Unless the point of the Kinesis layer is to keep the cost of DynamoDB provisioning low?
What you're describing reminds me a lot of Padelford Hall at University of Washington, another product of the late 60s.
(http://www.washington.edu/alumni/columns/june07/content/view...)
It was awful, actually several "wings" in one building. It was possible to get locked out of the building on a walkway between two wings, with no other exits. You would sometimes have to go through one person's office to get to another office.
The theory when I was a student there was that university construction in the late 60s was obsessed with dealing with civil unrest - psych buildings with riot-proof windows, admin buildings with confusing layouts, an open square covered in bricks that get slippery when hosed down, etc.
I could see Amazon using this as a NYC media presence, as much as a store. They could do readings by authors, launch events for Amazon original video content, Kindle product launches, and so on.
Also, six foot HDMI cables. Everybody needs those.
I think this is the first time I've seen the phrase "post Edward Snowden world", used like "post 9-11 world" has been for the last decade-plus.
I hope that catches on.
Edit: can't believe I got the name wrong. Fixed.
They're a bit vague when describing the "I-was-going-to-buy-it-anyway" problem, but it sounds like they're mainly talking about PPC ads on search engines stealing from SEO links on the same pages. (Some of it seems to be talking about stealing sales from the direct channel, which I have no idea how to handle.)
If your website is already tracking ad performance on a per-ad basis (i.e., tracking all the clicks on that ad, and keeping what you pay per click below what you're getting per click), then optimizing for only the paid search traffic that's incremental, and not cannibalistic, is pretty straight-forward, conceptually.
For a given ad's keyword, instead of optimizing only for the results you get from PPC traffic, you treat your PPC bid as an input that affects sales across PPC and SEO traffic for that keyword, and optimize accordingly.
There are a few extra steps and decisions that need to be made before full implementation, but this is the basic idea. It's actually not too bad to account for.
I think this study fails to give serious thought to the phonetic differences of the left-side and right-side letters, and the possibilities for co-correlation there.
The right side has 4 out of 6 of the vowels and 3 out of 4 of the other sonorants, which could easily be argued to be the more sonorous or pleasing sounds in a word. 7 out of the 11 right-hand letters fall into one of those categories.
By contrast, the left side is only 3/15 sonorants. Further, the left side has all the sibilants and a strong majority of the stops.
Pointing out that right-side letters correlate with agreeability is an interesting finding. Claiming that which side of the keyboard the letters are on is the _causal_ factor for agreeability strikes me as lazy.
I suspect that people in southern California would share your confusion about the pronunciation.
I completely agree, it's interesting how many people love to jump to economic theorizing about how people will act, and how few people look at the actual cost to implement.
I read through a breakdown in one of the Basic Income books, of what it would cost just to get a $10,000/year basic income. Here's just some of the changes that would be needed:
* cut military spending by a third; * get rid of ethanol subsidies; * get rid of mortgage interest tax breaks; * get rid of "married filing jointly/separately" filing status, make everyone file just for themselves
And that's just the ones that jumped out at me. Virtually all tax loopholes would have to be gotten rid of, and more. All for just the $10K/year basic income level.
So, just as a question of the political cost to implement, Basic Income seems like a laughable non-starter.
There's really nothing new about hostility to immigrants in the United States. The last generation's wave of newcomers is the next generation's "old guard", saying that the new wave is "lazy", "unskilled", and a leech on society. What's going on today seems like a fairly straightforward continuation of how we've always been.
There've always been lots of people who would say that the next wave of immigrants is unneeded, and unwanted. No matter how successful they turned out to be.
This is becoming my biggest concern about these Basic Income plans, too.
Giving this amount of money to every person in Switzerland would total almost half of the country's GDP.
Even if you exclude children and get the total amount down around 30% of GDP, you're still right around the total amount of money that the Swiss government takes in in a year.
So to get this basic income with no new taxes, the Swiss government would have to abandon all its other obligations. Or, put another way, to fund this and still function at the same level, the Swiss government would have to double its tax income.
You're only paying 35% in US federal taxes if you're making over 400K a year. Someone making $100K to $150K is in the 28% bracket.
And you're probably only paying 10% in state tax if you live in California. Most other states' income tax are around 5 or 6 percent, and some are at zero.
Gravity can be tested just by dropping your pencil. The invisible hand takes a lot more faith and fervent wishing, IMO.
The catalogue will list the build-year of the property you're looking at, but will it give much information on the build-years of the other nearby buildings?
DoubleDown Interactive - Seattle, WA - Full time, permanent (http://doubledowninteractive.com/)
We just want everyone to have a good time.
DoubleDown is an on-line casual casino, currently on desktop, Facebook, and numerous mobile devices. We are looking for HTML5 mobile devs, Flash/ActionScript front-end devs, and Java/Scala server devs.
This is a fun, laid-back work environment, and we're looking (mainly) for experienced developers who pride themselves on shipping quality code.
Profitable company. ~175 people. Perks like it's still 1998. You can have a positive and appreciated impact on the company pretty much as soon as you start.
Check us out at http://doubledowninteractive.com/careers - or feel free to send me questions (my personal email's in my profile).
Thanks!
If you were born in Bulgaria, Hungary or a hundred other places and your first exposure to English in bulk and attempts to speak it started at the age of 10 or later you'll have a fairly strong accent no matter what.
Sorry, but this is just wrong. Anyone who first learned English as an adult can improve their accent from strong to mild over time, with effort, if they choose to. If they live in an immersive English-speaking environment, this will often happen without conscious effort, as long as they value communication.
Anyone whose strongly-accented English doesn't improve after a few years in-country doesn't value communicating well. (Either that, or they just spend all their time in a native-language enclave.) And someone who doesn't value communicating well should not be in the role of CEO.
Agreed. One of the things I liked best about Matter was how it took all of Star Trek's hand-wringing about "first contact" and turned it on its head - there were right and wrong ways to initiate contact with a primitive culture, but it wasn't a big deal, all in all.
DoubleDown Interactive - Seattle, WA - Full time, permanent (http://doubledowninteractive.com/)
We just want everyone to have a good time.
DoubleDown is an on-line casual casino, currently on desktop, Facebook, and numerous mobile devices. We are looking for HTML5 mobile devs, Flash/ActionScript front-end devs, and Java/Scala server devs.
This is a fun, laid-back work environment, and we're looking (mainly) for experienced developers who pride themselves on shipping quality code.
Profitable company. ~150 people. Perks like it's still 1998. You can have a positive and appreciated impact on the company pretty much as soon as you start.
Check us out at http://doubledowninteractive.com/careers - or feel free to send me questions (my personal email's in my profile).
Thanks!
They're contractors. Treating contractors like they're full-time employees, without giving them full-time benefits, can get a company sued, not to mention dinged by the IRS for back payroll taxes.
One way to keep the contractors separate is to only have them employed for a limited time, usually in stints of less than a year.
If the workers are being classified as contractors, then it's important to have an arbitrary cut-off that limits how long they can work at your company. Otherwise some people can get kept on as contractors indefinitely, when they should have been re-coded as full-time employees.
Of course, this isn't a limit on length of employment, just a limit on the length of someone's employment as a contractor. Plenty of companies use more of a "contract to hire" approach, and make a decision whether or not to convert employees to full time at the end of the contract.
I can almost guarantee that the 11-month max is Amazon's policy response to the Microsoft permatemps lawsuit.
http://en.wikipedia.org/wiki/Permatemp - scroll down to the Vizcaino v. Microsoft section.
I would recommend that your friend:
* make a list of technologies/skills that he would like to learn;
* make a list of technologies/skills needed in his job, and in his upcoming project;
* look for any conceivable overlap in those two lists, and spend his time doing that - justify it as "prepping for the project".
There's nothing requiring you to specifically test every function in a class - though, as others have said, you can set the access level to default or protected to have package-level access for tests.
Strictly speaking, though, refactoring should never require new tests, unless you're specifically refactoring to increase testability. New tests should be related to specific bugs or feature requests.
This is a percentage chart, which only shows that mobile traffic is eating into desktops' _share_ of the total traffic.
This chart says nothing about whether mobile is eating into the absolute traffic that desktops are getting. More likely mobile traffic is increasing a lot, and desktop is holding steady.
The main difference is the margin. IPhones sell, reportedly, at a 58% margin. The profit margin on Windows has, in the past, sometimes exceeded 90%.
Amazon is retail. They make 12% margins in a good year. Which is one big reason why Amazon will put significant effort into a new market with a 25% margin, that the others would turn up their noses at.
That sounds like it could be generalized to [noun] [adjective] [adjective]. Notice the lack of verbs, prepositions, or markers for subordinate clauses.
This seems much closer to a code than an actual language.
Agreed, one of my favorites. I do this so many times every day:
hg diff -b <filename>
hg commit -m "comments" !$
1) Test your APIs. A public API, especially one that is key to your business, should be near 100% coverage. And attacked to look for security/usability/load problems.
2) Test enough during development to support later regression tests, and to make sure that the design is testable. This can usually be achieved with less than 20% coverage. But if you write production code that's so screwy it can't be regression tested, then you've got big problems.
3) Test any parts that scare you or confuse you or make you nervous. Use "test until you're more bored than scared" here.
And also be sure to be "that guy" who insists that every single request be made into a ticket, instead of handling simple walk-ups informally.
There's some research[1] that suggests that some dialects of Old English used double negation reliably, but that this got phased out in 'proper' Middle English.
It's interesting that double negation is standard in French, but not used in Germanic languages. In this case, it seems like the Germanic influences on English won.
[1] http://articles.chicagotribune.com/2006-11-08/features/06110...
Where are you seeing that earlier data? I can only get the graphs to cover 2012 and 2013.
This is a good example of how deceptive a percentage-change-only chart can be, without the absolute value of the portfolio also figuring in. If the system has a max drawdown of 98%, then getting 200% returns after hitting that low isn't going to do much good.