If you only provide hoteling, I think the majority of people will just claim a desk as theirs, and you effectively have no hoteling at all.
1,301 karma · joined November 17, 2008
If you only provide hoteling, I think the majority of people will just claim a desk as theirs, and you effectively have no hoteling at all.
In consulting and mentoring on this topic, I've found a lot of engineers push back against how "dirty" it is to have multiple copies of the data around in different formats. It feels wrong to not have a single, authoritative data format at any given instant. If the idea is to change the column type, why not just `ALTER TABLE ... ALTER COLUMN` instead of `ALTER TABLE ... ADD`?
But if you think about it, excepting trivial cases, once you're migrating data, there are parallel realities at least for the duration of the migration and deployment. It's not a question of whether you create divergence by versioning/staging (in some fashion) your data. It's a question of whether you manage the divergence and convergence of the parallel realities that already exist as part of a migration. If you don't, you either incur downtime or risk data corruption.
One big win here is that, by being disciplined about your code and data changes, you can cleanly separate deployment from release. You can deploy a feature but have it disabled or only enabled for a subset of users. Releasing a feature means enabling its feature flag, not orchestrating a set of migrations, replications, and deployments.
I can't select C/C++ from the language drop down.
About half of the time, I don't use the video chat functionality for one reason or another. I'd love in those cases if I could simply close the video conferencing panel to have the editor full screen.
Even if you don't allow me to disable video conferencing for the Codassium session, I would recommend different messaging on the right hand side panel. I've had a few candidates say that it isn't working because the right hand side just says, "Loading..." when we don't use the video conferencing.
There's a typo on the Tour page: "Schedule an interview via Codassium is easy," should be, "Scheduling an interview an interview via Codassium is easy."
I'm not a fan of the pricing plans. I'm unsure of the idea of limiting the number of uses per month in general, but the current limits are very unattractive. It's all basically oriented around each user only doing 3 interviews per month. I would prefer a limit on number of hours per day or number of uses per day over the total number of phone screens. As it is, everyone that I've turned on to Codassium would have to get a Custom Plan.
It'd be nice if the things I type versus the things they type were differentiated in some way. Maybe just a subtly different background color?
Do you have a better citation for this claim? The linked Business Insider article does not claim such a thing, and the court filings the article cites do not support the claim.
The article cites Google's Special Agreement Hiring Policy that divides companies into three categories: Restricted Hiring, Do Not Call, and Sensitive. Only the protocol with respect to Restricted Hiring companies is constrained to Sales, Product, and G&A. Google's protocol for the Do Not Call companies seems to prohibit actively recruiting any employee at those companies. The article does not address whether other companies limited the scope of collusion to, "sales and product people."
I mean these as honest questions. The law is complicated, and it's easy to accidentally run afoul of some provision somewhere while acting in good faith. Outside of retribution, it's preferable to resolve these situations amicably. It's faster for the employee and less risky for the business. So when I hear these kinds of stories, I like to identify where the breakdown happened. Was it a bad hire? A broken reporting process? A failure of the lawyers to assess the claim?
Honestly, I doubt "most proud" versus "best" makes a difference at all. Candidates generally explain their answers to these open ended questions. If they (for some reason) don't recognize the implicit, "And why?" part of the question, you just follow up with it.
The conversation will never be just, "Foobaz, next question." One way or the other, it will be, "Foobaz because..." It saved the company $2M/year. Or users really loved it. Or it improved the engineering process and made releases faster and lower risk. Or it was a really tough problem that required a lot of creative thinking. Or it taught me a lot about 3D game programming.
I cannot see how a mall is analogous. In the mall, you choose the stores you go to and then look for the product there. You are explicitly entering different stores, and you have the obvious ability to return to that store. That builds affinity with the store.
With Amazon, the typical entry point is to search for the product you want. You don't particularly care who is selling it so long as the price, delivery, and trustworthiness are there. Maybe if all other things are equal, I'll choose a vendor that I bought from before. But, to be honest, for most purchases, I've only ever thought of it as being fulfilled by Amazon or someone else.
Anecdotally, I literally can't recall the names of any vendors I've bought from in Amazon. But I do know the places I like in the mall.
Does this not then constitute an information leak about what seemingly "inessential" public-facing sites are housing "essential" services (that perhaps should not be on public-facing hosts)?
These systems are broadly the same. If you're writing your configuration from scratch, they're all fairly pleasant, and it's mostly a matter of preference. They share most of the same concepts (although the terminology differs) and features. In my experience, their differences are primarily in feel and community.
For feel: Chef gives you Ruby pretending to be declarative. Puppet and Ansible give you something more declarative at the expense of some expressivity. Puppet has its own syntax, and Ansible shoe-horns some procedural aspects into YAML syntax. I prefer Chef here. (Chef also provides a web UI that lets you edit things, but I strongly advise against using it except for managing nodes. Everything else should be code/JSON.)
For community: With configuration management, one of the things you'll want is good community involvement. You don't want to write every cookbook/playbook/module from scratch. From what I've seen, Chef and Puppet have a large head start in this department.
That said, you should be prepared to customize the community offerings. People generally implement precisely what they need, in precisely the way they need it, and your needs will not always align. Fork all of the community offerings so you can modify them while still pulling from upstream. Managing this is decidedly difficult, but there's no better choice. It's one of the areas where git submodules would be really great, if only they were nicer to use. If you're going to use Chef, consider also using Berkshelf for managing your cookbooks.
If you do not have configuration management in place, pick one of the major ones, learn the hell out of it, and get to automating your operations. Having your infrastructure as code that you can run whenever you want, that you can review to see exactly how something is configured, is life changing. Once you get to doing it, you will never want to go back to the bad old days.
Machines can read [these error messages] just fine, though.
Here's an idea: machines shouldn’t slap us in the face.
They should help us along if they fail to do our bidding.
He's not encouraging admins to replace useful debugging output. In fact, it's the opposite: he's encouraging email client designers to actually use the debugging output to let people know what went wrong. His mockup is quite clearly of an email client showing users relevant recovery options based on an underlying error message the client has parsed.In other words, he's proposing that email clients treat MTA error messages precisely as they already handle raw headers. Full headers contain useful debugging information, but you aren't normally debugging.
Frankly, the blog post leaves a lot of questions and is short on links to answers. It would be easy to walk away from the post thinking Joyent's HTTP Signatures to be incompetently designed. It was almost enough to have me quip, "More like HTTPS Signatures," because the design in the blog post is only sensible over TLS. However, having found the above link, I see that it is the defaults that assume TLS, but that you can specify the signature contain all headers and the request line. This makes it possible to sign requests over HTTP.
I'd rather the defaults be reasonable for insecure transports (i.e., all headers + 'request-line'), since the TLS case is easily handled with just 'headers="date"'. If that's not to happen, I'd hope that implementations actively prevent the use of the defaults over insecure transports. Unfortunately, Joyent's reference implementation doesn't seem to do this.
What version of PHP are you looking at? PHP 5.3 and up seem to have a sensible linked list implementation in zend_hash.[ch]. The buckets only have a pointer to the list head, but items are inserted at the head. The hash has a separate list for ordered traversal of all items in the "array" and that has pointers to both the head (for traversal) and tail (for insertion). In both cases, list insertion is O(1).
Of course, as you said, the search for our worst case is necessarily O(N). Depending on your perspective, we can say that's a trade-off with hashes, a fault with the hash algorithm, or a fault with the collision resolution strategy.
I am somewhat surprised that Shady Characters was not cited by the article. There is simply no better place to learn the surprising, entertaining histories of our punctuation.
See Amendment 36 at: http://judiciary.house.gov/hearings/mark_07272011.html
You can design something very intentionally without ever having compiled a spec for it. There are certainly design notes, e-mail conversations, and, of course, the code itself to document the protocol for internal purposes.
Which makes me question how hard it could possibly be to submit an open draft to a standards body.
Assuming FaceTime has an internal spec, that does not mean it is in any shape ready for public consumption. For example, the spec could leave unspecified various things that Apple's particular implementation did not have to address. It could be written very informally. It could have fallen out-of-date as the protocol evolved.
None of this would mean that FaceTime was designed "willy nilly." There are processes less than ideal but still perfectly acceptable.
This does not mean that Kootol is not a patent troll or that this is a legitimate invention. I don't know what the claims in 878/MUM/2005 are, and its title reads completely insane in American English ("connecting brains to equally like brains?"). Kootol has filed for several other, similar patents[2] that cite 878/MUM/2005. I wonder if 878/MUM/2005 really backs all of these different claims, or if it is simply a vague-enough tool for them to be using to make new claims that can be applied retroactively?