errors   5432

« earlier    

Q&A on the Book Evidence-Based Management
The most important issue in organizational data quality is whether you have the data you need to test whether your beliefs about the organization are really true. So if I believe my organization has a reliable backoffice in terms of transactions, do I have the data that show how many errors are made a day or a month for a given volume of transactions.? Counts tell us almost nothing; we need rates, like errors/daily volume. If I am relying on my impressions, I am talking to myself.
Management  data  rca  errors  monitoring  books  interviews  links  via:Workflow 
2 days ago by cote
ztrue/tracerr: Golang errors with stack trace and source fragments.
Golang errors with stack trace and source fragments. - ztrue/tracerr
type:library  lang:go  errors  stacktrace 
5 days ago by endorama
The 9 Most Common Database Design Errors
Reading this article might save you many hours spent fixing design and code problems, so let’s dive in. I’ve split the list of errors into two main groups: those that are non-technical in nature and those that are strictly technical. Both these groups are an important part of database design.
databases  design  tips  consells  errors  articles  vertabelo  Emil  Drkušić 
10 days ago by jaumeb
Angular applications —error handling and elegant recovery
When we started to design our enterprise client, we asked our UX designer to give us some design tips on how to handle errors from the back-end server in the application. Should it be a pop up, a…
angular  errors  developer  programming 
12 days ago by ciaranmccormick
Provide API to pass TLS / Certificate issues to C# code · Issue #16480 · grpc/grpc
What version of gRPC and what language are you using? gRPC version 1.14.1 C# on .NET 4.7.1 on Windows, C# on Mono on CentOS 7 What operating system (Linux, Windows, …) and version? Windows & Linux (CentOS) What runtime / compi...
C#  grpc  errors 
13 days ago by clehene
Uses STAMP (System-Theoretic Accident Model & Processes) by Nancy Leveson to analyze a particular malicious attack in the NPM ecosystem. Goes step-by-step in tracing down the errors.

“Who did this” is the wrong question. “How did this happen” is the wrong question. A better question is “why was this possible in the first place?”

An accident isn’t something that just happens. Accidents aren’t isolated failures. Accidents aren’t human error. Accidents aren’t simple. Accidents are complicated. Accidents are symptomatic of much deeper, more insidious problems across the entire system.

Systems thinking

errors  retrospective  npm  stamp  analysis  systems  systemsthinking 
15 days ago by drmeme

« earlier    

related tags

!basic  !in-depth  $tutorials  &abstractions  'basic  -  -36  2018  2019  404  65  accessibility  acknowledge  algorithm  amend  ammend  analysis  analytics  analyze  and  angular  anti-semitism  api-errors  api  apps  architecture>software  are  articles  as  authors  automatically  bash  bestpractices  bitbucket  black  blank  book  bookmarklet  books  boot  bowertom  branch  browser  bugs  bundler  bungles  c#  catch  celgene  certificate  changes  chef  chrome  clojure  code  codesniffer  codex  coding  cognition  comics  command-line  command  commands  commit  commits  committed  compare  computing  connection  consells  consolation  containers  contentsecuritypolicy  control_flow  corbynjeremy  correction  crash-reporting  csp  css  data  databases  dc:creatot=obornepeter  dctagged  defeat  defending'  delete  design  developer  development  diff  disk  docker  documentation  drkušić  drugdevelopment  due  ebooks  economics  either  emil  encoding  errata  error-handling  error  error_correction  error_handling  errorcorrection  example  exception  exceptions  explorer  facing  failure  fast  favorites  fda  firefox  fix  foundation  frontend  fun  ga  gaffes  generics  georgia  gerrard  git  github  gitlab  go  golang  good.intentions  google  grief  grpc  guide  halts  handling  haskell  hathitrust  head  help  heritage  heroku  high-sierra  history  how  howto  html  http  https  idaes  ifttt  in  incorrect  insecure  inspiration  installation  installer  interviews  ios  islam  java  javascript  jeffatwood  judgement  key  kinesis  labourparty  lambda  lang:go  layout  learning  lens  lines  links  log  logging  long  loss  mac  macos  macports  management  manual  map  math  maybe  mdn  message  midori  mistake  mistakes  modify  monitoring  moscow  mozilla  nataliewolchover  network  node.js  nov  npm  oceans  ocr  of  or  osx  palestine  panic  patch  pg_hba  php  phpcbf  phpcs  physics  pitfalls  player  politics  polls  post  postgres  problems  programming  promises  publishing  quality  quantumphysics  rails  rangers'  rca  read  reference  report-uri  report  reporting  reset  resilience  retrospective  rollout  ruby  rues  rust  scientists  screen  security  self-publishing  sentry  set_e  setup  show  sin  slate  sniffer  snippet  software  source  space  spacetime  spartak  ssl  stacktrace  stacktraces  staged  stamp  start  statistical  statistics  steven  story  study  style  swift  sysadmin  systems  systemsthinking  technical  termcap  terminal  the  they  throw  time  tips  to  tolearn  tolerance  tool  tools  toread  totry  tounderstand  troubleshoot  troubleshooting  tutorial  type:article  type:library  typing  typos  uk  uncommitted  undo  ux  versioncontrol  vertabelo  video  voters  warming  washington  web-development  web  webdev  weird  whea  windows  winobj  wordpress  writing  wrong  xcode  xkcd  xpath  youtube 

Copy this bookmark: