system – Priyank Verma

October 5, 2019

Trying to Wrap My Head Around The Dynamo Storage System: A Deep Dive

Introduction The world of databases is very interesting. To build a loveable product, a core infrastructure piece that’s needed is the data persistence layer. I find this data persistence layer to be like a tip of the iceberg, the get and the put calls have so much going under the hood that it’s mind blowing…

Software Engineering

AWS, database, design, dynamo, dynamodb, engineering, software, system
April 28, 2019

Introduction to LSM Trees: May the logs be with you

This post is a part of a newsletter that I run: “Scamming The Coding Interview“, which is geared towards helping people ACE their coding interviews. We send a coding question on weekdays along with a system design article like this one on weekends. Do subscribe If you find this article valuable. Introduction What will be the simplest…

Software Engineering

casandra, coding, database, db, design, interview, lsm tree, system, the
January 6, 2019

How To Objectively Reason About Systems: Correctness Properties Of A System

This post is a part of a newsletter that I run: “Scamming The Coding Interview“, which is geared towards helping people ACE their coding interviews. We send a coding question on weekdays along with a system design article like this one on weekends. Do subscribe If you find this article valuable. When a new system…

Software Engineering

design, distributed, distributed systems, model, safety, system, system design
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
August 6, 2018

Acceptance Tests: The Best Medium of Communication Between Stakeholders (if done right)

It’s a nice pleasant morning, and you have just entered the office. You greet your friends and grab a cup of coffee. You check your email and there is a new story assigned to you. “As a customer, I get my usage logs backed up” This is where is fun begins. Communicating Requirements A…

Software Engineering

(or, 1., 12, 15., 7., A, able, about, above, acceptance, access, accordance, add, adopt, after, agile, aiming, all, also, always, ambiguity., an, and, Another, any, appear, Application, are, argument, around, as, ask, assigned, associated, assume, at, automated, AWS, back., backed, backup, be, before, begins., best, between, biggest, Both, brings, built, business, business_name_date_backup.log, But, by, call, can, Can’t, cannot, case, change, check, clear, clearer, code, coding, coffee, Collaboration, collaboratively., common, communicate, Communicating, communication, Conclusion, confirmation, consider, conversation, cool!), cost-effective, could’ve, course, create, created, creating, cup, customer, customers, daily, day., days, decide, define, defining, definition, deliver, details, detected, didn’t, different, disagree, disaster., do, doc., document, documented., doesn’t, Don’t, done, drive, drives, each, easy, effective, effectively, effort, eliminate, email, End, ended, engineer, engineers, English, enormous, entered, errors, etc., even, exactly, fairly, fall, feature, few, file, files., find, finite, focus, folks!, follow, for, forth, framework, friends, from, fun, funny., GB, get, Glacier., Go, going, good, got, grab, great, greet, had, hands, happen, hard, has, have, having, help, helps, Hey, Hi!, high-level, Hmm., how, I, I’ll, I’ve, idea., if, Implementation, implemented., important, in, inclination, innocent, inorder, insist., into, is, issues, It’ll, It’s, it., job, just, know, language, last, late, later?, lead, leads, least, leaves, Let’s, like, log, logs, long, look, looking, lose, lost, Make, malady:, manager., managers, manifesto, many, me, mean, meaning., meant, mid-night, midnight, mocking, more, morning, Morty, most, move, much, my, name, named, need, needs., new, nice, night’s, No, Not, now, number, objectively, of, off., office, often.”, Ok., Okay., older, on, Once, one, only, other, our, out, overloaded, paper, party, pass., past, per, perfect, persist, pleasant, point, precise, precision, Premature, problem, product, properly., put, QAs, question, rarely, ready, real, recipe, release?, removed., request, requirement, Requirements, Rick, Robot, room, rule, Running, scale., see, seeing., Seems, seen, should, Simplest, since, single, skills, So, Solution, sounds, stakeholders., standard, statement., states, storage, story, suggest?, suite, suits, support., sure, survive, sync, system, systems., team, teams, tempted, tend, term, test, tested, tests, tests(or, than, that, that’s, the, their, them., then, there, they, things, think, thinking, this, Though, threats, through, thumb, time., timezone?, to, tone, too., tools, touch, towards, trap, true, two, unambiguous, understands., until, up, usage?, used, user, users, UTC., vague, validations, very, want, wants, was, wastage, wave, way, we, well, what, what’s, when, where, which, will, with, wordsmith, work, working, works., worse, worst, worth, would, write, written, yes, you, Your
April 29, 2018

Devops and The Principle Of Flow

In the technology value stream, work typically flows from Development to Operations, steps consisting of functional areas between our business and our customers. As stated in the lean principles developed by Toyota, we should optimize to get a single-piece fast and smooth flow for our releases. We increase flow by: Making work visible, Reducing batch…

Uncategorized

(or, (WIP), 10, 310, 4., 40, A, above, acceptance, According, achieving, activities, added, affecting, after, agile, all, allow, already, amount, an, and, Another, any, anything, Application, are, areas, as, at, batch, batches., be, become, before, being, better, between, beyond, bigger, board, bouncing, brochures, bugs., Building, business, But, by, by urgent, bypassed, can, cards, case, categories, causes, centers., changes:, channel, codifying, column, coming, common, communication, complete, completed only, completes, component, Conclusion, consisting, control, creating, customer, customers, daily, decrease, defects, defining, delay, demands, deploy, deserves, developed, development, DevOps, difference, do, doesn’t, dominated, done, downstream, dramatically, dynamic, each, easy, eliminating, encounter, enforcing, ensures, entire, envelope, envelopes., essential, every, example, Explaining, external, Extra, far, fast, fast-flow, features, find, first, flow, flows, fold, folded, folks!, following, for, from, fulfill, functional, furthur, get, gets, given, goal, hardships, have, help, how, However, I, Ideally, if, implementing, Improving, in, increase, increasing, insert, internal, intervals, into, invisible., is, It’s, it., just, kanban, Kanban board., keep, key, Knaban, large, lead, lean, Let’s, levels., like, Limit, limiting, limits, mail, mailing, Make, Making, manual, manufacture, manufacturing, material, may, more, multi-tasking, multiple, needed?, new, next, No, Non-standard, Not, now, of, off., on, one, one-piece, only, Operations, optimize, other, our, our work, out, outcomes., over, own, paper, Partially, passed, pay, perform, performing, piece, piled, pioneer, point, possible., post, Practice, Prefer, prevent, preventing, principles, Prior, processes., processing, production, Progress, QA, quality, reaches, reduce, Reducing, releases., reliability., requests, required, requires, resource, result, revolution, right, Running, same, satisfy, seal, sealed., seconds., sequentially, services, set, Shiego, Shingo, should, side, significant, single, single-piece, size, sizes, skyrocketing, small, smooth, So, software, some, something, soon., span, speeding, stakeholders., stamp, starting, stated, step, steps, stream, streams, successfully, such, suppose, switching, system, take, takes, task, teams, technology, ten, testing., than, that, that’s, the, the ideal, them., there, this, those, three, through, time., times, to, toyota, traditional, Trello, trouble?, typically, up, us, use, using, value, visible, visual, waiting, was, waste:, wastes, way, we, well, what, when, where, which, while, why, will, willing, with, without, words, work, worst, Yet
March 11, 2018

8 System Design Principles I learned After Doing It Wrong More than 50 Times!

At Squad, we strive to build awesome products to solve customer(internal and external) needs. As a product engineer, paramount part of your job is to design and build products. Dig deep into the root cause of the problems, design solutions and implement them as the end product. Over the course of my journey so…

Uncategorized

8, coding, deisgn pattern, design, engineer, engineering, google, how, iterate, lean, pattern, principles, product, programming, ship, software, software engineing, system, technology
August 5, 2017

Clean Code Chapter 1&2: Clean Code & Meaningful names

I have started reading the book Clean Code by Robert C. Martin, which is considered to be a industry standard for writing maintainable and elegant code. Because this book is such a heavy read, and each chapter is full of content and a knowledge bank in itself, for personal reference I’ve decided to summarise each chapter in…

Uncategorized

c, clean, code, coding, design, engineering, gist, java, martin, meaningful, names, pattern, programming, robert, short, software, summary, system

Tag: system