seorphates

Countless hours saved. Countless discoveries made. Goodbye search.cpan.org.. It was a fun run.

I sort of agree but a good sysadmin was never idle on the inside. I'm seeing good devops people getting worked well beyond what I'd consider reasonable expectations i.e. "Oh, look, you can do everything! Here's everything!".

They're being perverted into a role having a full load of pure operations with shit for processes (and, often, systems) and an expectation that you have time to automate and shore up all the shit and technical debt accumulated since.

Can most good or even extraordinary developers simultaneously be elbow deep on a dozen unrelated products and actually get reasonable traction? I can barely keep one glass castle together, myself.

They'll never die.

Some monkeys will just keep swinging branch to branch. Some monkeys check out the tree.

Grumpykins here. I think the term "Modern devops" sort of nails it but not quite how you used it. Most departmental/enterprise sys admins/engineers of lore that had even the slightest necessity for life outside the box scaled anything resembling automation to its breaking points. Combined with knowing and serving the reasons for their existence - developers, users etc., and devops is nothing new - it is now simply the necessary manifestation of progress at scale (albeit positively devoured by managers speaking business, not entirely unlike "agile").

"Use what works" definitely presents a lot more choices these days and likely will forever more.

"Use what works well" is something different where "well" implies helpful, dependable, predictable, manageable and so on that will continue to scale with your needs. Only breaking things down the "old-school" way will lead towards success, stability, security and life outside the box.

Good devops is still, primarily, good engineers engineering good things, for themselves and others.

Granted the article is from 2015 but my impression is author is not just cranky, but scared.

I don't know. I'm reading it differently. I'm reading it in a way that almost any other entity with the power to execute on a term like that probably would - liberally and with deference to their own interpretation of lawful. Not too mention the 100% murky scope of requests and behests of government.

I read that the wire is owned by Comcast. Its agents roam free and everything traversing that wire is monitored. 100%.

I might say that anything relating to content would be a prime benefactor of decentralization. If you wish to control your own data be it cat pictures, a video channel, streams, email, website, payment method or whatever then the only sure way to prevent other people's ideas, ideals or ideology from affecting your data is to not cede authority over it to anything or anyone.

For an oversimplified example I could, in theory, be in control of my input on this site with a nifty membership hook for publishing (or revoking) my interactions with it by working in my own "shared" instance of HN using a mutually agreed upon distribution protocol wherein each comment is published and "owned" by the commenter without HN having to pony up the resources to store or display it. Which could possibly include some potential for eliminating "acceptance critereon" altogether. ie. HN would have to ask me directly to manipulate my input for anything other than ranking or basic community acceptance. Wherein, ultimately, HN could pull the plug whenever but my "shared" instance could live on with others' until I, alone, pull my own plug which could even result in "comment deleted" throughout all live instances for all prior comments. And so on.

Well,

A) A recruiter is not going to be hiring you (but tread carefully because they're a foot that can be used in many doors)

B) You primary object is to formulate the answer to that question from what you can harvest throughout the interview

C) A positive, direct and clear answer should do nicely, almost always.

D) No puppies will be harmed unless you swing and miss and end up kicking your own puppy when you go home because you blew the question.

So, B. I can do many things in many ways. You should end up knowing exactly why they should hire you before they even ask.

Oh, and

E) Learn to recognize the ones you don't want to be hired for and quickly. Interviews can be stressful. You don't want to waste good energy on something you want to get away from as far and as quickly as possible. I've had exactly two of these.

This a solid five years behind schedule but I'll take it.

I believe any solid grab for a more open handset os starts here.

That doesn't seem too far off the mark. On the craftiness of nation states scale that's maybe, what, a 2?

Given that it feels like everyone and their brother's camel seems to have access and input into our histories and the (just. holy shit.) levels of information these firms have access to and records for regarding just about everything we do with a dollar this is as good a start as any.

Data hoarding industries like these, those that really have too much sway over individuals' well being and access to basic services, needs to be the second most regulated thing on the planet. Or maybe third.

This is what jail is for, bad people that do bad things to others. Excepting maybe bankers or traders, of course.

You know, as opposed to jailing good people that do "bad" things to themselves.

The past decade has been interesting and I'm still processing it.

My current thoughts are that an appropriate approach is for your systems to document themselves via the applications that they run - inside out.

Though I must abide I cannot fully subscribe to "infrastructure as code" anymore. It has proven just another shift, primarily in toolsets and who (or what) gets say and sway over the capacity, capabilities and efficiencies of the thing you actually care about - the app stack and all of its assembled functionality.

In other words most approaches are still "outside in" - one defines 'x' for deploy fitments and that typically over and over and over again and, typically, with a rigidity that can too easily override and overrule effectively caging your application in scale and scope. With my current tact I am trying to provide for 'y' to "self identify" (via some/any form of config mgmt) where from here you can begin to effectively "deploy to any" by hooking the "application config as code" that, in turn, defines its infrastructure and deploys "outward". The "infrastructure as code" then becomes the servant with its objects and platform definitions etc. and the "appconfig as code" becomes the master where the latter defines its own scope and scale.

Infrastructures have a funny way of mutating into inefficient "definitions" of something that once made sense, on the first day, and forevermore complicating progress with capacity, rules and opinions.

But, generically, snmp is still pretty cool for telling me what I need to know. Strapped that into any end engine and, boom, ask any question, request any inventory.

So.. I track apps, not systems. Systems are expendable, applications are not.

Mm. That's on point. It is as illogical as having the means and knowledge for prevention and not applying it. The crazy shit (booting theater active operational assets) was implemented by authority. Not patching theater active assets leads to death.

Reboot. Around the same time-frame we gathered the flag for a deployment (fleet admiral) and I was responsible for UNIX systems on the ship. Not long after coming aboard the command came down to reboot all of the systems at midnight, nightly (yes, only the UNIX systems). Being that "But Mister.." never really gets you too far in the military I just rode it iterating through any possible reason for the madness, nightly. I could never come up with a good one. Until now. (ok, perhaps not a "good" reason but crazy enough to count.)

It now makes much more sense to me that a (terrible) mishap had occurred and possible prevention was only a reboot away. I can see how being exposed to that context at upper levels could easily cause one to latch onto any perceived preventative measures.

I also once saw a short ntp time step across multiple clusters (yeh, simultaneously) shut down half of a wafer factory.

Time is important.. but rebooting all your systems at midnight probably will not help you to control it. This especially if there are large, hot, fast objects flying around in the night sky and definitely, really, don't do ALL of them at the same time every day .. especially during, you know, battle. /pro-tip

It's an interesting (but mostly depressing) problem. The insistence that "others must be in control of what you own" doesn't really sit well with me, at all. I won't drive a phone without root, for instance. Otherwise the plethora of updates I have sitting around not being updated would do nothing but eat data with garbage updates with naught but a new roll of advertisements and, if you're unlucky, new garbage access requests. Update the os? Yeah, no. Not on your watch, at least.

A firewall, for instance, is a basic necessity. Even the crude android flavors. It includes the ability to lock out your "vendors" selectively and accurately.

My build is, hm, approaching it's fourth year, I think. No auto updates save for select apps. No complaints. No surprises. But I'm special, I don't do "phone for fun" and so have a fairly limited and hardened short list of requirements.

The most annoying thing on android is Google XXANY - by a wide, wide margin. I'll be itching to build a google-go-around on my next handset, for certain.

Save all those apps you like, for sure, I still depend on side-loading quite a few that have since gone by the wayside. At this juncture I have to take absolutely every bit of control that I can get my filthy paws wrapped around.

Why is the team being formed? There must be specific needs, goals and timelines. That seems like it would be the primary driver. It sounds like you already have several choices all up to the task. You might burn several days trying to wedge the team into a decision. It could even get heated. So, unless you're looking to eval the temperament of your team members I'd just pick a pony and saddle up. If the tech lead is brilliant and only likes the chocolate doughnuts then you can give some extra deference but don't let a lead list the ship.

I would suggest looking up and down your entire stack with a good eye, too. Evaluate it from the outside. Even if it doesn't exist yet. Are there other operations to integrate with? Will selecting one or another affect its maintainability? What happens when turnover strikes?

If they're good enough they'll build with any tool. Pick one then see if your team can change your mind within two hours. Use the other five to get busy.

Horse shit. Fatally flawed article. But I see the comments pretty much have that covered.

I wonder where the other 70% is..

I wonder where the collective of artist streaming sites are..

I wonder who's making stuff..

I. Just. Wonder.

Well, I couldn't agree more. The concept that ad-blocking is bad is right up there with the content industry thinking, believing that the Internet couldn't, wouldn't exist without them. Rubbish.

I don't understand how that changes anything about customization.

But I do understand the tab stance. When anything changes in UIs that directly affects the entire experience it is almost always a hurdle, for sure, no matter how savvy, no matter how willing.

And that justifies the remainder of the thread existing how, exactly?

Is it customizable? That seems like a pretty strange question from someone that maintains it for a user base. Apart from "disabling" tabs what are you looking to customize? Having used TB since inception I might think a more apt question is "What can't you customize?".

I also don't think I understand your tab stance. You don't have to base your usage on tabs, do you? Personally, given the volume and types of mail I deal with, I was waiting for tabs for years. I just want the context menu option to "view message in conversation" to always exist. It dropped off a couple of builds ago and I can't seem to get it back. Usability of mail without this is decreased exponentially.

I am of a similar mind. Every single droplet of data that would not or could not exist without you, about you or because of you should, effectively, be "copyright" you. Every single drip. Everything. Use it without permission and, well, you're just another a dirty wire pirate.

Our jester, filling the air with truth.

Our FCC commissioner, spinning yarns of fantasy.

Mhm.. you all work too much, or not enough.. still on fence.

It's a motivational concept, a personal reinforcement of a goal you've set for yourself, slang for dropping in. You'll get hit but you want to get hit. You want this.

Wanna be? Gotta be. Poke and go.

They also have ramifications for the systems that consume them. If a system is ascii and using extended ascii then globalization presents some specific challenges around these groovy usages of the seemingly innocuous little flat line.

I like how an artist of no insignificant consequence makes his entire catalog available, and then some, and the only comment on the submitted page is (succinctly paraphrased) "yeah but the website sucks and they should feel bad".

The cynic in me reads that like an on target torpedo fired from the inside.

Regardless, nice move from Mr. Neil Young.. Fantastic move.

Is it taxed?

Do we have healthcare?

Will a spouse have the same benefit?

Rent takes a fifth of that net, minimum, and you guys are talking about retiring, travel, lounging around and lives dedicated to charity?

It's not 5k a week. Am I missing something?

Given what I see here, a stinkbutt stance of a question, I'd say the greatest impact to myself would be some stress reduction, slightly relaxed job requirements and a helluva better outlook for a tired, aging body.

As a casual observer the entrenched expectation of copyright is wholly incompatible with today's means of information flow and can only result in further erosion of privacy in and around all digital communications.

The entire premise of a limited monopoly was, previously, fairly easy to police, all things considered.

Realistically, expectation or desire for a full copy stop is a fools errand and further attempts at this along with the simultaneous desires for harsher penalties will hurt the many much more than any rights holder could ever be helped.

A digital age copyright solution is being prevented because of unrealistic or outdated expectations that are being wedged into a reality that has, effectively, aged out.

In my opinion the trifecta of threats that are at the root of the impending Internet Dark Ages consists of large media rights holders, ISPs and the sub-constitutional security state.

The only sliver of light that I can spy includes a catalog that is on par with our digital age. If the expectation is that any and all works can maintain their own copyright gates, or, worse, that the government can man it for them, is harmful, childish and doomed. The CASE Act appears to be more fear-based garbage law that will continue to aggravate the already untenable state of copyright and the expectations of protections. .. treating symptoms with poison.

I don't appreciate the direction the nn discussion has gone. To me the core and fundamental principal of innovation and growth is connectivity - pure, raw, naked and unfettered access to an open network. I am and always have been able to choose any "edge" provider or network service or content I desire, always. This is not true with regards to simple connectivity. These two things are being improperly (nefariously, imo) tied together much like the access and content mergers - these two things simply do not belong together - access is not content is not access. I do recognize and understand the broader discussion around content and services when it pertains to inordinate impact, influence or control via overly influential and controlling services - services which, for the most part, we can still all choose whether or not to use whenever we want.

The only true and immediate threats I can currently perceive are coming from those controlling the gates to access. We've been robbed of the basic premise of title II protections for a vital communications service because we allowed the topic of discussion to change. "Network Neutrality" was never a good hook and now it has enabled the loss of focus on the core problem that is ISP service in this country. Twitter content? No so much.

I stopped thinking about ebay a long time ago. I would only consider it if it's the last seller of the thing on the planet. And I definitely do not and will not use paypal, willingly, ever.

They've done not much more than strong-arm their user base on both sides in one form or another for years.

Sorry, they're nothing but a ghost of the Internet past to this little clicker.