structures – Priyank Verma

September 2, 2018

A plea for lean software: 6 Lessons I learned to help keep software simple

Preface Recently, I was browsing the codebase of my company and saw that it has three versions of dashboards for an analytics page in it. I am pretty sure that customers don’t need that. This sparked something in my naive brain and I started exploring the internet for related ideas. That’s when I found…

Software Engineering

“FAT, (or, –, 1., 10, 2., 3., 4., 5., 6., A, abstractions, acceptable, accommodate, accurately, add, adding, admiration., age-old, ago., aids, all, allows, also, am, an, analytics, and, any, appropriate, architecture, are, armies, as, at, available, away, baffling., be, because, become, belief, better, bigger, brain, browsing, built, bulky, But, by, can, cannot, cause, causes, changed, changes:, code, codebase, communication, company, compared, compiler, complex., complexity, components, conceivable, Conclusion, confidence, consider, consumed, continue, curtail, customers, customized, dashboards, decomposed, decomposition, degree, deletion, deliberately, deprecated, design, designed, designers, designing, detail, detailed, development, disagree, disciplined, discussed, does, doesn’t, Don’t, duplication., each, either, Enhanced, enough, entire, entirety, errors, essential, essentials., etc., even, every, expands, experience, exploring, explosion, extensibility, extensions, extent, faster, feature, features, fill, Finding, first, flexibility, following, for, foremost, form, found, from, functional, functionality, get, getting, goal, grows, hard, hardware, has, have, help, hierarchy, higher, holds, hope, how, huge., I, I’ll, ideas, if, ignored, important, improve, in, incompatibility, Incomprehensibility, increase, increased, individual, influenced, insanely, interfaces, Internet, into, introduction, irrelevant, is, It’s, it., justify, keep, keeping, key, kill, killed, languages, largely, laws, lean, Learned, least, lessons, Let’s, lies, like, live, machines, main, maintainability., Make, Making, me, measured., memory, methodologies, mind, minimizing, modern, modules, Monolithic, more, most, much, must, my, naive, need, needed?, needless, nerve, never, new, No, Not, now, number, of, on, one, order, original, outset., over, page, paper, part, passes, Patterns., people, pinpoint, place., Plea, PM, post, power, predominant., Preface, prerequisite, presented, pressure, pretty, primary, probably, problems, programmers, programming, proper, quantity becomes, rapidly, reacted, reason, Recently, reduce, Reducing, reflect, related, release?, remember, remove, rendered, required, requires, resonated, Resources, responses, responsibility, return, root., run, saw, seem, sell.”, sensitive, should, significant, similar, simple, simpler, single, size, slower, small, software, Solution, some, something, sophistication, sparked, specification, standard, started, state, step, Still, streamline, streamlined, Strongly, structures, suggested, sure, suspicion, system, systems., take, taking, teach, team, teams, than, than quality. Every, that, that’s, the, their, them., there, these, things, this, three, time., to, Today, toll, too., tools, topic, touch, true, two, typed, understood, unrecognized., us, usage?, use, user, versions, very, was, way, we, were, what, when, which, while, with, write, wrong., years
May 5, 2018

Organization Archetypes And The Concept Of Market-Oriented “Solver Teams”

Organizations which designs systems are constrained to produce designs which are copies of the communication structure of the organization. In other words, how we organize our teams has a powerful effect on the software we produce, as well as our resulting architectural and production outcomes. Thus, in order to get a fast flow of work from…

Uncategorized

“E-Shaped”, “Solver, A, a bunch of, a fast, able, admins, advantage., Advantages, all, also, an, analysis, and, Another, Archetypes, architectural, architecture, are, areas, as, at, attempt, be, because, becoming, being, benefits, bring, Broadly, business, But, call, called, can, capabilities, centralize, combine, communication, complicated, composed, comprehensive, conception, Conclusion, constrained, contribute, copies, cost., coupled, covering, cross-disciplinary, cross-functional, customer, data, deliver, delivery, dependencies, deployment, design, designs, develop, development, DevOps, disciplines, division, done, dramatically, each, effect, Enable, Enables, enabling, engineering, engineers, entire, etc., ever, every, Ex., execution, experiments, expertise, experts, fast, faster, feature, flat, flow, folks!, for, from, functional, Functional-oriented:, generalist, get, great, has, have, having, helps, hierarchical, high, highly, how, idea., impact, improves, in, increasing, independently, inform, innate, instead, interesting, is, it., knowledge, launch, learning, like, machine, major, managers, market, market-oriented, marketing, Matrix-oriented:, matrix and market., member, members, move, much, multi-specialist, multiple, must, nature, needs., Not, number, of, on, only, operational, Operations, opportunities, optimizations, optimize, order, organization., Organizational, Organizations, organize, orientation., other, our, outcomes., overwhelming., own, person, plays, point, points, poorly, powerful, prevent, primarily, problem, problems, produce, production, provides, quality, quickly., Reducing, rely, reporting, respond, responding, responsible, resulting, results, retirement, safely, same, saw, Server, service, services, single, small, smoother, software, solve, solving, speaking, specialist, specialists., speed, Squad, SREs, start, stream, stream: functional, structure, structured, structures, successful, support., systems., tall, team, teams, technologies., tend, testing., than, that, that’s, the, their, them., there, these, they, they’ll, this, three, Thus, tightly, to, tracking, types, user, value, waiting, want, we, well, when, which, who, with, without, words, work, working

Tag: structures

A plea for lean software: 6 Lessons I learned to help keep software simple

Organization Archetypes And The Concept Of Market-Oriented “Solver Teams”