558 karma · joined December 29, 2011
Think about how they've turned expenses into profit in almost every other aspect of their business.
- Shipping their books? Ship their own + others and make a profit
- Hosting their website? Host their own + others and make a profit
- Advertising their products? Advertise their own + others and make a profit.
It also effects more than just the version you're linking to
- downforeveryoneorjustme.com says down
- seeing new twitter posts still
guessing it's intermittent
All it would take for all of your customer's privacy and security (mostly their security via obfuscation) to be compromised is for one person to gain access to your google login. If somebody does that, they are instantly gaining access to countless private URLs nobody would know about otherwise in a beautiful easy-to-use interface called Google Analytics.
And then you have "intentions" to do opt-OUT tracking?
You are currently demonstrating your decision making (when it comes to security) is very poor. You really need to think more about your users if you're going to be serious about this project.
As long as you reply in your 30 minute deadline, i dont see how you still can't do what he's doing. I have my phone on me all the time and if there's an emergency or some sort of window where i must reply, i hop on the phone or go back to the desk and get it done.
That said, my reply wasn't intended to be a blanket statement of all remote workers.
One example of where it doesn't work is at U-Haul. A lot of uhaul customer service is people sitting at home glued to their computers, waiting for calls. There is no 30 minute window there.
My point was that it's not as impossible as the comment author made it seem. A balance between "riding in the park" and "answering my client within 30 minutes" is possible here.
Working remotely is great for ones health. Co-working is best for synergy and communication.
It's all about the balance.
Working down to the bone, "every second", will lead to serious burn out. Your mental health suffers, as do your relationships.
I won't make any assumptions about who you are or how you work, but I tend to see this mindset from new blood who wants to get the edge over others. I understand this mindset, as it's very productive - like a short sprint - but it's not sustainable.
If you want to last the whole race, you need to pace yourself.
Not everybody builds things with mass appeal in mind.
Not everybody has to understand the reason for something.
Some things are done for ourselves and how we like them, regardless if it has some sort of use case.
A: It's a niche chat app for gamers to use while gaming, in order to communicate as a team.
From my understanding, it was meant to be a low resource alternative to skype. It's hard to play games like League when skype is eating up your resources/bandwidth/etc.
My short reply is... I agree that staying within the app is a win. The overall mood seems to be "yes, one less app i have to use now..."
I don't keep apps I dont need or use, and a lot of people feel the same way. I dont want YET ANOTHER social networking app. This app feels like snapchat and IG merged, except in reality, IG just stole a lot of Snapchats thunder/users.
Regardless of what the post says to you, people have it and are already posting a LOT. Vogue already has anna wintour in multiple posts on their IG story. Brands already are posting. A lot of the vine/snapchat "stars" are already 20-30+ posts deep. I see fashion bloggers, tech writers, etc. A lot of people are already using it.
Meanwhile their customers are very happy and very active. Look at how many snaps you see on your snapchat right now and then go look at how many IG stories have already been posted in the first couple hours.
I'd say that was a successful launch.
Nit picking things, as a developer, i understand... but ultimately what matters is: are customers using it? Right now the answer is, without a doubt, yes.
Thousands (Millions?) are debating deleting their snapchats at this very moment. I know I am.
IG did a great job getting a whole lot of activity back on their app. Congrats to them.
What is the difference then?
Also, what is worse? A bot with a premium account or a human with a free account?
<div class="center-this"><div>Stuff</div></div>
.center-this {display:table;} .center-this > div {display:table-cell;height:100%;vertical-align:middle;}
I even code pen'd it for you: http://codepen.io/anon/pen/RPEypL
It doesn't require everybody to be in on it to execute this. It only requires one entity and that's apple.
Apple pings indie artists they know will get mad. The singer of the brian jonestown massacre is known for his rants. They get a bunch of people pissed off "Free music.. free music..." and wait for it to go viral. Then, flip the script and campaign done.
But again, i think they just did a good job of turning this nightmare into a positive.
Before I took over development we were running on apache w/ vanilla PHP and CPU's would be > 75% on a regular basis. The site frequently ran into the Apache 10k issue you mentioned in your paper as well. After getting the new server setup & optimizing all our MySQL queries, it's abnormal for all of our CPUs to even be doing anything. Out of all our CPUs, we might have 5 < 10% currently.
One thing I've gathered from this project is technique is a huge part of optimizing WordPress. 1 resource hog at this scale is greatly amplified and can bring everything crashing down. I remember the first time I coded a simple 'popular posts' widget and how hard that hit when you have 150,000 posts to run through and 300,000+ pages generating on a regular basis throughout the day. We had to scrape it the same week it went up.
One big example on how thinking about your queries is huge (let's ignore page caching for a moment) is if you have a menu that queries all your categories (We have 1,000+) in the menu on every page load, and then run that query every time you generate a page, that would be ~650,000 times a day that menu query is run and the menu is generated. When you think about running one query on a table with 1,000+ rows, it sounds like nothing. But when you have to do it 650,000+ times a day... It adds up.
By switching our menu to be generated once every 5 minutes, having it cached in html each time, and by having that menu loaded onto every page via javascript instead; we only have to query & generate the menu 288 times a day. Apply this "single query/generation + load in js technique" to things like widgets within WordPress (all our related posts areas are loaded like this), it has made our resource usage less than 1% of what it used to be.
Although people get really excited about things like widgets & cool custom plugins... It's good to remember, if you can code, that sometimes hardcoding and/or coming up with your own technique will save you a ton of cpu/ram usage if you truly want to build for scale. Every single query counts. Nginx is crucial > 10k connections & php-fpm is a great partner for nginx as well. I'm going to print out your thesis and run through it a few times. Nice work my friend.
----
Also, idk why somebody said APC is dead. One of the most, if not the most, widely used caching plugins, W3TC, still supports APC caching and a lot of talks about WordPress optimization use APC. Personally, I find other ways to be better, but that's another topic.