|Latency Comparison Numbers (~2012)|
|L1 cache reference 0.5 ns|
|Branch mispredict 5 ns|
|L2 cache reference 7 ns 14x L1 cache|
|Mutex lock/unlock 25 ns|
|Main memory reference 100 ns 20x L2 cache, 200x L1 cache|
|Compress 1K bytes with Zippy 3,000 ns 3 us|
|Send 1K bytes over 1 Gbps network 10,000 ns 10 us|
|Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD|
|// Just before switching jobs:|
|// Add one of these.|
|// Preferably into the same commit where you do a large merge.|
|// This started as a tweet with a joke of "C++ pro-tip: #define private public",|
|// and then it quickly escalated into more and more evil suggestions.|
|// I've tried to capture interesting suggestions here.|
|// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,|
|// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,|
How to record multiple applications and microphone into one audio file on Linux
Step 0. Terminology
Sinks are for output, sources are for input. To stream source to sink a loopback must be created. More shall you find there.
Step 1. Create output sink that will be recorded
Our output sink will be named
pacmd load-module module-null-sink sink_name=recording sink_properties=device.description=recording
Hardening the USB Armory
As a good crypto nerd, I usually use an entirely encrypted linux FS:
/ but also
/boot using grub LUKS support. It's a good setup but it's not perfect, the BIOS and
the bootloader are not protected.
I recently got a USBArmory and I wanted to apply the same (or a better) setup.
I found some useful links but no clear howto. So this is my setup.
Here's one of my favorite techniques for lateral movement: SSH agent forwarding. Use a UNIX-domain socket to advance your presence on the network. No need for passwords or keys.
root@bastion:~# find /tmp/ssh-* -type s /tmp/ssh-srQ6Q5UpOL/agent.1460 root@bastion:~# SSH_AUTH_SOCK=/tmp/ssh-srQ6Q5UpOL/agent.1460 ssh firstname.lastname@example.org user@internal:~$ hostname -f internal.company.tld
CR-6 post-unboxing checklist
With most of the CR-6 SE issues being due to bad wiring or loose/too tight screws I feel like it is time for a good post-unboxing checklist, to be walked through pre-assembly. Even though I do not have my unit shipped yet, I've seen enough issues and fixes that I can compile this post.
I initially posted this on the independent CR-6 community Facebook group but since not everyone wants to use Facebook (which I totally understand), I will repost it here. I mirrored most of the relevant content of Facebook to imgur.
If you have any feedback or anything that needs to be added, please let me know and I will amend this post!
Note: There are some known issues with this printer - please read the entire guide. (It is long, I know, but this is a necessary evil!)
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.
|# Shell script that configures gnome-terminal to use solarized theme|
|# colors. Written for Ubuntu 11.10, untested on anything else.|
|# Solarized theme: http://ethanschoonover.com/solarized|
|# Adapted from these sources:|