leostratus

An ongoing project to catalogue all of these sneaky, hidden, bleeding edge selectors as I prepare my JSConf EU 2012 talk.

Everything is broken up by tag, but within each the selectors aren't particularly ordered.

I have not tested/verified all of these. Have I missed some or got it wrong? Let me know. - A

A friendly reminder that you may need to set this property on your target/selected element to get the styling results you want:

-webkit-appearance:none;

davidleandro

heroku pg:backups capture --app APPNAME
curl -o latest.dump `heroku pg:backups public-url --app APPNAME`
pg_restore --verbose --clean --no-acl --no-owner -h localhost -d DATABASE latest.dump

popravich

The standard names for indexes in PostgreSQL are:

{tablename}_{columnname(s)}_{suffix}

where the suffix is one of the following:

• pkey for a Primary Key constraint;
• key for a Unique constraint;
• excl for an Exclusion constraint;
• idx for any other kind of index;

MWins

http://web.mit.edu/ssit/cis/CISRequirements.html

Super long requirements document which is just not feasible for small scale projects with a single developer or even a small team. It would take more time to gather the information for this document than to complete some projects.

https://www.atlassian.com/agile/requirements

Shorter example from Confluence (bitbucket/atlassian) - Don't have real problems with the structure of the requirements but I know from working with their software, it isn't very easy to work with to produce useful documentation. Which makes me leary of using them as a reference.

https://en.wikipedia.org/wiki/Product_requirements_document

MWins

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

jagin

import cv2
import os
import json
import numpy as np

def parse_args():
    import argparse

    # Parse command line arguments
    ap = argparse.ArgumentParser(description="Image processing pipeline")

IslamWahid

TypeORM tricks

Finding entity with with relation condition

There's a workaround for filtering based on relation fields for findOne()/find() methods that I've discovered recently. The problem with filtering related table fields only exists for ObjectLiteral-style where, while string conditions work perfectly.

Assume that we have two entities – User and Role, user belongs to one role, role has many users:

@Entity()

songthamtung

#!/bin/bash
FILENAME=guid.csv
HDR=$(head -1 $FILENAME)
split -l 1000 $FILENAME xyz
n=1
for f in xyz*
do
     if [ $n -gt 1 ]; then 
          echo $HDR > Part${n}-$FILENAME
     fi