git init
or
Installing ubuntu snappy core on raspberry pi 2
Translated to os x from https://developer.ubuntu.com/en/snappy/start/#snappy-raspi2
Download the image
http://people.canonical.com/~platform/snappy/raspberrypi2/
Locate your sd card
| #!/usr/bin/env python3 | |
| import os | |
| import sys | |
| import datetime | |
| import pyotp | |
| import hashlib | |
| ### TO ALLOW ACCSSS CALL sys.exit(0) | |
| ### TO DENY ACCESS CALL sys.exit(1) |
| #!/usr/bin/env bash | |
| set -e | |
| if [ -e static ]; then | |
| rm -r static | |
| fi | |
| mkdir -p static | |
| sass src/sass/main.scss > static/application.css | |
| $(npm bin)/browserify src/js/main.js > static/application.js |
I was talking to a coworker recently about general techniques that almost always form the core of any effort to write very fast, down-to-the-metal hot path code on the JVM, and they pointed out that there really isn't a particularly good place to go for this information. It occurred to me that, really, I had more or less picked up all of it by word of mouth and experience, and there just aren't any good reference sources on the topic. So… here's my word of mouth.
This is by no means a comprehensive gist. It's also important to understand that the techniques that I outline in here are not 100% absolute either. Performance on the JVM is an incredibly complicated subject, and while there are rules that almost always hold true, the "almost" remains very salient. Also, for many or even most applications, there will be other techniques that I'm not mentioning which will have a greater impact. JMH, Java Flight Recorder, and a good profiler are your very best friend! Mea
This week NN Group released a video by Jakob Nielsen in which he attempts to help designers deal with the problem of customers being resistant to their new site/product redesign. The argument goes thusly:
There's slightly more to it than that, he caveats his argument with requiring you to have of course followed their best practices on product design, and allows for a period of customers being able to elect to continue to use the old site, although he says this is obviously only a temporary solution as you don't want to support both.
| #!/usr/bin/env -S bash -c "docker run -p 8080:8080 -it --rm \$(docker build --progress plain -f \$0 . 2>&1 | tee /dev/stderr | grep -oP 'sha256:[0-9a-f]*')" | |
| # syntax = docker/dockerfile:1.4.0 | |
| FROM node:20 | |
| WORKDIR /root | |
| RUN npm install sqlite3 |