Lenovo messed up with the X1E and P1 Gen 1 versions (and maybe later generations) in that the system boots with a thermal limit (aka Tjunction or tjmax) set to 82C (some report 80C). What this means is that regardless of power draw or under-volting settings, when your CPU hits 82C, it will drop the frequency down to the "Configurable TDP-down" frequency, or even lower. It will also may limits the system power draw.
| #!/usr/bin/env bash | |
| # | |
| # Plex's profile for Chromecast is too conservative and only plays 1080p on | |
| # the Chromecast Ultra UHD device (4k). | |
| # | |
| # This script will download an updated Chromecast definition and start a Plex | |
| # docker container, binding a few local paths of where you run this script. | |
| # | |
| # You may want to refer to the Official Plex Docker repository and read the | |
| # README text: https://github.com/plexinc/pms-docker |
| #!/bin/bash -e | |
| # A script to mass install Gnome extensions from a single folder. | |
| # | |
| # for global extensions, use /usr/share/gnome-shell/extensions/ | |
| EXTENSIONS_DIR=~/.local/share/gnome-shell/extensions | |
| TMP_DIR="/tmp/gnome-install-extensions" | |
| DIR=$1 |
I hereby claim:
To claim this, I am signing this object:
It was not exactly obvious. Here's how to revert a Gist commit!
Checkout the gist like a normal git repo:
# replace the Gist ID with your own
git clone git@github.com:cc13e0fcf2c348cc126f918e4a3917eb.git
Treat it like a normal repo. Edit, force push, etc.
| package main | |
| import "fmt" | |
| /* | |
| Here's a use of labels in Go to continue a for loop | |
| from within another for and within a switch case. | |
| */ | |
| func main() { |
| #!/bin/bash | |
| # | |
| # GoLang cross-compile snippet for Go 1.6+ based loosely on Dave Chaney's cross-compile script: | |
| # http://dave.cheney.net/2012/09/08/an-introduction-to-cross-compilation-with-go | |
| # | |
| # To use: | |
| # | |
| # $ cd ~/path-to/my-awesome-project | |
| # $ go-build-all | |
| # |
| /*Package main is a simple test of Json Identing (aka pretty print) | |
| To run: | |
| $ go run main.go | |
| { | |
| "eventId": "xyz", | |
| "articleId": "123" | |
| } |
| #!/bin/bash | |
| # bash script to create a GoLang README.md in the current and all sub-directories. | |
| # | |
| # installation: | |
| # place this in your ~/bin or similar. make sure to: chmod 755 godoc2md-all | |
| # | |
| # it is recommended to have a doc.go for each package, that allows for samples and | |
| # additional instructions. | |
| # |
This is my response to an email asking about Domain-Driven Design in golang project.
Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.
That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.
Conclusions could be very different, if there was a different project, team or a story-teller.