Skip to main content

Search This Blog

unicolet.org

Delivering the improbable.

Quoting Deming: A bad system ...

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

August 28, 2024

A bad system will beat a good person every time.

W. Edwards Deming at a February 1993 seminar.

deming management organizations people performance systems

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Powered by Blogger

Report Abuse

Archive

2024 40

2022 1
- February 1
2021 5
2019 1
- August 1
2018 3
2017 4
2016 8
- December 1
- May 2
- March 1
- February 2
- January 2
2015 11
- December 1
- November 1
- October 1
- August 1
- April 4
- March 1
- February 1
- January 1
2014 5
- October 1
- September 1
- August 1
- June 1
- February 1
2013 10
- December 1
- October 1
- August 1
- July 2
- May 1
- March 1
- February 2
- January 1
2012 35
- December 2
- November 2
- October 1
- September 2
- August 4
- July 2
- June 5
- April 4
- March 3
- February 3
- January 7
2011 18
- December 1
- November 4
- October 2
- September 1
- August 3
- June 3
- May 1
- April 1
- February 2
2007 14
- December 2
- May 1
- March 1
- January 10
2005 19
- June 2
- May 3
- April 1
- March 3
- February 5
- January 5
2004 4
- December 4

Show more Show less

Labels

linux22 sproutcore21 sysadmin20 javascript17 computer14 development13 linux tipstricks13 opennms12 leadership11 postgres11

salt10 system administration10 devops9 grails9 openlayers9 web9 management8 monitoring8 windows7 configuration6 database6 java6 programming6 saltstack6 centos5 configuration manager5 performance5 zfs5 ai4 apache4 backups4 cloud4 elasticsearch4 firefox4 html54 logstash4 oracle4 sql4 vmware4 architecture3 cybersquatting3 deployment3 effective3 embedded3 event log3 gis3 j2ee3 kvo3 learning3 provisioning3 recovery3 refactoring3 security3 software3 team3 test3 testing3 tuning3 ubuntu3 unicolet.org3 agency2 android2 aws2 backup2 book2 c2 cache2 camel2 cloud92 cluster2 collectd2 css32 effectiveness2 ehcache2 email2 engineering2 enterprise2 esxi2 failure2 farnam2 fear2 git2 graph2 ide2 index2 infrastructure2 integration2 jdbc2 kibana2 knowledge2 logging2 mapnik2 mapserver2 mastery2 microsoft2 mirth2 mixin2 motivation2 mvc2 nagios2 nginx2 otrs2 parallel2 plugin2 podcast2 postgis2 puppet2 python2 review2 ruby2 script2 scripts2 servers2 shell2 snmp2 storage2 success2 sun-tzu2 svn2 tech debt2 template2 tile2 tiledrawer2 tomcat2 tools2 unity2 vagrant2 vbs2 virtualization2 20121 2351 3331 3d1 4k1 71 IE1 Microsoft-Windows-PrintService/Operational1 Tom Gayner1 abbot1 access1 actiforce1 activemq1 agile1 ajax1 amazon1 amd1 amqp1 animations1 antithesis principle1 apple1 appsmith1 archive1 archunit1 ati1 audit1 awk1 backdoor1 beatles1 beck1 bias1 binary1 birt1 blob1 bloom1 body1 boldrin1 bootstrap1 breach1 brendan gregg1 browser1 bsod1 btrfs1 budget1 bytea_output1 c++1 c91 cantrill1 cas1 case1 cfce1 changes1 chatops1 chrome1 closable1 cm1 coaching1 code1 code reviews1 codemotion milan 2016 conference1 codescene1 coding1 commands1 commitment1 commuting1 complexity1 computing1 context1 continuous integration1 conway1 covey1 crowdstrike1 crypto1 csv1 cube1 culture1 cygwin1 ddd1 decision1 delegation1 deming1 derby1 design1 desktop1 devlake1 devopsdays1 disk1 dmbs_job1 dns1 dom1 dora1 doshi1 drools1 drucker1 dynamic1 ebpf1 eclipse1 economia1 edit1 ego1 elb1 elixir1 elk1 engineer1 engineering manager1 erlang1 error correction1 eventid 3331 eventlog1 exceptional1 executive1 express1 fare1 farnam street1 feedly1 figma1 filter1 firegl_sig_notifier1 flow1 forerunner1 formatting1 formula1 freund1 fun1 funny1 futuresmart1 gaming1 garmin1 getcapabilities1 gio1 giveaway1 gnome1 google docs1 google web fonts1 grailsui1 graphite1 groovy1 gruver1 guava1 guest agent1 helpdesk1 history1 homebrew1 host1 howto1 hp1 html1 httm1 http1 ij1 imposter1 impress.js1 industry1 influence1 input stream1 install1 instant1 internet1 irc1 italia1 javax.management.InstanceAlreadyExistsException1 jms1 journal1 jquery1 jts1 junit1 kata1 kent1 kids1 knowledge project1 kvm1 laserjet1 laura tacho1 leaderarship1 libvirt1 links1 liquibase1 lnk1 log1 login1 logon script1 lopp1 lotus1 lvm1 mac1 manager1 managing up1 mapping1 mappu1 mario1 mario kart1 marquet1 mba1 mcu1 mdb1 migration1 minion1 mirth connect1 money1 motto1 movies1 music1 negotiation1 nerves1 net-snmp1 nfs1 ninja1 nintendo641 node1 node.js1 nodejs1 notes1 nsis1 ntp1 online1 open source1 openemu1 openshift1 openstreetmap1 openstreetmap osm1 operational1 opslane1 organizations1 osgi1 osm1 otis redding1 oxide1 packt1 parenting1 patch1 people1 photo1 pingdom1 post1 power1 print1 printservice1 privacy1 problem1 procrastination1 productivity1 project1 proxy1 prune1 psychological safety1 psychology1 qa1 qemu1 qnap1 quota1 quote1 rackspace1 radar1 radeon1 raffle1 rands1 reader1 reading1 readwise1 reclaim1 recognize power1 reddit1 renovatebot1 repeat1 report1 reporting1 restic1 restore1 retention1 retro gaming1 revert1 right1 roadmap1 rome1 rrd1 rspec1 rss1 rsync1 rules1 rundeck1 runloop1 running1 rust1 samsung1 sc.outlet1 schwaber1 scrum1 selenium1 senior1 server1 service1 servlet1 shane parrish1 shapefiles1 shared_buffers1 show me1 sit1 skill1 sles1 smartwatch1 snapshot1 sociology1 solution1 space1 speed1 spreadsheet1 spring security1 sqlite1 stand1 standing desk1 standups1 states1 stm1 stm321 strategy1 stream1 strong language1 style1 subversion1 sun1 suse1 sw1 swift1 syncthing1 syndrome1 syslog1 systemctl1 systemd1 systems1 taglib1 tail1 talent1 taxonomy1 tcp1 tdd1 tea1 technology1 thoughtworks1 ticket1 time machine1 toyota1 toyota kata1 training1 turn the ship around1 twitch1 tzu1 uei1 uek1 unblocked1 unix1 vacuum1 valiante1 value1 vcb1 vcenter1 verizon1 version control1 virt-install1 virtualbox1 visual1 vm1 voip1 vsphere1 wardley1 warm1 wdsl1 wevutil1 wifiweb1 wms1 work1 x111 xfs1 xp1 xy problem1 xz1 yui1 zope1

Show more Show less

RSS feed

Posts

Posts

Comments

Comments

Popular posts

Mirth: recover space when mirthdb grows out of control

August 23, 2012

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in

JTS processing Grails servlet

January 05, 2012

Sometimes it is convenient to make certain topological operations available in a web-based gis. For a gis that makes heavy use of Javascript (like OpenLayers-based ones) it might be worth looking at jSTS , a Javascript port of JTS. For all the rest and for those who don't want to load yet another library in the browser you can always write a Grails controller that encapsulates common JTS operations like buffer, intersection, union, etc. Assuming you are familiar with Grails the steps are as follows: drop the jts jar in the lib directory create a controller and define the relevant methods define a url mapping to prettify the calls Step 1 is trivial, so we'll go straight to 2. Create a controller and call it JtsController , then open the source file and paste this code: import com.vividsolutions.jts.geom.* import com.vividsolutions.jts.io.* import com.vividsolutions.jts.operation.overlay.snap.* import grails.converters.JSON import grails.plugins.springsecuri

Quoting Will Larson: extract the kernel

September 09, 2024

One of my most unexpectedly controversial posts is Extract the Kernel , which argues that executives are generally directionally correct but specifically wrong, and it’s your job to understand the overarching direction without getting distracted by the narrow errors in their idea. from executive translation : it reminds me of Shreyas Doshi antithesis principle : everyone can be effective with a good boss, but it's more interesting (and relevant as a hireable skills) to be effective even with a "bad" boss. This KP episode explains it in much more details . It's an alternate take on the old adage: “In calm waters, everyone looks like a good sailor, but in stormy waters, you want to be the one with the experienced captain.” The experienced captain is our ability to handle these situations in imperfect conditions.