I’m sad to announce that I am leaving @themarkup to pursue other projects, which I will announce soon.
It was an honor and a privilege to found @themarkup five years ago to create an investigative newsroom that integrated engineers and journalists. We showed the world what journalism could be: math literate, computationally superpowered, and human-centered.
On my departure, I thought I would reflect on the ten lessons I learned leading these investigations. https://themarkup.org/hello-world/2023/02/04/journalistic-lessons-for-the-algorithmic-age
More progress on my knitting clock. I've mounted all of the main components to the backer board. I also wired two buttons to GPIO pins and wrote a simple script to advance the machine forward and backwards one stitch with the buttons. I'll likely use this when I'm casting on and casting off.
The top of the clock will be where the stepper motor is. Now that I know how the pieces fit, I will cut the top so it is house-shaped, and build the sides and front of the clock.
I wrote a blog post about the dangers of focusing too much on hardware specs to predict performance when choosing hardware. In my experience many other factors (such as the software the hardware will run) have much more of an impact. Focusing on specs alone incentivizes bad practices like planned obsolescence and disposable hardware.
U.S. border officials copy the contents of up to 10,000 phones and computers every year and save them to a big database for 15 years, as we first reported in September: https://www.washingtonpost.com/technology/2022/09/15/government-surveillance-database-dhs/
Following pressure from Sen. Wyden, the agency, CBP, now says it's considering shrinking that 15-year save time and plans to give people more details about what they're doing: https://www.washingtonpost.com/politics/2023/01/31/abraham-accords-expand-with-cybersecurity-collaboration/
I knitted a shawl! Well, the flatbed knitting machine did a lot of the work, but I helped. This was the second attempt as I ran out of yarn halfway through for the first attempt and the local yarn store only had the single skein. I ended up selecting a different yarn for this attempt.
All the functional pieces of my hackaday-inspired knitting clock are in place:
* Working circular knitting machine
* Spare Raspberry Pi I had lying around
* Adafruit motor control hat
* Spare stepper motor from a broken 3D printer
* Software to control the stepper motor
The next and more challenging step is to figure out the best way to attach the motor to the knitting machine and build an attractive case to mount everything.
I rotate through my set of favorite razors whenever it's time to change the blade. The Gilette Fat Boy and Slim (far left in picture) are great razors, as is the red tip (3rd from left). Yet each time I rotate to the Stahly Live Blade (center of picture) I'm surprised and impressed again at how well it shaves.
I don't know if it's the fact that it vibrates, or the design of the head, but with a new sharp blade it beats everything else in my collection. Underrated razor.
As a #cyclist, I deal with some #geography. #Geospatial information for everyday means #maps.
Here's a tutorial for making a map style for YOUR specific needs, with minimal amount of hassle.
https://dcz_self.gitlab.io/posts/quick_maps/
I use #openstreetmap as the source of data, #postgis for the strage, and #TileMill for rendering.
Sadly, I called off the #cycling trip for which I made my style :(
My Purism GPG key expired today so I updated the expiry and published the key to keys.openpgp.org (the link is in my profile).
In my case I normally use subkeys stored on smart cards, and keep my private keys offline and stored in a safe place on a pair of thumb drives for redundancy, so updating the expiry is a bit more involved than it might be for most people.
The best way to get over the fear of messing up something you have handwoven is to put it to use right away!
I finished weaving my pair of doubleweave overshot hand towels! I'm really happy with how these turned out.
In these pictures you can see how the colors invert on the opposite side of the towel. On one towel I experimented with inverting the colors for the stripe and I think it does add an extra dimension and visual interest to it, but I'm also curious which of the two you prefer. I also subtly modified the pattern on that one so the pattern around the stripe was symmetrical.
Another batch of vintage Knitking magazines arrived! This is an even larger batch than the last one from the late 80s and early 90s, and spans the years 1972 through 1978. I have the full year's worth of issues in some cases in this batch.
My wife reviewed the last batch and while she found many of the pictures amusing, she didn't want me to try to make any of them. We'll see whether this batch from the `70s does any better!
After seeing this @hackaday post about a knitting clock, I've decided to try to make one of my own. It will be my first electronics project with stepper motors so I imagine there will be quite a bit to learn.
https://hackaday.com/2023/01/23/knitting-clock-makes-you-a-scarf-for-next-year/
For the second fancy hand towel, I'm experimenting with inverting the colors for the stripe section. I like the effect but now I'm wondering whether it would be even better to invert the colors for the borders around the stripe as well. The problem is, now that I've committed to this, I can't really try that idea out on the other half of this towel without making it asymmetrical.
I finished weaving the first in a pair of fancy hand towels. From this angle you can see how the doubleweave overshot technique makes the pattern reversible--the opposite side of the fabric has the same pattern but the colors are inverted. I also somehow leveled up on my selvedges partway through this towel.
These are for us to use and don't have to be a matching pair, so I'm going to experiment with a different stripe pattern for the second one.
I finally started weaving the next in my series of fancy-so-you-feel-guilty-using-them household items: fancy cotton hand towels!
This project is an excuse to try doubleweave for the first time. In this case I'm doing a doubleweave overshot technique which results in a dense, thick fabric without the long floats overshot usually has.
When I finished threading my warp, I discovered I had some unexpected threads left over. Oops. So when I sleyed the reed, I painstakingly double-checked every threading and caught a few mistakes.
In one case I had to insert temporary heddles, and halfway through I found I threaded a pattern twice in a row, so I had to shift the remaining 200+ threads, a pair of heddles at a time. After 13 hours total to measure warp and dress the loom, I'm now ready to weave.
The biggest piece of advice I'd give to colleagues who are devs, is to figure out what you will do when software dev work moves from many opportunities writing code at a large number of companies to fewer jobs managing automated systems that write code.
Sysadmin/neteng careers made that transition w/ cloud over the past decade, the remaining major cost for tech-heavy orgs are devs, which is why the industry focus is on reducing that head count with automation. Tech is not there yet, but coming.
If you were laid off recently, especially if you are taking it personally, I recommend reading The End of Loyalty. It covers the shift over the 20th century from companies providing lifelong employment (retirement watch, pension, etc) to mass layoffs at the drop of a hint.
Take home message is that the future promises not only little job security, but less *career* security. Have to be prepared to retrain/retool, and possibly even change careers multiple times during your working years.
Technical author, FOSS advocate, public speaker, Linux security & infrastructure geek, author of The Best of Hack and /: Linux Admin Crash Course, Linux Hardening in Hostile Networks and many other books, ex-Linux Journal columnist.