# things Published articles for things. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using Docker Containers to Run Development Tools Without Local Installation DevFeed: [Using Docker Containers to Run Development Tools Without Local Installation]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-11-02T15:42:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Containers](), [Docker Image](), [Docker Hub](), [Command-line interface](), [Shell]() Tags: [command-line](), [computer](), [containerization](), [devops](), [docker](), [docker-hub](), [embracing](), [flexible](), [gives](), [messy](), [robust](), [setup](), [things](), [tools](), [transportable]() ### AI overview This tutorial explains how to use Docker containers to run development tools without installing them directly on a computer. It describes the benefits of disposable, version-specific, self-contained images and introduces Docker Hub and shell aliases. ### Source excerpt Embracing Docker for All The Things gives you a more flexible, robust, and transportable way to use tools on your computer without messy setup ## A HashiConf art collab DevFeed: [A HashiConf art collab]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2021-10-15T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [color](), [Requirements](), [iteration]() Tags: [art](), [conference](), [custom](), [design](), [generative](), [hashicorp](), [iteration](), [printer](), [printing](), [requirements](), [things]() ### AI overview The article describes creating custom generative-art prints for HashiConf Europe speakers. Each print combines the speaker's name, talk title, and the relevant HashiCorp product color in a randomly generated geometric grid, following conference design guidelines. ### Source excerpt A couple of months ago my friend Jana helped organize HashiConf Europe, and asked me to work on generating custom artwork for each of their speakers. This was my first experience with creating art for someone else, and especially art that had to match someone else's artistic guidelines. I've said this before, but I live and nap by the idea that rules (and editing) are at the core of the artistic process and not having to do that myself was brilliant. I wanted to write a bit about it because a) I did a bunch of work that I'm really proud of and I never got to talk about it and b) I am vain and I want to talk about it. This was the final poster: And this is what we wrote about it on the card that accompanied it: Enclosed you will find an art print made for you by generative artist and engineer Monica Dinculescu. This individual print is unique to you and you alone, as Monica has incorporated your name, the title of your talk, and the color of the HashiCorp product that you are talking about at this year's conference. Each cell in the grid has been randomly generated to contain either a letter from your name, or a pattern in the product color. Cells located towards the middle of the grid are more likely to contain a letter rather than a pattern, and this likelihood decreases in the cells towards the edges. This print is the only iteration of its kind. Were it to be generated again, it would look slightly different each time. I print everything in my art store myself, because I sell very limited editions and third-party printing companies only make sense financially when you're printing in the several dozen. This does mean that sometimes I'll fight with my printer thinking that its colour profile is whack, only to discover that it was Doing Just Fine™ and my MacBook oversaturates things like it's an Instagram filter in 2011. Every day is a school day. Here are all the prints drying on their totes profesh drying rack that is definitely not just a string I hung around in ## Threat Modeling Building Blocks DevFeed: [Threat Modeling Building Blocks]() Original publisher: [Read original article]() Author: Adam Published: 2019-09-04T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [data](), [Requirements]() Tags: [building](), [comparison](), [data-protection](), [models](), [requirements](), [results](), [reuse](), [tasks](), [techniques](), [things]() ### AI overview The article presents threat modeling as a collection of interconnected tasks and discusses research on breaking threat modeling into smaller, assessable building blocks. It highlights comparisons involving privacy and data protection, requirements, STRIDE, CAPEC, CWE, OWASP, data-flow-diagram variants, and CARiSMA extended. ### Source excerpt Threat modeling isn't one task -- its a collection of tasks that build on each other to produce more valuable insights. ## The CSS background-image property as an anti-pattern DevFeed: [The CSS background-image property as an anti-pattern]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-05-28T12:49:00Z Content type: opinion Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [CSS](), [Accessibility](), [Search engine optimization (SEO)](), [Web Development]() Tags: [accessibility](), [allowed](), [alt-text](), [amazing](), [background-image](), [browsers](), [cases](), [css](), [image](), [insights](), [it-s](), [leave](), [property](), [seo](), [things](), [time]() ### AI overview The article argues that CSS background-image is often misused for CTA hero and UI images. It discusses SEO, accessibility, and performance drawbacks and points toward using more appropriate browser image techniques instead. ### Source excerpt The CSS background-image property allowed us to do some amazing things, but in most cases, it's time to leave it behind. ## Professionalism in Software Products Comes from Attention to Detail DevFeed: [Professionalism in Software Products Comes from Attention to Detail]() Original publisher: [Read original article]() Published: 2018-05-22T18:53:45Z Content type: opinion Language: ru Sources: [Blog by Michael Dubakov]() Topics: [jira]() Tags: [jira](), [tag-38e01848bd76](), [things]() ### AI overview The essay argues that professional quality is revealed through attention to detail. It compares Things and Jira, discusses thoughtful product interactions and text, and connects care in product design with clean code and polished writing. ### Source excerpt Меня давно волнует вопрос, как определить истинный профессионализм? Пока лучшее, что я смог придумать -- детали. Довольно часто хорошее... ## ServiceWorkers and Offline Browsing DevFeed: [ServiceWorkers and Offline Browsing]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-01-15T02:09:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Web](), [web browsers](), [Caching]() Tags: [browsing](), [cache](), [devices](), [insights](), [instant](), [loading](), [offline](), [provide](), [server](), [serviceworkers](), [sync](), [things](), [web](), [web-browsers]() ### AI overview The article explains how ServiceWorkers can support offline browsing, instant loading, local caching of visited and anticipated resources, offline form completion, and later synchronization with a server. ### Source excerpt ServiceWorkers provide a way to provide offline browsing and instant loading (amongst other things). ## Hostage Negotiation 101 DevFeed: [Hostage Negotiation 101]() Original publisher: [Read original article]() Author: Graham King Published: 2011-09-18T20:24:18Z Content type: opinion Language: en Sources: [Graham King]() Topics: [trust](), [saving]() Tags: [behaviour](), [book](), [friendly](), [negotiation](), [society](), [strategy](), [things](), [time](), [trust]() ### AI overview A summary of Gary Noesner's memoir about hostage negotiation, covering peaceful surrender, exclusive communication, environmental control, calm listening, organizing demands, and building trust. ### Source excerpt Negotiating lives: Insights from an FBI hostage negotiator's memoir. ## Environment Structure for Django Apps DevFeed: [Environment Structure for Django Apps]() Original publisher: [Read original article]() Author: Map Published: 2011-05-17T03:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [Django](), [Development](), [Python](), [PostgreSQL](), [Git](), [osx](), [Ubuntu]() Tags: [development](), [development-environment](), [django](), [git](), [osx](), [postgresql](), [python](), [setup](), [things](), [ubuntu]() ### AI overview A cookbook for structuring Django project environments on OSX and Ubuntu. It explains how to create a Python virtual environment, install Django and PostgreSQL dependencies, use requirements.txt and .gitignore, and prepare a repository for contributors. ### Source excerpt I've been writing applications off and on for nearly 4 years now, since before Django 1.0 was even released. I must say the framework could not be better described than by its own tagline "The Web framework for perfectionists with deadlines". Among the things I love about it are: However, after using the framework for nearly 4 years I'm just now discovering my preferred way of managing environments. I know there's still a bit of back and forth on development environment/IDE, but as far as configuring actual project environment I've become very comfortable with what I've now been using for many months. It also allows for someone else bootstrapping their environment incredible quickly as well. Below is a quick cookbook of how to do this on OSX and Ubuntu. $ sudo port install python27 $ sudo port install py27-virtualenv $ sudo port install postgresql90 Now for setting up your project: $ mkdir example $ cd example $ virtualenv-2.7 --no-site-packages . $ source bin/activate $ sudo brew install python $ sudo brew install virtualenv $ sudo brew install postgresql Now for setting up your project: $ mkdir example $ cd example $ virtualenv --no-site-packages . $ source bin/activate $ sudo aptitude install python sudo aptitude install virtualenv sudo aptitude install postgresql Now for setting up your project: $ mkdir example $ cd example $ virtualenv --no-site-packages . $ source bin/activate For those of you not familiar virtualenv is a self-contained python environment. It holds its own copy of python and any libraries you install. Now that you've setup your virtualenv we can go through the process of installing django and setting up your repository. This is the same across all of the above platforms: Add to a .gitignore file: bin build include lib .Python *.pyc Add to a requirements.txt file: Django==1.3.1 psycopg2==2.4.1 Then run: $ bin/pip install -r requirements.txt This should fully installed any of your required apps and makes it easy for others to do the same to begi