renzok

function _check_required_programs() {

    # Required program(s)
    req_progs=(readlink xmllint xsltproc curl date sed)
    for p in ${req_progs[@]}; do
	hash "${p}" 2>&- || \
	    { echo >&2 " Required program \"${p}\" not installed or in search PATH."; 
              exit 1; 
            }

renzok

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

renzok

Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.

Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma

renzok

begin;

UPDATE osdregistry.samples
   SET nitrate='nan', 
       nitrite='nan',
       ammonium='nan',
       phosphate='nan',
       silicate='nan'
 WHERE submission_id = 215 and osd_id = 117 

renzok

CREATE MATERIALIZED VIEW osdregistry.sample_boundaries_tagging AS 
 WITH boundary AS (
      SELECT DISTINCT ON (osd.submission_id)
	     osd.submission_id, 
             osd.osd_id,
	     b.gid,
             b.iso3_code,
             st_distance(osd.start_geog, b.geog) as dist_m
        FROM elayers.boundary_polygons b
        JOIN osdregistry.samples osd 

renzok

COPY tara_samples (sample_name, ena_read_no, pangaea_id, publication, type_of_study, seq_method, date_verb, latitude_verb, longitude_verb, depth_verb, feature_verb) FROM STDIN WITH (FORMAT csv, HEADER, DELIMITER E'\t', NULL  '', FORCE_NOT_NULL(type_of_study,seq_method) );
sample_name	ena_read_no	pangaea_id	publication	type_of_study	seq_method	date_verb	latitude_verb	longitude_verb	depth_verb	feature_verb
TARA_004_DCM_0.22-1.6	ERR598950|ERR599095	TARA_X000000368	sunagawa

renzok

BEGIN;

SELECT _v.register_patch('00138-add-boundaries-polygon-table-elayers',
                          array['00137-osdregistry_new_sample_env_view'] );

-- section of creation best as user role megdb_admin
SET ROLE megdb_admin;

create table elayers.boundary_polygons (

renzok

FROM debian:jessie

ENV USER=boatswain USER_ID=1000 USER_GID=1000

# now creating user
RUN groupadd --gid "${USER_GID}" "${USER}" && \
    useradd \
      --uid ${USER_ID} \
      --gid ${USER_GID} \
      --create-home \

renzok

awk 'BEGIN{RS=">"}NR>1{sub("\n","\t"); gsub("\n",""); print $0}'

renzok

with pizzas AS(

select p.pizzaid, p.name, p.calzone, 
       i.imageid, i.url, i.copyrightshort, i.copyrightlong,
       amount, diameter, curcurrency, array_agg(trim(t.name)) as toppings, string_agg(t.name, ',')
  from pizza p 
  LEFT JOIN image i On (p.imageid = i.imageid)
  LEFT JOIN pizzasizeprice psp on (p.pizzaid = psp.pizzaid)
  LEFT JOIN price on (psp.priceid = price.priceid)
  LEFT JOIN size ON (psp.sizeid = size.sizeid)