I have none.
Also, I disable uPnP and its ilk on my firewall. I have a guest wifi router and keep scrubs off my network.
I have none.
Also, I disable uPnP and its ilk on my firewall. I have a guest wifi router and keep scrubs off my network.
$5/month unlimited data size (writes).
You can sync files back over or they will actually ship you a HD with your data; if you return the drive you get a refund of the drive cost but you're also free to keep it.
The cost for individual file reads is reasonable too.
No muss no fuss
I agree 100%, but the fanboy "must have the newest version for prestige" types don't care. In fact, the more exclusionary the better for them. Totally absurd.
Those sorts of low-powered laptops are already incredibly cheap and nearly disposable, so why would I want one that requires my phone?
What's going to happen Soon(tm) is your phone will be able to do a decent display projection + keyboard. The whole any-surface desktop idea. + multitouch. Then we'll be talkin'
Right now I'm just looking at getting a cheap chromebook that converts to a table and running android apps on it. Really only useful for me when traveling, so not a high priority.
Everyone who knows anything knows that the community is the value. Get everyone on the internet, value is automatically created.
The only problem is 1 of those billions of people would probably share a song illegally on a p2p network and would owe 75 trillion dollars, leaving us like 68 trillion in the red.
I'd like to know too. I only use windows for gaming at this point but I've not updated my gaming rig since they started with all the invasive pointless tracking crap.
I'd rather just run without updates than wade through the mess of BS that is their updates to figure out what is actually going to be applied.
It's a good point but following some sort of vaguely sensible process and best practices (as nebulous as that can be) doesn't cost any money. Like, it doesn't cost any money to create role based accounts for service/license management, bring up systems in a clean repeatable way, implement monitoring etc. Most of my career has been around open source software which is free licensing fee-wise. I think you need qualified engineers regardless if it's OSS or not so the argument of "we need vendor support!" never really flies for me, outside of hardware which does fail.
The purchasing stuff I agree is a big minefield. I think the best we can do as engineers is give them the whole picture. Present the options, the risks, and let them choose. Be as clear as possible and get them sign off on the risks if they choose crappy solutions to save money. Then you can hold them accountable when stuff melts down the way you said it would. If you're lucky, over time you can develop a reasonable working relationship with the business side of the house and there can be mutual trust. Makes life much easier. It's easy to see certain groups as "the enemy" (I'm certainly guilty, depending on which hat I'm wearing on that particular day) but the truth is Hanlon's Razor is a real thing and most people want to at least do a reasonably decent job. Most of the real problems are people related not technology. Sometimes a simple "hey, we're going back and forth on this a lot; I don't fully understand where you're coming from. Want to grab a coffee and you can explain it?" goes a long way.. vs "they're dumb/bad/the enemy and I will 'win' this battle". Hell, they might even be bad but you still gotta find some way to work it out; massive hostility doesn't make for enjoyable workplaces or lives - considering how much time is spent working.
> How does that sort of shit even happen? Who the hell promoted this person? Why?
A lot of the problem is the business side almost always knows nothing about the tech side or (bigger problem) who to trust and who is full of it. They're generally the sorts who can barely keep their own workstation under control. So you run into a few problems.
1) There's a shortage of qualified tech people who have been around long enough to avoid some of the common problems
2) The people ultimately responsible for hiring and business continuity don't know the difference between a good techie and someone who just fabricated most of their resume
3) Incompetent people tend to prefer to hire other incompetent people
4) Qualified people with experience can usually sniff out the hellholes during the interview process and GTFO
Specific to this company, they had extremely weak management. They had a profitable product that required very little actual engineering.. it was a mobile service but the app actually was self contained on the handset.. the only reason they hit our webservice was for billing and account related activities.
They hired the clown via contract from a consulting company to be their Windows/IT guy. Then their service was expanded to multiple carriers and they needed a real datacenter; because this guy was already there, they asked him if he had the ability to build out the DC. So suddenly this low tier windows guy has an opportunity to be an ops/infrastructure manager and add all sorts of fun stuff to his resume; he jumped on it. None of the people had any grownup level ops experience to evaluate his skillset or vet his plans/ideas.
After they had the DB meltdown I mentioned earlier they realized they needed a real ops person. The startup I was at was dying and a friend I worked with before (a business analyst SQL person) suggested me. They also wanted to put their product in teh clowdz; this was 2008-2009, the startup I was at was a pretty early AWS pioneer. (Pre-EBS, pre-ELB.. it was the wild west!).
Anyway I got in and it was a mess, I fought to help them clean stuff up and to avoid problems before they happened. The devs appreciated my efforts but due to the aforementioned weak management, the monkey dude was actually technically a manager? and I was just an engineer? Or something. So while technically I was "in charge" of production he still kept his claws in enough that he'd fight with me over every decision. I finally gave up and got a new gig when it became clear the situation wasn't going to change. Basically it came down to - I'm used to cleaning up peoples messes but I'm not going to fight for the right to clean up other peoples messes.
Ironically when I put in notice they actually offered to fire that dude on the spot if I'd stay. That made me doubly sure I made the right decision to leave; you should never put an employee in that situation to make that kinda choice. He was let go ~ 3 months later after they hired a replacement for me (they actually paid me contract to interview people for them). They're still around (and profitable!) despite themselves; most of the original people are gone due to a series of acquisitions.
Anyway I have a bunch of stories.. I've been doing internet startups for the last 18ish years. I like some aspects of them but sometimes I go park at a big company for a while to recharge. Maybe someday I'll write a book. I actually collect some of the funnier/more absurd stuff that goes on at the various companies. Mostly for my own personal amusement (and because other people wouldn't believe it otherwise). I anonymize them though.
A lot of the kids coming into syseng/devops/dev aren't necessarily bad, they just are inexperienced and have to learn the same lessons. That's the part that wears on me sometimes.. but if people are willing to take advice/mentoring from old timers(heh.. not even 40) then it's all good.
There has been a few times in my career I worked with lots of smart people (smarter than me) and it was a blast. Unfortunately that never seems to last all that long.
I guess. Lately I think the real difference between a seasoned engineer and a "senior" engineer is just taking that extra 10% of time to do things vaguely sensibly up front. There is no such thing as temporary. At the least, set things up so refactoring them later doesn't require a total redo.
This guy in particular was just in way over his head but one of those sorts who is paranoid about admitting that or asking for help. In fact he was hostile to help. Not really part of my original point but he'd do stuff like;
- ignored my advice to not tie production services into corporate domain (if you ever get sold/acquired etc, you understand)
- ignored my advice to not create a "split domain" with the corporate domain (eg the windows domain was companyname.com, the windows dns servers thought they were SOAs but that same domain had actual internet resolvers with different records)
- refused to entertain the notion that linux was production ready (this was in 2009) and forced solaris as a standard. On x86. As vmware VMs.
- refused to take any help or assistance in installing the base OS despite being a windows guy with zero unix knowledge. We ended up with stuff like DB servers that had 2x swap as ram.. and they had 128G ram..
- For some odd reason was very hostile to the notion of service/host monitoring.. like.. not just against nagios but _anything_
The list goes on and on.
He was just really promoted way above his experience level as happens in startups; they hired me probably 8 months after him, when production databases had been wiped and backups hadn't been successful for months (back to the no monitoring thing).
It took a bunch of years to fully undo all the crap he had put in place. I danced a jig when I closed the lights on the datacenter he had built (we migrated). Did I mention in that datacenter, he setup "redundant" switches and firewalls for the servers.. but had all the internet drops coming down into one single unmanaged 1G cheapie netgear entry level switch?
If he had allowed me to help I bet he'd still be working there. I have no problems mentoring people as long as they're not asshats. Last I heard he was in law school after a stint in real estate..
We almost lost our production domain. The original dummkopf who set things up registered it all under his own name and individual email instead of using a role based account. He then was fired for unrelated incompetence. Fast forward to the domain renewal coming up.. charge went to his personal CC.. he disputed the charges.. we would have lost it except by pure dumb luck I was in the middle of a DNS migration project and was auditing/cleaning up the registrar details. It was as last minute as you'd want; expiration was within 12h.
One of my pet peeves - people who register for services or get licenses tied to their individual accounts.
Pretty much any set of algos is going to be easily defeated by humans trolling and no system is going to be anything near perfect. My thoughts;
1) Create a small set of simple, concise rules that are inviolate
2) Have a system so people can mark submissions as good (no rules broken/useful) or bad(rules broken)
3) Have your referees do nothing but determine if that submission is breaking one of your rules
4) Based your user trust as a derivative as how the user voted compared to what the referee votes
The theory is any controversial submission is going to get flagged & referees attention. Their job is limited in scope to just determining if the post breaks the site rules or not, nothing to do with quality / content / opinion. If users are trying to game the system their votes are going to conflict with the referees so their user trust is going to go down, whereas if people agree their trust is going to go up.
Eventually you'll have a group of users that you can generally trust to do the right thing so you can weight their actions accordingly.
Obviously there are some weaknesses;
- Referees are pretty much god (that's why the scope of their power is extremely narrow and simple)
- You can end up with hive mind (though you can combat that if enough trusted users conflict with other trusted users). I'd argue it's a way better protection than pure crowdsourcing ala reddit where the demographics crush submissions into hivemind
Just tossing that out there off the top of my head. It's not something to replace automated reputation management, just something augment it and limit some of the abuse.
I don't loan books or money with any expectation of seeing them again.
Would you treat coworkers like that? In meatspace? If someone called me a fuckwad in a way that wasn't obviously jokey/ironic it would be a huge problem to me. Being nice and civil is a much better way to get things done. Like, grumpy/curmudgeonly is kinda par for the course but that's totally different.
I used to work with a really toxic dev that for whatever reason our management dept protected. He was extremely misogynistic and refused to work with any women. One time in a meeting he said something basically like "it's in the spec, you stupid bitch" (as an aside, it wasn't in the spec
I about died laughing seeing this come from an Anonymous Coward.
Thanks for the laugh AC
Does anyone believe that the NSA shared any details or scope about their hardware purchase? Or any of their vendors?
"Hi we're building out datacenters so we can do some probably illegal data snooping, can you help us?" I'm sure an agency that is cloaked in as much secrecy as possible goes around sharing that sort of information. Especially without gag orders.
Not only is she a massive tool she's obviously full of it. She needs a gag, it's an order.
UNIX is hot. It's more than hot. It's steaming. It's quicksilver lightning with a laserbeam kicker. -- Michael Jay Tucker