606 karma · joined January 4, 2013
More alternatives include:
- Aphrodite (https://github.com/khan/aphrodite)
- Radium (https://github.com/FormidableLabs/radium)
- JSS (https://github.com/cssinjs/jss)
Including table of contents in your README is pretty big overhead if you cannot generate it automatically. This template is meant to be a good starting point for any size of project, so it was a conscious decision to leave table of contents out of it.
https://github.com/jehna/readme-best-practices
You can use it to quickly go through most common information you should include in your own readme.
I would not trust some device to read my thoughts to write them to a Word document. Random thoughts are too uncontrollable.
I would not trust my phone to connect automatically to any device, I see that's a huge risk.
I would not trust my computer when I talk to it. Anyone can hear the conversation and it's disturbing in public spaces to other people.
We saw this happen with Google Glass. People need interfaces they can trust, that are not intrusive.
My experience is, that while ecommerce sites may break, most of them are quite usable even without JS.
Most good blogs work just fine. And the ones that don't I usually don't bother reading.
First is cookies. Say you log in to Facebook with your browser from your own IP address and a hour later you fire up VPN to browse the web. One of the websites you load has Facebook's tracking pixel and - unless you cleared your cookies - boom: Facebook knows you have visited that site.
Even if you clear your cookies, you may have some long-living stuff (like Flash cookies etc) that can be used to track your browser.
And even if you clear everything or use incognito, sites can use some clever heuristics (CPU power, enabled plugins, timezone, browser version, webrtc, etc.) to track your browsing and to match that it's you.
Prerender, Push, Render, Pre-cache, Lazy-load
But of course Polymer doesn't do prerender, so it doesn't fit the Google's image.
It really bugs me that you'll have to load and parse a huge amount of code to get anything rendered on the screen with Polymer.
Programming is not a solo task (unless you do something alone, for yourself, without anyone ever using it). It's all about communicating your deadlines, issues, successes, problems, estimations, risks and decisions to the team/client.
Programming itself is a form of communication. You're usually writing the code for the next developer that's going to have to read it (which might be you in a few months).
As a manager/client if you're not sure if you have a good or a bad programmer, you certainly don't have a good programmer. If you have a programmer that always keeps you up to date and makes sure you understand what's going on, you do have a great programmer in your hands.
I see two ways around this:
1. The company behind the computer takes full responsibility and charges for the risk. Stripe has made online payments a breeze, because they are the one taking responsibility for the legal things (securing payments, proofing physical access to servers holding the credit card data etc).
2. The tool is so understandable that I'm willing to take the legal risk. There are a few tools that make accounting so easy for a small business owner that I'm willing to take the legal risk myself about the accounting.
The problem is, that it's really time-consuming and expensive to get decent terms of service/privacy policy/other common legal document squeezed out of your local lawyer.
The initial version is basically a copy-paste of some template that just has your own company's name put in and does not anyhow describe the service you're building.
After a week or two with back-and-forward you'll get to settle for some English-like gibberish 15-page document that has been passed through the email and you're sure that after all the hours you've put in to try to make sense of the document your clients have no chance to understand even half of it so you're just putting it in since the whole service is already past the deadline and everyone's anyway blindly ticking the box without reading.
The reason why this hasn't changed is that lawyers get paid by the hour, so it's not wise for them to automate anything.
For personal projects I've used some of the 5$ templates from quick Google search, but the problem is that I have no-one who'd take the blame when the shit hits the fan.
In the perfect world this would be an automated computer program that'd ask me a few questions and produce a perfectly understandable and legally binding document that has some trustworthy corporation behind it making sure I won't get sued for trying to do simple business.
I use an app called "Lose it!" To track my daily calorie intake and have paired it with Google Fit where I track my weight every day.
It has been way harder to eat excessively, as I'm constantly aware that I'm accounting all I eat. So mostly it just makes me aware about what I'm eating.
Results: Constant 0.5kg weight loss in every week.
A bit aside from the subject, but I also have changed to use paper money instead of cards.
I have a weekly budget that I get from the ATM every Monday. This raises awareness of the money I spend, since I can see my current budget every time I open my wallet. It has helped me to save significant amount of money.
1. Help the managers realize that you're probably saving 1000s of hours monthly by using existing open source software. The least you can do (as a company) is to give few hours back to the community.
2. Sometimes it's about "can we open-source this tool/work/whatever?" or "does this give our competitors advantage?". Make sure you think this through before talking to the manager; I got a couple of internal tools open-sourced when I argued that even though it does advance our competitors if we'd publish a great tool, it also positions us as a company as the leaders of the genre (helping in recruitment, sales, etc).
3. "Does it benefit the company?" - Managers love to see the company logo in the project. So ask yourself if you're willing to trade some publicity of the company (e.g. "powered by YourCompany" badge, "supported by YourCompany" in the README.md, or moving the Github project under your company's account) for some hours that would be allocated for you to work on the project.
https://developers.google.com/appengine/docs/ssl#server_name...
For now, it's only in beta.
I think the comparison is more of "PaaS vs. IaaS" than "AWS vs Google Cloud Platform".
The year is 1982. Rodney Mullen just managed to perform the world's first "Ollie" skateboarding trick, that can be count as somewhat the start of the modern day street skateboarding.
What now is the most junior skateboarding trick (with available equipment, training etc.) was not a low-hanging fruit back then. While looking back, you can easily learn the trick by imitating; but back then there was no-one to learn it from. You had to go trial-and-error a sh*tload of times before making the first trick.
Of course it looks sooo low-hanging fruit now. With current equipment and support. But you have to realise that the tools and methods came afterwards, to support the original invention. But looking the time back then, you had none of the aids. Just you, climbing to that tall tree to grab the apple and plant the seeds so everyone else could grab the fruits from smaller trees.
But I wouldn't blame them. These are people that don't know anything about security.
At least person that should have enough dignity to say "this is so badly wrong, I refuse to do it" should be the developer.