In a mostly-tech company I couldn't imagine not having some compartments so that you don't suddenly find yourself 1 among 30 people in the same room - I'd go completely insane.
302 karma · joined October 12, 2010
In a mostly-tech company I couldn't imagine not having some compartments so that you don't suddenly find yourself 1 among 30 people in the same room - I'd go completely insane.
- Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version.
- Decouple the browser from the operating system. I don't really care if they make it cross-platform (though it would be nice), but if the browser stops updating unless you upgrade to the next version of Windows you WILL end up with legacy sites again and again that cater to a specific version, and then we can start over and just replace every rant against IE 6-7-8 with Spartan 1-2-3.
I can understand what you mean, but to the end consumer they are going from being able to buy a Tesla directly to not being able to.
For postgres itself, make sure you know what all the settings in the configuration means, why they make sense 90% of the time and definitely do not make sense in 10% of the time (such as a low memory server with super-fast SSD disk arrays). And in general ofcourse a good knowledge of SQL, index usage/performance. Postgres extensions (arrays, JSON, etc.) are decent, but in my experience it's something you can get into relatively fast if you are solid on the rest.
Alternatively, argue that letting you work on solo projects will be beneficial to the employer; Risk-free testing of new frameworks and languages that leads to an experienced developer.
For some very big companies (I've worked at one myself) they seem to have a zero tolerance policy of outside work and you might be SOL in that case - I guess you have to ask yourself whether it's worth it then.
I think the point of the article is that being smart at puzzles is not enough. It may not matter whether you have 3 or 10 years of programming experience, but if you have 20 years of puzzle solving experience with only 6 months of (real-life) programmering experience you have a lot of non-trivial learning left to do.
Being in a startup setting where everyone (usually) is expected to be a bit of jack-of-all-trades, I would argue that having programming experience trumphs being smart, at least for the first period. You may be the master of finding smart algorithms to design your application, but if you can't build the first CRUD website it does you little good.
Also, we are talking ~37k lines of code, not exactly something you can write in a week or two for $500.
The idea of surveillance, in this case, is that no 3rd parties can snoop on your data. If you are actively using a site, it should be under the assumption that they can and will track anything you do on their site.
I would still say that tracking down a misspelled e-mail address or have the user completely confused at the next login (because they don't realise they misspelled it) might be worse than having the break in the registration process.
There is no risk to you as a consumer, you have to either give them permission to set it up on your behalf or you basically use the first request for money to set it up (there's a bunch of numbers you enter and VOILA it works). Also, you can cancel these at any time from your end (but your landlord might not be too happy with that).
I have hope that they will do this, but looking at the history it's far from certain.
The URLs were public to start with (so that the iPads could make use of it), he just went further than intended by AT&T, but that is not a crime (at least, that is what is argued).
My interpretation of it is that he is lamenting how the issues list has become a catch-all for everything from bug fixes (which are fine) to random non-Backbone related development questions, and looking at the issues at lot of them are in the form of "HALP!" with a very light description.
We frequently (at least once per month) get a phishing e-mail asking us to reply or click a link and provide our credentials. For anyone who has attended the university more than 6 months, there will have been at least 3 e-mails from the IT-department telling people to not ever, in any way, give out credentials. Yet, for every phishing mail we get at least 3-4 accounts get compromised (out of ~1500), and more would get compromised if the IT department weren't quick to block traffic to the offending URLs. And again, this is in a crowd that should be somewhat unfavourable to scammers (as most of us know and can recognise such attempts).
You can try to educate your users, and you should, but just know that it only minimizes the risk, it will never, ever nullify it and if they can send 1 million e-mails from just 1 account, then it is practically a dead-end in terms of stopping the scammers. I can completely understand why they are blocking Google Docs, it's a matter of settling for the "lesser evil" solution.
I used to operate a tor exit-node and my hosting provider wasn't really interested in whether I was infringing or not; If the data looked to be going to my server, I was responsible so in the end I had no option but to operate as a non-exit node. Put.io will most likely be hosting their own data (or in the cload), so this might not be an issue.
A good presentation has few slides with a few key points, some images and the rest should come from the presenter. In contrast, an article explaining a subject is primarily made up of text, code samples and a few images. If you try to aim for the middle ground, you are going to get something that is sub-par for both.
I still haven't been aggressively asked by employers what I make now, but I have been asked aggressively what I wish for (as in, you tell us first and we'll say yes/no/maybe).
Grouping Cassandra, CouchDB, MongoDB, Redis, etc. is the same as grouping MySQL with git - they all store data in one way or another, but the data they store and the way they store it varies wildly.
It's also sad, because all these "alternative" databases offer a lot of features that RDBMS' don't, and they should be promoted instead of stuck under an "umbrella" term to protest against SQL databases.