I love Bitter Lake and The Power of Nightmares, but cannot stand HyperNormalisation for having almost nothing to do with the book's concepts, regardless of whether it stands on its own.
1,172 karma · joined February 14, 2013
I love Bitter Lake and The Power of Nightmares, but cannot stand HyperNormalisation for having almost nothing to do with the book's concepts, regardless of whether it stands on its own.
That isn't to say that the customers are savvy and have a good understanding of different types of automated traffic and which automated traffic is harmful and which is benign. Many have a quite naive understanding that doesn't extend beyond "bots = bad, unless it's Google" and dial protection settings to the max for no good reason.
Salespeople will gladly hound engineering teams to pound out an MVP for whatever their particular prospects want this quarter, and a shiny MVP is often enough to close a deal so long as it holds up in a demo with managers whomever has purchasing power. Once that's done, sales is happy to forget about that product, or at least convince themselves that it working in a demo means it will work well in production (they lack the technical competence to see the inevitable holes that will appear down the road if the MVP isn't developed past minimum viability).
If next quarter's customers want a different set of features, well, sales will push for those, often to the detriment of fleshing out existing functionality or ensuring they're stable and maintainable. They're insulated from any pain that results from half-baked products if the people tasked with actually using products aren't those with purchasing power, and in the enterprise context, they usually aren't, and are themselves insulated from line workers who could tell them they've essentially bought a lemon, or more the promise of functionality instead of actual functionality.
Facebook have previously removed, for example, suggestive posts from Ramzan Kadyrov, which, while they did not make direct statements, were threatening: https://www.themoscowtimes.com/2016/02/02/instagram-removes-...
While Kadyrov has a more established history of following through on his threats than Bannon, I don't think it's unreasonable to come to the conclusion that Facebook does have a double standard: if you or I post "<prominent government official>'s head should be on a spike", do you think their moderation team would apply the same leniency?
I wager they would not: what we see here is part of an established pattern where Facebook's executives, and Zuckerberg in particular, do not want to be seen as biased against the right wing sentiment, because remaining in the good graces of those with political power is more important than actually upholding their supposed community standards.
Amen to that. IMO good documentation is incredibly valuable, but not in a way that aligns with business priorities. At my current job, we hear, repeatedly, that our documentation is poor, and that we need to improve it. Execs echo this sentiment, but the status quo doesn't budge.
Internally, we have about a 10:1 engineer:tech writer ratio (in a small-ish org--I assume the gap is even wider in larger orgs), and the writers are all generalists, covering every product from top to bottom. In practice, this means that engineers are asked to draft the bulk of documentation, and the writers scramble to at least copy-edit it.
Engineer-drafted documentation often isn't great, unfortunately, for several key reasons:
- Writing software is very different from using software. Engineers often don't use their own products, and writing about something you don't actually do is hard.
- It's very easy to omit details that are important for novices when you are an expert. Engineers usually have a great deal of knowledge about their own software in their brain already, because they wrote it, and cannot magically forget everything they know when asked to write documentation for someone who doesn't have that knowledge already.
- Writing effective, clear prose is hard, especially when writing about complex technical subjects for an audience with varying skill levels. Engineers don't spend the bulk of their time writing prose, and it's often not their strongest skill.
Personally, I have a mix of both skillsets because of a weird career path, but while I actually like writing documentation and am arguably better at it than writing software, there's no good reason to pursue that path: I can easily get double the salary in an engineering position as I can in a writing position, despite being a rather mediocre engineer. So I do software engineering :shrug:
The DMCA is over 2 decades old, and seemingly nothing useful has come up since. The current system seems to do not much other than provide a big stick for the RIAA and MPAA to wield whenever they get bored and try to extract rent using law that still seems stuck in some mire of player piano era logic. The last sane system I encountered was when I was doing college radio, where you had a license to play music, were required to log what music you played, and were assured that some clearinghouse would sort out the royalties that needed paying out of the aggregate license fees.
There seems to be mass confusion over what's legal on modern services like Twitch, where music is used in the same spirit as radio (background music chosen at the whim of the DJ/streamer), but isn't legal because it runs up against licensing schemes designed for including music in TV and film productions with massive budgets.
There doesn't seem to be any clear way to handle shit as any sort of small content creator, as the rightsholders seem to want to preserve some weird fantasy land where they're both entitled to complex negotiated rights deals (which make sense if you're say, some massive entity a la NBC, and want to include music in a new big budget show) while also not providing anything for the rest of society (if you're not NBC- or CBS-sized, the people who negotiate rights contracts won't give you the time of day). If you're not one of the mammoth-class media conglomerates, your options appear to be "do not use music ever" or "use music casually, and then be on the receiving end of a massive legal bludgeon". You can't get the time (or music) of day, but if you do somehow manage to get it, then you _do_ get the time of day, but in the form of massive retroactive fees or whatever that you "should" have paid had the licensing cthulu been willing to engage with you before you determined that the rightsholders weren't interested in dealing with you.
Right ol' kafkaesque nightmare, it is.
The bare-bones experience is kind of nice, to be honest, as my listening habits don't really need much functionality beyond "load a folder of music, respond to media key inputs, and scrobble to last.fm".
It's good for discovery also, since while Bandcamp Daily is a marketing tool, it's still written by music nerds who do a good job curating music from local scenes and odd genres. Indie labels also often run storefronts on Bandcamp, and are a decent way of finding the same, as most release music from their local area or with a similar sound. It's different from algorithmic discovery, and requires a bit more effort, but IMO it's worth it to explore on your own, and a fun way to learn something more about an album or track than streaming services' "Chill Hip Hop Beats To Study/Relax To"-style personality-void mood-based curation.
Bandcamp isn't perfect, to be sure. It's not as good for older music (though there are niche labels like https://habibifunkrecords.bandcamp.com/ that dig up old recordings and re-release them digitally) or big-name artists on major labels, but there's so much music available nowadays that you usually won't be at a loss for something to listen to, you just won't always be able to find a specific track as easily as on Spotify. Their mobile app also isn't great, and really needs to add a way to download tracks for offline listening, but hey, no music service is perfect, and I'm fine using a mix of both it and Spotify where one offers a better experience than the other.
You're not wrong, but...
I wish there were some alternative where we instead fixed our ossified, byzantine processes gradually over time, so that we didn't need to break out the sword arm tornado in the name of getting work done and then, in hindsight, say, "well, shame about the negative externalities, but there really just was no other way. Ah well, let's move on, everyone who isn't a pile of flesh and blood and bits on the floor tidy up. Gotta get everything clean for the next sword arm tornado."
I'll recognize that I'm a bit of an oddball in that respect nowadays, but it can work, at least with a small enough room. I love having all the conversations cross over one another and just being able to read back and follow them.
given Sonos' track record with the "lol, can't have anyone using an OLD PRODUCT THAT STILL WORKS FINE" thing i'm rather unsure we should really give them the benefit of the doubt here
ref https://news.ycombinator.com/item?id=21895086 for "recycle mode" fiasco
i was VERY confused for a second
Word. One of the things I love about Linux is that the prevalence of package management as a defining feature of a distribution is that it's almost always the case that application files are pretty well organized according to a standard (my home directories are a mess, but stuff outside is mostly pristine). Even things that aren't quite up to par you can at least clean up by just uninstalling the package--not perfect, but it generally does work.
The various companies that couldn't be arsed to fit their shit inside an RPM or DEB (not universal, but most other systems will have a functional enough means of converting a DEB or RPM until something gets popular enough that the community repackages it), or nowadays Flatpack, or even Docker (Docker has its own set of issues, but it's a decent enough isolation mechanism, certainly for filesystem stuff) are slowly re-creating Windows' mess of infinity different install/uninstall systems, all broken in their own unique small ways, and are happy to just yeet everything they need over the root directory (ah, the joys of driver installers designed by electrical engineers), are a plague on the modern Linux ecosystem.
"curl | bash" nonsense doesn't even make your installer distro-agnostic anyway--it just means that you'll slowly uncover the incompatibilities over time. Oh, your devs all use OS X, and weren't aware that BSD-lineage and GNU core utils don't all act the same, or are even entirely different, and didn't account for that? You've never encountered differences between FS layouts and your script falls over and dies because it relies on everything looking exactly like the build environment? Cool, you gotta reinvent the wheel now, and will probably do so poorly.
My fav example was a former coworker who loved to spout the adage "____ is a security company, and doing things securely is our top priority" in response to many security-related questions, but was also responsible for a set of instructions that had a "curl -k https://example.com/thing.sh | bash" line. Said engineer justified this with the rationale that the end users they worked with often had borked environments with ancient broken OpenSSL installations (or TLS intercept proxies not properly configured in Linux machines, whatever, some half-assed reason--I assure you that the download server certificates validity was not an issue), and lacked the expertise to fix them, so in the interest of expediency, they took a shortcut and didn't even bother to mark it as a problem to fix later. Our industry never ceases to impress me.
Some support manager discovered that adding those damn interstitials led to a massive reduction in human interactions (and thus cost) from a boomer population wishing to handle all account management tasks by phone conversation with a person, but at least had some percentage who could be convinced to use a website for routine tasks. We've been living with the fallout ever since.
Perhaps you and the OP would be quite happy, say, writing code for a lab that makes novel fentanyl analogues for the express purpose of including them in black-market knockoff heroin powder, which in turn leads to a number of deaths (accurately cutting in your microgram-potent meds is hard, and sometimes your downstream supply chain makes a hit that's got too high a fentanyl analogue/cut material ratio, go figure!), or an industrial system that captures unsuspecting babies to then drown them, strip their flesh, and harvest their valuable bones (not really that realistic in our normal reality, but per http://www.bay12forums.com/smf/index.php?topic=25967.0 it works great in Dwarf Fortress! or it did, anyway, until that got patched out because of said bone harvester), or hell, let's just Godwin on it and say you'd be perfectly happy writing automation tooling to make Treblinka 10% more efficient.
The respondent, whom you so readily chastise, has a quite valid point that we can't separate our engineering work from "politics" (ethics, really, but there does seem to be a side in this debate that prefers to say "politics", since that evokes more the admittedly annoying horse race electoraliasm and doublespeak-driven world of actual politics and takes away from the thrust of the issue, which is ethics, which happen to often overlap with politics but are very much their own thing) ever. That's an important thing to recognize, especially in an industry that has persistent issues with laying ethics aside in pursuit of "great inventions" (let's be pragmatic, it's mostly in pursuit of profit, with some good inventions as an occasional byproduct).
What I think the respondent may be getting at is that there is a significant population in the industry that probably does have some lines they won't cross, but is privileged and willing to cross a great many lines that won't affect them personally. You perhaps think that's a laudable stance, and you can hold that opinion if you wish, but you should do so with the recognition that there are a number of people that will see that less as a commitment to honorable professional detachment and more as a willingness to trod over the rights and wellbeing of the less fortunate so long as it doesn't injure you immediately. I'd argue that it's important thing to at least consider in an industry that often speaks of changing the world for the better--perhaps that was more it drinking the consultant kool-aid about what millenials value in their work and deciding it needed to work that into messaging, if not action, but hey, if it wants to say that, it ought to put its money where its mouth is.
Some are a bit more savvy and will take a still rather ham-fisted approach of doing so for most countries. That's not uncommon with retailer websites that realistically only serve a single country, and therefore have good enough reason to challenge all others to deter automated traffic from compromised machines outside their market.
in a sense, yes? it's not masochism, it's perhaps recognition that sometimes it does make sense to recognize that old systems are imperfect, but weren't built entirely out of toothpicks and gum, and can be retrofitted to remove their worst parts, and that strong parts do exist and can be made stronger?
the alternative seems to be that we continuously build new toothpicks and new gum, but that somehow those will better by virtue of having been forged in a modern toothpick and gum factory that puts out perfect new shiny. it definitely has no faults of its own to be discovered several years down the line, nope.
i'd say that the problem now is less a lack of simplicity and more that there just isn't a whole lot of interest in teaching practical usage and operation of the computer systems that underlie a lot of modern tech: from where i sit, /industry/ (individuals are whole different story) is interested in paying well primarily for new development both applications and infrastructure, but has decided that the quality, improvement, and maintenance are more of an afterthought. it's a microcosm of a larger human tendency to prioritize novelty, perhaps.
from where i sit, much of the opportunity for a good (well-paid) position is skewed towards greenfield development: if you can build new applications, or architect new infrastructure, great! industry loves you, and will pay you much dosh to do that. if you want to fix or improve existing things, or ensure that new stuff actually works, you're valued less.
QA/SDET as an attractive profession appears to have largely ceased to exist, cause you can just assign that work to the greenfield devs, and they can do it sorta--they'll probably focus more on new development, and the QA will suffer for it, but they'll produce enough testing and validation product to tick a box.
on the infrastructure end, architects are in great demand, but once that infrastructure is built, you don't "need" anyone to maintain or improve it, or diagnose issues as they arise. i've spent a lot of my career doing tech support work for infrastructure for odd career path reasons, and capable colleagues or counterparts are few and far between: the people i support, who maintain existing systems, seem to have not the slightest idea how they or their underlying protocols work, and other people in support roles seemingly sit on a binary divide of incredibly capable technical diagnosticians and troubleshooters and people who have been shunted into the role for lack of ability to perform in greenfield work, but can't perform in other roles either.
management has often asked me why they can't find people who are good at maintaining infrastructure or who are able to diagnose and address emergent problems, but the root of this seems quite obvious. it's not that the systems have grown too complex: they've always been complex, and while the locus of that complexity has perhaps shifted somewhat, i don't think our forebears were operating in some simple, easily-understood world that has ceased to exist. the problem is that nobody wants to pay anywhere near for an advanced brownfield skillset compared to what they'll pay for adjacent skillsets in greenfield work. the smart and capable people recognize this and move towards greenfield work even if they don't like it as much, and brownfield work is left with a sea of people who couldn't transition and can't deal with the complexity because they never could. the complexity or difficulty ain't new, but all the people that could deal with it were driven out.
the major challenges i've seen with WAFs on that front are that users treat them (and often, any part of a security solution) as a panacea for general classes of problems, which they aren't. WAFs can provide excellent targeted defense ("this request looks like it's trying to exploit CVE-2020-4521 specifically, I should almost certainly block it") and very mediocre general defense ("this request kinda looks like it might be SQLi--block it?").
the latter suffers from the issues others have raised in adjacent comments: the WAF doesn't know if the defended application applies its own sanitization (it should, but for its function, the WAF assumes that upstream doesn't, and could be vulnerable) and/or if the request content is something that reasonably should include SQLi-like content. The Cloudflare WAF in particular, at least circa 2018, suffered from including a lot of OWASP project rules that could spot "naked" SQLi quite easily, but in doing so also triggered on a lot content where the appearance of SQLi was, in fact, normal usage of punctuation characters where they made sense in plain English prose--someone can and should legitimately use quotation marks in the course of writing a prose English comment, like I'm doing right now, along with an occasional semicolon or paren alongside quotes, because those same symbols have meaning and use in both SQL and English prose.
this leads to lots of fun user confusion scenarios, where someone on the sales side of thing says "yes! enable the WAF! more protection = more product value for you!", and some months after, someone on the support side says "sorry, but the WAF can also generate false positives on legit text content, or can miss legit malicious content if it's gift-wrapped effectively (a la the OP)".
that sort of nuance is really hard to understand for more naive users, who can't easily distinguish between "the WAF blocks things it can positively ID as threats", "the WAF blocks things it mistakenly identifies as a threat based on superficial similarity to actual threats", and "the WAF doesn't block things that are threats, but are crafted to avoid the WAF". Users just see ~WAF~, and unfortunately often see it as technological wizardry that does or should just work, because it's magic. It ain't, but communicating the nuances, to a general audience? That's damn hard, and has long been neglected across industry because it doesn't fit well into shiny marketing copy.
technical improvements are valuable, but they can only go so far--at some point, there's greater value in educational content that helps dispel the magic somewhat, so that users understand the shortcomings of any given tool and can spot when those shortcomings arise. Thankfully the whole Cloudflare TV project and other educational content does seem to be progressing, though im unfortunately too far removed from the day to day now to see how well it's succeeding :) optimism hat on, it is, and godspeed!
The people in question are current students at my alma mater, where I studied, among other things, Russian language and the former Soviet Union. Some in the current class are likely studying the same, but most aren't, and even those that are, well, they're just starting to study it.
Again--no certainties there, but while I received a fairly decent US high school education, coverage of the cultural and political history of the former Soviet Union is limited by necessity--there's just not enough time to slot that in among everything else US high schoolers are expected to learn.
My gut feeling is that if I'm seeing them share this sort of content, that it's reaching them organically, not because they're finding it after a long time studying the whole of the space over a decade of hobby interest--that's where I'm coming from. The end viewpoints and values may have similarities, but they will be colored by many other factors, and those factors matter.
If that intuition is right, while we may share views in some sense, their view is quite possibly being shaped by actors whose intent is to shape it in a particular direction, who recognize that there are avenues to do so (the amplification/radicalization potential of internet content rabbit holes is well-documented at this point), and who aren't really interested in building a nuanced perspective grounded in mutual understanding of both FSU and American history.
Intuitively, based on their past actions, those actors want the opposite: to (skillfully, mind you) leverage their own nuanced understanding to craft a shallow, targeted narrative that's believable enough, with the primary goal of supporting their own agenda and political goals, not with the goal of building a strong basis of mutual understanding across borders. Is trying to reason about those aims hard, to the point of being nearly impossible to get right? Yes! Entirely! But I don't think the response warranted is "well, it's hard, we should all give up and just see what happens". We must try to instead do the best we can, both in our words and actions in a given moment and with an expectation that we won't be entirely on the mark always, but that we can and should try to watch for our mistakes and catch them as early as we can--that is how we improve and help one another.
So, to sum up, can I rule that out definitively? No. Can I make what I think is a reasonable assessment of what's going based on the information available to me and my own background of knowledge, and recognition of what's changed in the world since I made a similar journey? Hopefully, albeit worryingly, yes. I therefore think it's important to not abdicate any notion of responsibility or to call it a day and agree to disagree on a lot of the nuance--doing so tacitly grants one sort of nuance authority, and the intent behind it may not be entirely benign--historically, it hasn't, and an about face seems unlikely at this time.
It's unfortunately very much in the interest of Facebook's leadership team to discourage it, however, as a clock in clock out, see and hear no evil labor culture is good for the leaders' personal wealth, so ethics be damned, number go up.
American coverage on their efforts was by and large terrible, at least from major outlets. Focused analyst coverage in the space has been a lot more nuanced, but nobody's reading that without an existing personal or professional interest.
The other half of that analyst coverage is that they rapidly became quite tired of Maddow and friends hammering on a very simple narrative that missed the point, but was very effective at achieving its actual goal, keeping consumers of major media on the left-of-center end of the American political spectrum engaged in their content and bringing in continued advertiser money. That tiredness is relegated to water cooler discussion on Twitter, however, so it's not going to shape major outlet coverage much.
The IRA and/or its successors or friends appear to have taken the same approach as Russian security services have with the rash of targeted murders in Europe, with a "this totally isn't our doing, but anyone slightly educated on the subject will recognize our hand, because we want them to be aware that it's us and we don't actually mind people knowing" wink wink nudge nudge threadbare veneer of disclaiming responsibility.
Normally, I wouldn't really care: the 2016 stuff everyone made a fuss about on social media was largely ineffective and at best served as a smokescreen to distract from their very successful actions outside social media--Buff Bernie is a lasting meme treasure and nothing more. This go 'round, however, they've apparently learned from their mistakes, and I'm seeing.evidence that personal friends _are_ receiving and and are influenced by their messaging.
I thankfully haven't really had to watch any family or friends succumb to the Fox News media poison, and thought my social circles largely insulated from that sort of problem, but I was apparently quite wrong--right about _what_ wouldn't influence people, but blind to the idea that other actors would follow the same model and create content that _would_ suck in their target audience.
https://twitter.com/evelyndouek is a good source of reporting about Facebook and other social media cos' continued lackluster attempts to stand up potemkin independent review bodies, if you want more info on the space and can stomach more disheartening news.
when that status quo slips away, it exposes those who were merely charlatans acting the lauded part (putting on a good facade face while lacking depth in teh actual capabilities society and organizations rely on, simply fronting a good appearance)--the changes uncovers those who failed to put forth the front out of ignorance of or disdain for it. it raises those whose true strengths mattered more all along, but to which broader culture was blind to, having long lost its way tacking too hard towards praising the facade, assuming it implied the foundation
fires burn away some moss; the hardwood remains--it was always there, but now we get to see it, and further see that some of the most elegant fungus was naught but a large clump of mold growing upon itself alone, without much underneath
the printer stuff is something else. i put some fault on canon here for pushing me to unofficial sites because their official shit requires you to download a fucking exe to deliver a PDF manual (cmon, wtf, how can your docs delivery pipeline be THAT bad), but the unofficial stuff is some ninth circle of hell
the first was some bog-standard infini-redirect ad fraud crap, but the second was uh... well, i was impressed to the degree that the indian tech chop shop "YOU ARE INFECT DIAL 1-800-LEGIT-MICROSOFT TO CLEAN COMPUTER" site was able to shut down a fully up-to-date copy of firefox, somehow eating all my other tabs, grabbing hold of my mouse pointer in strange ways when the window was in focus AND preventing the windows "close window" button from killing it.
task manager was still able to execute it but damn, that was some ARTISTRY put into making the fraud site as clingy as possible--puts 90s-era malware sites to shame, and this shit kicks around on right on the first page of google search results for a printer manual query, not some shady-ass porn site you'd drunkenly click through to via 3 levels of ever-sketchier ads
people ranted and raved about goods of questionable quality gaming amazon reviews, but eh--honestly, most of those i've bought were fine, if not artisanal high-end shit--they just engaged in a lot of dubious "get free shit for a good review" growth hacking tactics that are A-OKAY THATS JUST HOW YA DO BUSINESS when it's some SF startup pulling the same crap in a different form. it's weird how seemingly nobody gives a fuck that a lot of google searches will boost things that are far worse--offering purestrain fraud on a platter is fine, selling mediocre flash drives and kitchen gadgets with inflated reviews is THE HIGHEST OF CRIMES
There's a legitimate case for high-density, specialized interfaces that aren't focused on usability in the sense that you might find in more consumer-targeted software: the end users of these systems don't necessarily need something that's easy to learn or that presents only important info up front. Arguably they need the opposite: something that packs a lot of complex functionality and dense information into a small space is _good_ when your users are highly-specialized and frequently run through similar complex workflows. It's akin to a phone camera interface and a camera designed for professional photographers: the former eschews having ALL THE THINGS for accessibility, whereas the latter eschews accessibility for high info density and rapid access to tools because its users are okay putting in the time to learn something complex when getting over the learning curve will afford them a high degree of control and quick feedback.
Where things break down is customizability: expert tools, and especially expert software tools, suffer from "the user knows best, they can design their own UX" syndrome: this is true to a degree, but in the case of shared tools oft turns into one user (team lead X, who's been doing this shit for years! they know their shit!) designing something that works for them, or that replicates an existing workflow from elsewhere (just make it EXACTLY like the old paper charts! why would you do anything else? what do you mean the design considerations for a paper system might not perfectly transfer to a computer system?) in total ignorance of things they fail to do well. Computer systems, I think as an artifact of their relative novelty, lead users to believe they're experts in UX design by virtue of having (a) experience in the field the system serves and (b) having used a computer interface at some point in the past (and, in America, (c), broader cultural hubris about individual competency across disciplines based on competency in some unrelated highly-skilled field). Designing a truly good interface requires a dialog between user and designer, but we too often tend towards a "skilled user must be right, they're good at SOMETHING and therefore good at EVERYTHING" mindset. Enterprise software design provides customizability to a fault--we hear users want it, don't have enough time to actually sit down and try workflows with them, and they say they're skilled enough to do it themselves independently, so let em have at it.
I sometimes wonder what it'd be like in a world where "cars" were sold to ENTERPRISE DRIVING CABALS, full of VERY SKILLED DRIVERS, where the "car" in question ended up being a pile of sheet metal and control surfaces, a collection of engine and power train components, a big tub of asphalt, and a rough map of places people need to go, entrusted to a multitude of very experienced horse carriage drivers who each sought out to build their own bespoke personal vehicles and interstate highway system as they saw fit based on their own intuition and cunning, with nary a notion of needing to design something that worked for anyone else or wanting to take advantage of the new tech's more novel features. I doubt it would be a good one, but it would probably be hilarious to look at having driven on a somewhat saner system in a more thoughtfully designed vehicle.