seorphates

pp is not on the wrong track. The first is clearly under assault from several quarters. Without the first we cannot even question authority much less dig in and speak about it. The second seems meant to shore up the first. I guess you have to try to think a little like a man that has only just gained his freedom and whose aim is hold and maintain that freedom for all of his and on equal footing. How would you proceed?

Either way, the costs are only ours to bear and Ms. Rudd's fantastically dystopic sales pitch seems to be selling tickets like hotcakes for a fast moving train.

The blatant assaults have become vicious. There is no authority over minds. We mustn't allow the mere access to information the means to determine or contain the freedom of the mind much less our bodies.

First they came for the children and then they came for the drugs. They are currently coming for "terror" and ache to expand that access without burdens or bounds. They will not stop until they have everything, which we must not permit.

Sure. But given recent events and the increasingly blatant escalation of government power over its people it starts to become more clear that, at the root of it, "freedom of speech and of the press" means exactly that which our current governments fear the most and desperately aim to control - the freedom for all to research, dig and question the authority that governs them. It has almost become a simple interpretation. Which brings us to the second.

Complicate that with the fact that through generous corporate sponsorship we now seem to find our collective selves being led by all manner of wolves.

I'm not quite sure I can be hyped. It's worth keeping an eye on. The core dbms is relatively easy to carry and with some careful considerations can be formed and firmed up quite nicely. The irony is the that thicker the oracle kit the more intricate, delicate and expensive it becomes. Storage, db engine, memory and.. cluster ware? Nope, that bird can-nah fly.

Nice database you got there, it'd be a shame if it couldn't grow. Eight figures later.

If ml can expect, select and plant my data closer to the end user then my core rdbms engine can grow, otherwise you're just moving pieces on the monopoly board. Fat pipes, willing victims and a little ingenuity can go a long way.

Sooo, no UNIX, then?

I find myself wary of the long tail on this one. When wars fade into enforcement then rights fade into privileges.

I don't understand your first statement. I thought that if you wrote your own function/routine/blah you can have it return anything you might like to handle - in one side and out the other.

{print_this_garbage_out=`do_a_little_dance` #maybe even with awk|sed|perl|python|sql|mom

retval_for_something_hopefully_cool=$? # or some other requisite test/set, limit sky

echo "${print_this_garbage_out}"

return ${retval_for_something_hopefully_cool}} # don't exit, because that might be silly

The bash is sort of like your machine code, it, like your machine, can use anything it has access to, if told properly. So I don't understand "can't even return a value". I don't know much about bash for bash's sake so I'm wondering if I may have missed something along the way.

Sure, sure. I only rejected the implication that I was somehow ignorant of the factors involved and just la lala painting with a broad brush of simplicity and righteousness that was somehow at odds with your perceptions. Apart from that I'm pretty much in agreement with your opinion. The reality, for most, is that remote is still the black sheep of options and that only if it's an option. I have zero against an open office plan if those that provide them embrace all the options. I am fortunate enough to have exactly this situation. I have a haul into the (open plan) office, which I love (the haul), mostly because I have three pedals and fast roads but the burning of a few of the days hours to get there and back is more wasteful than not. Far too many are put into the position of long commutes and, omfg, astronomical costs of living to get just a teensy bit closer. I think my only real point, apart from providing just another opinion, was that if capable employers embrace these options in totality then the human condition could be a bit better off for it - open plans or not.

These are just opinions, right? Right. We both have valid ones that are actually pretty closely aligned. We seem to both appreciate our fortunate circumstances which are, for the most part, at opposite ends of the "we're fortunate" spectrum. I regret having inadvertently annoyed you, but, in all respects, you shouldn't be annoyed with anyone's opinions simply because they seem to not be like your own. I think we're good here. Are we good here?

It's sort of telling how far out of my way you went to form an argument against something you manifested all by yourself.

You're a bike ride away from the office that you prefer? Fantastic job of deflection.

It's rather obvious that there are trade-offs, isn't it? It's pretty clear to me, at any rate, and there's nothing inherently wrong with providing an office. Shame on your words coming out of my mouth.

In relation to the expense of providing "office space" for several hundred the cost of a fat pipe is pretty darn cheap, were that it existed.

If you don't have the need to live where you work there are "simple" choices any given person can make that will make their lives easier, happier and, hopefully, more fruitful for both themselves and their employers.

And besides, having worked in offices (real ones), cubicles (and half-ones), bullpens and open spaces (including fields) I feel I am more than qualified to provide my own opinion on the matter without implying that my "simple" opinion is somehow not compatible with your own.

Open spaces suck to work in. It's that simple.

For. Sure. I have difficulty with lively sensory input conditions. In a nutshell I will, by default, listen and hear every conversation within ear-shot. It can be a huge effort when attempting to carry a discussion when among many.

Not too mention I reflexively am willing to snark at anything I hear, no matter who's speaking. That can get uncomfortable, too, but in different ways.

That's one of the reasons I wave one of those tech-broad-brush-anti-social banners around - Internally I'm interacting with everything around me. That can be hard. I demure when the option is available if for only to manage my senses. I'm so misunderstood.

Working in open office plans is simply awful.

Personally I believe remote work, for any tech-enabled employer, makes the most sense. The impact on infrastructure by removing commuting alone could maybe help save the planet. And our collective sanity.

Wouldn't it be nice to have ISPs that can provide an infrastructure that could actually support that? I think so.

The hideous effects of cluster-fucking hundreds of thousands of people daily just needs to stop. Tech companies are guilty. They're huge and, humbly opined, are idiots for making it worse and not really needing to. Top that off with an open floor destination and.. damn, work is beat.

duckduckgo hackernews whatthefuckjusthappenedtoday arstechnica wavecam/buouy reports/any

but these are just for today, I can't remember yesterday.

Yes, you're not wrong. I tend to think of the slightly larger, more complex scopes having multiple programs with many teams when looking at these things lately. This is just a small example of an impetuous reply not adding value and it didn't even reflect any real opinion that I may or may not hold.

I'm about a decade removed from any real "two-box shops" (small and/or startup focus etc.) and so sometimes think they can't possibly exist anymore. I see a few of the "we want the world" job postings and experience burnout just reading some of them.

"Pragmatic engineering" I like the sound of that but I'd secretly hope it's not meant to rhyme with "best practices" - I like good practices and all but I like and appreciate the actual games much more. :O) That's just a small parting snark - mostly harmless. Best of luck on your search! I'm trying to maintain some focus on data operations at the moment but with any luck my next jump attempt will be into something counter to current trends.

Is that one job or four? I see four distinct engineering disciplines in your post - Site Reliability - DevOps - Compute - Storage. The only two I would reasonably consider combining (in a day-to-day combined way) are the last two and even that's a risk for any largish operation. The first two do not benefit being combined and neither will garner the attention required to succeed. I would not apply unless you were small, generous and good to your community. Buy hey, if you threw in networking and security I'd know you have two boxes and need help and I'd bite out of sheer curiosity, like a shark, testing, tasting.

Most of the responses here so far that do not include some sort of a guide are not the responses you're looking for (imho).

Mind your pipes and quotes. Guard your variables with braces. Do not export everything, test for and (try to) handle return codes and conditions and keep it simple (emphasis simple) but most of all just write it.

BASH (or Bourne) is ubiquitous when dealing with systems (vs programs). You don't need to be on the fashionable lang of the day by any measure. BASH, for most cases, will always be there, always ready and, in most cases, is the default human interface for deployed systems. As scripting languages go you don't need "better", you need dependability, zero dependencies with no requirement for modules or any other whizbangwoohoo plug-in. Language Fashionistas and personal preferences aside at least some level of fluency with BASH should be mandatory for anyone interfacing with a system.

100% correct - UUID strings are ASCII < 128 .. but there are imposters for character code 45 ("-"). Assumption based approaches to conversions or field handling should not be assumed to be safe ones just because UUID is "technically" ASCII. Only the keeper of the field can truly enforce that constraint.

In dealing with conversions or characterset handling the UUID pitfall is the hyphen. This is an extremely vulnerable character when dealing with multiple data handling and feed sources (to say nothing of data conversions).

The hyphen has a handful of imposters and one of the more troublesome ones is in extended ASCII as "en dash" (there's another as "em dash"). These do not have a direct mapping to unicode as they are not "hyphens" but they sure do look like them to humans in a hurry. It will throw your meticulously thought out and implemented keys (or any other well-measured column) into a tailspin. Dealing with extended ASCII implementations has been the most hazardous area of characterset handling, at least for me.

Although probably unlikely the UUID is not a guaranteed direct ASCII to UNICODE conversion. I'd advise awareness and perhaps even some level of caution if you have a complex data flow (or, more apt, a seemingly ridiculously simple and bulletproof one).

Extended ASCII sucks so if you use it and don't have one or both feet nailed to the floor then get off of it, sooner.

That's one of those things where money can go a long way quickly - fat i/o (including network if you're off-loading, sharding, peering, vdbs etc.), good cpu, efficient log sizes. Sticking to the basics is probably the best - if you're running high transaction and data change rates then the collective throughput "off" of your transaction server(s) is every bit as important as the throughput "on" the server(s).

It looks like you're just talking about a good, old-fashioned, well-built operations team.

In DevOps there is no "I can't run npm" unless the new guy is building his first personal env. In DevOps ERRNO scrolling down the screen means your kit is broken and you need to rebuild it to a known, working state, yourself (and crap like that certainly wouldn't be making it into production). In DevOps the entire organization is on board. Everyone has a role even if it's just feedback or a ring-ring fielding phone jockey and they'll know why and they'll know it's an important contribution because every lost piece of information affects delivery and quality.

If you're automating, integrating, designing, orchestrating, trouble-shooting or just about any other ing-ing you can think of than you're an engineer and you can front that with whatever you like be it systems, integration, quality-assurance, software, application, automation, monitoring, cloud, reliability, hardware, database, support, etc. etc. and even devops, if you like.

The difference is whether the organization you're doing all of your "engineering" for has accepted and/or is applying the DevOps "method".

I've perused some "DevOps Engineer" postings and a good amount of them look like garbage idolization of this or that toolset combined with looking for someone they can beat on until their infrastructure works like they think they'd like it to.

DevOps ain't infrastructure and it certainly isn't ace dev guy running the prod kit and no, it's not about "enabling" developers either. It's an operation comprising the entire cycle of delivery with expectations and requirements from all members.

Given the case of some new startup and they're on the hunt and poised to ramp then what they're really looking for is a savvy engineer (or 12) that can ing-ing all. day. long.

Sadly, because of business overlays and buzz-wordery and agile styles and .. certain software stacks, a more than fair share of time gets sucked right out of the actual developing and operating parts, especially if there's any palatable resistance to acceptance but, alas, it really is just another thing fronting ing.

On my OSX box (mbp) the context menus and popups are horridly misplaced and popup in random locations on the screen. For the popups the pointer is also often completely misaligned with the menu items requiring item selection to be clicked dozens of pixels away. I've also long given up throwing TB to a different display - text, UI sizing and menus explode and it becomes unusable on any other monitor.

Having said that it's still the best email client software I can find - UI issues aside.

Classification is provided by the government, internal to the government ergo a citizen that is neither government nor contractually associated with said government can read anything they like.

To ensure that test kits, catches and patches prevail. But that's only a guess.

God said: OK, now that they're done bashing each other and I'm no longer at risk of loosing the lot so let's get back to business.

But then that gets shattered because, well, because we just bash with drones and chemicals.

So I, at least, find myself back at square one... : The planet is dying and you have the capacity to launch 25,000 people in one direction with one hail mary. What do you do?

Yeah, we definitely need to get our evolves on. The odds still seem pretty stacked against.