Meta tags:
keywords=devops,testing,lean,code,quality assurance;

Headings (most frequently used words):

is, how, to, software, for, you, the, of, know, in, testing, and, as, rot, programming, it, other, miller, jq, csv, data, infinite, undo, do, what, stuff, can, test, change, works, large, organizations, see, connections, between, observability, devops, toad, feedback, engagement, phenotypic, conformance, analysis, engineering, hypothesis, invalidation, suboptimization, reason, technical, debt, but, have, go, outside, world, find, discussion, uncomfortable, truth, that, dev, complex, relationship, with, an, increasingly, intelligent, like, tabular, here, use, pipe, into, vs, checking, concern, trolling, instance, however, full, list, narrative, posts, historical, reasons, frictionless, yet, still, wears, out, soft, skill, hard,

Text of the page (most frequently used words):
the (99), that (52), and (39), with (25), software (25), for (17), have (15), are (15), testing (13), can (13), this (13), not (12), you (12), because (11), how (11), but (9), rot (9), time (8), from (8), csv (8), all (7), lot (7), #programming (7), then (7), jun (6), other (6), such (6), people (6), they (6), about (6), test (6), discussion (6), devops (6), systems (6), code (6), one (6), think (6), system (6), hypothesis (6), process (6), sun (5), like (5), checking (5), don (5), what (5), cartesian (5), data (5), using (5), engagement (5), much (5), life (5), narrative (5), implementation (5), history (5), language (4), most (4), them (4), their (4), yet (4), only (4), policing (4), problem (4), out (4), view (4), will (4), find (4), which (4), miller (4), need (4), uncomfortable (4), requirements (4), program (4), nor (4), subsystems (4), day (4), features (4), change (4), complete (4), specification (4), feedback (4), analysis (4), observability (4), development (3), makes (3), feel (3), bad (3), some (3), reason (3), been (3), first (3), around (3), form (3), fucking (3), concern (3), itself (3), see (3), when (3), must (3), between (3), computer (3), quality (3), comes (3), pretty (3), well (3), just (3), work (3), sort (3), mon (3), noahsussman (3), truth (3), dev (3), complex (3), relationship (3), increasingly (3), intelligent (3), over (3), books (3), example (3), ignored (3), its (3), has (3), long (3), programmers (3), learn (3), way (3), call (3), optimally (3), begin (3), same (3), after (3), cycle (3), fact (3), phases (3), more (3), standard (3), events (3), composed (3), discrete (3), modern (2), 4th (2), behavior (2), either (2), explain (2), already (2), everyone (2), written (2), place (2), who (2), far (2), trolling (2), point (2), establishing (2), often (2), revolves (2), whether (2), human (2), assurance (2), easy (2), json (2), working (2), even (2), use (2), source (2), currently (2), tool (2), xml (2), found (2), results (2), achieve (2), here (2), tabular (2), wed (2), june (2), tentacular (2), suboptimization (2), technical (2), debt (2), outside (2), twitter (2), world (2), discourse (2), despite (2), successfully (2), dealt (2), those (2), old (2), server (2), environment (2), hard (2), boot (2), believe (2), topic (2), changes (2), phenomenon (2), agreed (2), idea (2), good (2), solutions (2), social (2), squishy (2), problems (2), production (2), contains (2), suited (2), functioning (2), observed (2), upon (2), any (2), come (2), sense (2), past (2), legacy (2), historical (2), instance (2), web (2), database (2), full (2), list (2), always (2), front (2), hacker (2), news (2), aug (2), impossible (2), since (2), thing (2), both (2), very (2), your (2), kübler (2), ross (2), curve (2), six (2), organizations (2), know (2), new (2), codebase (2), important (2), properties (2), static (2), existing (2), phenotypic (2), conformance (2), describes (2), ruleset (2), open (2), may (2), developers (2), rate (2), respond (2), prediction (2), formal (2), predict (2), safety (2), comprehensible (2), framework (2), frames (2), reconstructed (2), connections (2), toad (2), infinite (2), undo (2), older, vision, sympoietic, praxis, interrupting, professionals, corret, trivial, choices, uncool, best, viewed, dispassionate, light, elitist, immature, alienating, won, put, wasted, persists, personally, interrupted, least, times, interruptor, isn, yeah, motherfucker, knew, give, shit, becasue, perspective, minutia, takes, three, while, speaking, conference, aka, tone, seen, take, correcting, choose, identify, automators, activities, common, biggest, goes, agile, community, microagressions, stop, apologize, jerks, chain, though, god, damned, bothers, although, division, fashion, luminaries, myself, certainly, utility, certain, foundational, local, taxa, architects, short, effected, role, divide, meme, under, leading, sqa, conferences, today, including, gtac, stpcon, star, cast, various, selenium, confs, troll, rationalwiki, 11th, now, structured, spent, learning, enjoy, mlr, c2j, cat, my_file, anyway, solves, install, homebrew, compile, choice, processing, sorts, except, handled, never, parsing, liked, make, honest, substandard, xmlstarlet, pipe, into, awk, sed, cut, join, name, indexed, tsv, 12th, illustration, funnel, foss, developer, 14th, 2015, 2017, pic, com, skjykuvv4o, https, cgtn57mrt4, 18th, recent, movement, toward, thinking, hopeful, sign, concerns, deal, changing, hasn, forthcoming, growth, hype, last, ten, years, knowledge, locked, away, couple, side, java, sell, junior, engineer, fresh, camp, undergrad, recognizes, importance, sure, feels, comfortable, giving, advice, almost, term, subsystem, upgrades, solving, taking, commonly, solution, management, job, interviews, performance, evaluations, part, contraventions, listed, general, taught, coding, camps, literature, documented, known, engaging, opportunity, heuristics, would, allow, distinguish, issues, soft, skill, understood, area, does, science, contribute, algorithmic, environmental, aesthetic, words, space, taken, humans, collaborators, course, state, meaning, satisfy, empowered, group, stakeholders, inevitably, exhibit, bugs, related, hosting, called, caused, continue, evolve, hands, users, frictionless, still, wears, might, considered, did, function, there, concept, metaphorically, encapsulates, precede, bit, canonical, definition, reasons, predictable, lived, product, eventually, outgrow, service, begins, single, monolithic, scales, capacity, increase, distributed, original, activerecord, orm, was, replaced, variety, databases, services, dependence, 25th, posts, exciting, page, thanks, upvoting, post, fri, thorough, exploration, read, refer, back, peter, naur, 1985, theory, building, levels, stack, case, functionally, could, exist, largest, application, derpiest, cannot, implemented, built, iteratively, via, validation, hypotheses, hello, corollary, consider, implies, design, programs, constrained, laws, nature, incomplete, proceed, said, decide, modifying, repeating, implement, pattern, prefer, holds, writing, different, haven, enough, own, admittedly, controversial, opinion, everything, activity, subset, engineering, invalidation, sep, 3rd, hope, infographic, helps, every, initiative, portfolio, together, project, two, tested, ways, visualizing, cope, works, large, jul, 2nd, diagram, stuff, applied, epistemology, brett, pettichord, nov, 5th, initial, loop, changesets, resemble, gets, speaks, consistency, absence, syntax, errors, without, resorting, normative, risks, fit, practices, lead, bikeshedding, practice, based, rather, than, voted, team, tue, 28th, metric, where, engage, rates, calculated, measurement, tools, facing, email, frequency, slack, announcements, obviously, failing, tests, fixed, 29th, operate, mainly, off, taxonomies, failures, try, derive, ontologies, address, reactive, follows, order, great, specificity, means, future, embedded, reaction, prior, stupidity, accept, little, o11y, culture, resiliency, btw, obliquely, being, gotten, clay, shirkey, quote, however, techniques, nice, necessary, finite, luck, explaining, why, lets, quickly, unknowns, conversely, rooted, traditional, edited, mental, model, disciplines, naturally, become, obvious, sat, 24th, sharealike, 2025, noah, sussman, reading, articles, bullet, falsehoods, mining, git, log,

Text of the page (random words):
noahsussman infinite undo infinite undo data mining in the git log bullet falsehoods about time software as narrative how to articles devops reading list cc sharealike 2025 by noah sussman aug 24th sat how to see the connections between testing observability and devops toad i think that if the mental model one is using is like the new view on systems safety then the connections between the disciplines in toad testing observability and devops naturally become obvious as you work more and more with software systems conversely for people rooted in the traditional cartesian view of software systems it s pretty much impossible to explain edited for instance if i think that the history of a software is composed of discrete finite frames of time that can be reconstructed after the fact then good fucking luck explaining to me why i need an observability framework that lets me respond quickly to unknowns because if i think history is composed of discrete comprehensible frames that can be reconstructed after the fact then i have a lot to learn from the system out of that history your observability and prediction techniques are nice but not necessary however if i don t accept that history is composed of discrete comprehensible events then i have very little to learn from history and then the o11y framework and the culture of resiliency makes sense this is btw what is obliquely being gotten at in the clay shirkey quote process is an embedded reaction to prior stupidity it means people with a lot of process are people with the old cartesian view of system safety they have a lot of process because they think they can predict what sort of events will be important in the future since formal process is reactive it follows that in order to have a lot of formal process we have to have a lot of events we can predict with great specificity people who operate mainly off of prediction just don t think that way we don t come up with taxonomies of past failures and try to derive ontologies that address them may 29th wed feedback engagement feedback engagement is a metric that describes how often and where developers engage with feedback from the ci system engagement rates can be calculated using all of the standard engagement measurement tools from production facing systems email open rate the frequency with which developers respond to slack announcements and most obviously the rate at which failing tests are fixed or ignored may 28th tue phenotypic conformance analysis phenotypic conformance analysis describes the practice of establishing a static analysis ruleset based on the observed properties of the codebase rather than on an existing open source standard or a ruleset voted upon by the team then the initial feedback loop revolves around how much new changesets resemble the code that is already in the codebase this gets at the important properties that static analysis speaks to consistency and the absence of syntax errors without resorting to a normative standard that risks a bad fit with existing practices and can lead to bikeshedding nov 5th mon how do you know what you know testing is just applied epistemology brett pettichord stuff you can test a diagram jul 2nd mon how change works in large organizations the kübler ross change curve and the six phases of a project are two time tested ways of visualizing how organizations cope with change here the kübler ross curve and the six phases are together for the first time i hope this infographic helps to achieve every initiative in your portfolio sep 3rd sun software engineering as hypothesis invalidation if testing software and writing code feel very different to you it s only because you haven t written enough code yet that is only my own admittedly controversial opinion i believe that everything we call software testing is a subset of the activity we call programming implementation is a test of a hypothesis to implement a pattern in code one must first form a narrative or if you prefer a hypothesis implementation is itself a test of whether the narrative holds up corollary consider that the full specification for a program and the program itself are the same thing this implies you can t design computer programs by up front complete specification you are constrained by the laws of nature to begin with an incomplete hypothesis and proceed by testing the implementation of said hypothesis using the results of that test to decide how to go about modifying either the hypothesis or the implementation or both then repeating that process at all levels of the stack it is always the case that complete specification is functionally impossible since such a thing could only exist in the form of a complete implementation the largest web application and the derpiest hello world program both have this quality that they cannot be implemented by complete specification but must be built iteratively via in validation of hypotheses for a much more thorough exploration of this idea you can read or refer back to programming as theory building by peter naur 1985 aug 4th fri software is narrative hacker news thanks everyone for upvoting my post on hn it s always exciting to see my work on the front page of hacker news full list of software as narrative posts jun 25th sun software rot software rot the software development life cycle is predictable in that any long lived product will eventually outgrow some of its subsystems for instance a web service that begins life with a single monolithic database server will as it scales need the capacity increase that comes from a distributed database a historical example can be found in twitter s original dependence on the activerecord orm which over time was replaced with a variety of databases and services for historical reasons in one sense this might be considered as a canonical definition of legacy systems the system contains subsystems that are not optimally suited to day to day functioning despite the fact that at some point in the past those same subsystems did function optimally there is a concept of software rot or bit rot that metaphorically encapsulates the life cycle phases that precede this sort of legacy system frictionless yet it still wears out the observed course of the software development life cycle is that features begin life in a working state meaning that they satisfy the requirements agreed upon by an empowered group of stakeholders but that inevitably the same features begin to exhibit bugs that are not in any way related to changes of code nor hosting environment software rot as this phenomenon has come to be called is caused because the requirements for features continue to change and evolve even after such features are in the hands of their users the system contains subsystems that are not optimally suited to day to day functioning this is not a well understood area of software production nor does computer science have much to contribute by way of solutions the problems are not algorithmic but environmental social aesthetic in other words it is what programmers like to call a squishy problem because so much of the problem space is taken up not by software but by humans and their co collaborators in programming soft skill is hard the idea of engaging with squishy problems is uncomfortable to a lot of programmers i think this is because programmers currently do not have an opportunity to learn the heuristics that would allow them to distinguish good solutions from bad when it comes to human and social issues taking software rot as an example it is a well known phenomenon long documented in the literature of software yet it has no commonly agreed up on solution its management is not a topic of discussion in job interviews nor in performance evaluations for the most part the contraventions for software rot are not listed in general programming books nor taught in coding boot camps i do not believe that software rot is ignored as a topic because no one recognizes its importance i m pretty sure it s ignored because no one feels comfortable giving advice about it because almost no one has successfully dealt with the long term requirements changes and subsystem upgrades that go with solving software rot the knowledge about how this problem have been successfully dealt with are locked away in a couple of books and those books are old using server side programming and java as their example environment that s a hard sell to a junior engineer fresh out of a boot camp or undergrad program the recent movement toward systems thinking in software is a hopeful sign but we need modern discourse that concerns how to deal with changing requirements over time and so far such discourse hasn t been forthcoming despite all the growth and hype about code over the last ten years jun 18th sun suboptimization is the reason for technical debt but i have to go outside of programming world to find discussion of it suboptimization is the reason for technical debt but i have to go outside programming to find discussion of it https t co cgtn57mrt4 pic twitter com skjykuvv4o tentacular devops noahsussman june 18 2017 the uncomfortable truth is that dev is a complex relationship with an increasingly intelligent other the uncomfortable truth is that dev is a complex relationship with an increasingly intelligent other the uncomfortable truth is that dev is a complex relationship with an increasingly intelligent other tentacular devops noahsussman june 28 2015 jun 14th wed an illustration of the funnel for foss developer engagement jun 12th mon miller is like jq for csv and other tabular data miller is like awk sed cut join and sort for name indexed data such as csv tsv and tabular json here s how i use miller to pipe csv data into jq jq is currently my tool of choice when it comes to processing all sorts of data except xml and csv xml is pretty well handled by xmlstarlet but i have never found a csv parsing tool that i liked i just make do with using jq to work with csv and to be honest i find the results i can achieve to be substandard anyway miller solves all that and is easy to install even if you don t use homebrew and need to compile it from source mlr c2j cat my_file csv jq it is that easy now my csv is structured as json which i have spent a lot of time learning to enjoy working with in jq jun 11th sun concern troll rationalwiki testing vs checking testing vs checking you will find this meme under discussion at all of the leading software quality assurance sqa conferences today including gtac stpcon star cast and the various selenium confs in short the discussion revolves around whether a cartesian divide can be effected between the human and the computer s role in software quality assurance testing vs checking it is not the discussion itself that bothers me although cartesian division is out of fashion with devops luminaries such as myself i can certainly see the utility of a cartesian point of view when establishing certain foundational local taxa as we test architects often must do concern trolling what jerks my fucking chain though is the god damned concern trolling the biggest problem by far is all the fucking language policing that goes on in the testing and in the agile community language policing is microagressions stop it and apologize the most common form of language policing aka tone policing that i ve seen take place around testing vs checking is correcting people who choose to identify as automators of test activities i ve personally been interrupted while speaking at a conference at least three times only to have the interruptor explain that checking isn t testing yeah motherfucker i already knew that and i don t give a shit about it becasue from my perspective that s minutia that everyone takes as written in the first place interrupting other professionals to corret trivial language choices is uncool at best viewed in a dispassionate light such behavior is elitist immature and alienating most people won t put up with that either because it makes them feel bad or because it makes them feel like they ve wasted their time yet the behavior persists for some reason jun 4th sun a modern vision of testing as sympoietic development praxis older