Thank you for taking time to visit! This is basically a journal of thoughts and a collection of resources. In the day of social media and YouTube, blogs are kind of quaint. But I suppose I’m kind of quaint too. The blog is a running thread of my thoughts on various subjects, mostly around technology and software. There is also a resources section where I put things after a thought has matured a bit, and it is worth sharing more formally.
For the resouces, they usually start with a number of blog posts. Then I try to formalize things a bit. They are geared to larger projects, with integrations and architecture needs, etc. But I hope projects of most any size can utilize what is there!
Some years ago, my manager asked me if I ever get tired chasing the bright lights. I had no idea what he was talking about. I did my work… and sure, I stayed up to date with the latest trends in technology… but he knew that was to help the company, right?! Back then, it had not occured to me that those were precious cycles that needed to be used on higher priority work.
I mean, if I didn’t have that latest container starting up via kubernetes on AWS, how would I ever know if the latest TensorFlow could be installed on it, and still take advantage of the GPU? Because I would want to make sure it was ready for me to a little time tweaking my MNIST model via a Jupyter notebook. Right?
(Updated for 2018.)
I get distracted by bright lights. And whether I like it or not, I need to to satisfy my id’s demand for instant gratification… At the same time, trying to avoid sacrificing the long-term plan and what is happening now.
After much meditation on this “id problem,” I found a nice third option between infinitely planning for the long-term and investigating that bright light. If I take a moment to “coredump,” then the bright lights don’t take over the day, and I get back to the priority work. Call it a FOMO journal. My quaint little site is the way I have learned to compromise.
Ctrl + Z
+ Stopped coreyt-scheduler-ML2-EDF-LST
$ pgrep -f internet-brightlight
$ _blpid=$(pgrep internet-brightlight)
$ ps -p $_blpid -o %cpu,%mem
$ gcore -o /tmp/core-internet-brightlight $_blpid
0x76f46588 in read () from /lib/libc.so.6
Saved corefile /tmp/core-internet-brightlight.665
$ gdb -q -nh /tmp/internet-brightlight.$_blpid core
(gdb) set logging overwrite on
(gdb) set logging redirect on
(gdb) set logging file /tmp/brightlight-trace.log
(gdb) thread apply all backtrace
(gdb) backtrace full
$ _ts=$(date +"%m_%d_%Y_%H_%M_%S")
$ tftp mybig.id -c put /tmp/brightlight-trace.log /blog/brightlight-$_ts.log
$ kill -9 $_blpid
Thanks for visiting!