717 karma · joined September 26, 2010
Tomoe Hotaru
_,~~,
/ /(| \
(((/ ) )\
/ e e( \\
// \ = / /
"---] [--"
Sailor SaturnWell, you've just been shown the opposite. By dismissing your own argument - by claiming it is just a matter of random, arbitrary preference - you kind of write yourself out of the conversation. I guess you are less likely to offend, but you're less likely for anyone to listen at all. You may as well have not spoken in the first place.
This is excellent advice. Actually, give anyone you interact with your dopiest, most shit-eating grin possible.
HOW YOU FEEL: Like a fucking idiot HOW THEY FEEL: Wow, this guy really appreciates this interaction! What a big smile! : D
You get used to it. I have gone through this too. I used to never smile in photographs. Now, I give every photograph my "retarded person who has just learned he is going to mcdonalds" huge idiot grin. You know what? Now I look like everyone else who smiles in photographs
Sorry, but this is total nonsense. I knew many a chem student with access to pure ethanol (not to mention the wits to manufacture it). They are still with us (as are the photos)
So, pure alcohol/ethanol will not kill you faster than the equivalent liquor. You may, of course, wish for death ..
I would also like to know where you are from. iPod was an incredibly strong brand here. It was basically synonymous with mp3 players. Anything else seemed, and in truth was, second best. I owned 3 or 4 of the things.
I didn't mention softlayer because I did not want to look like a stooge but yeah, that is who I use these days. Decent prices, reasonable support, you would have to give me a reason not to go with them for a new deploy.
Ah yes, here's the classic AWS apologist pattern in full effect. You don't use EBS! Of course you don't, you would have to be some kind of friggin' idiot to use EBS. So what do you use for, say, MongoDB data files, that is different from morons like me who stupidly assumed they could/should use EBS?
You sound like you think I'm being unfair. Why? Plenty of sites were badly affected by that outage; it precipitated a lot of self-examination at some companies I know of. I don't think I am overstating the issues here.
1. Contracts. They want 1 years minimum contracts for any dedicated servers. For truly gargantuan orders I could understand this but for one puny server? Never.
2. Their definition of "cloud" is different from mine. To use their "cloud" services your servers need to be public facing, ie on public IPs. Want them on your own VPN? You can stil get the cloud prices but not the API. you create and cancel servers via tickets. This is different from VPS how?
3. Sloooow provisioning - even if you are able to use their "public cloud" API to provision a server - prepare to wait hours for it to be done, leading me to suspect it does nothing more than email a tech to provision a VPS and hook it up somehow. Oh, you can't pause them to save money either, again making me think these "cloud" servers are nothing more than slicehosts with an extra layer of abstraction
Is that enough? I could go on.
Cloud computing scales the efficiencies, yes. It also scales the problems. And because of this, AWS is by several orders of magnitude the worst of my current hosts.
I have dedicated servers. No downtime in past year. I have a couple of cloud servers with rackspace. No downtime (although i don't recommend them). I have some VPSes with local providers. No downtime.
AWS? More than 24hrs downtime in the last year. Seriously, for someone trying to run web sites reliably - screw that. I'm not using AWS any more.
And don't even get me started on the apologists. "EBS slow as treacle? Well you should have been running a multi zone raid-20 redundant array! Duh!". "EC2 instances dying at random? Well you should architect and implement a multi-master failover intelligent grid!"
I used to be under some kind of crazy delusional spell that the above was correct and it was somehow my fault that I wasn't correctly adapting to AWS's numerous failings. Well, no more. Now I realise that I should just stick with the super reliable service I know and love from traditional operators. You need to programmatically grow and shrink your app server flock? Great, use AWS. For the other 99.999% of us - stick with what you were using before.
I also don't appreciate the call to some kind of moral high ground - "I run a business which helps teach little kids to read". Yeah yeah. Maybe slowpoke has devoted his life to curing cancer in kittens. Wouldn't make any difference to his argument, either.
That said, you're pretty young, and your awful diet has evidently not caught up with you yet. When it does, I predict a swift re-evaluation of your ideas about nutrition and self-exceptionalism.
Unless you are a bodybuilder, which I am guessing you are not since they most certainly do care about what they eat, you are likely considered overweight in every other country on earth.
That's not how the real world works.
I was all primed with a fiery response about how good programmers in hot markets should be pulling more than 200k, lousy markets at least 100k, and anyone who wasn't is either a lousy negotiator or not good, but then I remembered where I was. The crème de la crème. Yeah, "staff programmers" (as I call them) might well earn less, on average, than nurses. And it's a guaranteed, standardised wage, none of this grasping meritocracy competitive nonsense.
The thing about programming is that it gives you a chance to shine. I mean really shine. God bless the nurses, etc, but realistically speaking any one nurse is not going to change the world just by being a bloody good nurse. I think the attraction to the high-stakes sink-or-swim pure meritocracy game is a very male thing.
NASA could definitely be run better but let's compare apples to apples. I'm sure any given engineer at SpaceX has a computer on his desk superior to the entire world's computational capacity at the time the shuttle was designed.
A bad place to work can actually be fun for a while, if you have good coworkers. It can be a bonding experience, a rite of passage, friendships forged in the fires of mt doom etc. But indifferent management and ashen-faced zombie coworkers determined to cling to their mediocre jobs until they rot to death in their seats? It's a different type of poison, but just as deadly ..
I'd be suspicious of a departmnt with a turnover rate around 6 months, sure, but if it was 5 years I'd be equally worried, because unless working for that company was the shit then I'd be concerned with the kind of developers the company had hired in the past and what kind of culture such a bunch of unambitious seat-warmers had developed, and I'd be expected to fit into.
Anyway YMMV but out of all the outsourcing decisions I've had to make recently, github was one of the easiest.
.. and then I realised, github does all this for me, and for $50/m or something for an org account, and that is an absolute no brainer for a working professional. I cannot fathom these complaints about $22/m or what not. If you have enough knowledge to participate on HN and that amount of money is meaningful to you, you're doing something wrong.
In a great many cases it is impossible to make a GUI to perform every conceivable action you want to do. You need to drop down to a more basic level, and that inevitable means text, whether it be programming languages (like HTML) or command lines. Drawing some arbitrary line based on when you in particular decided to stop learning new things is pretty meaningless.