chomping at the bits
Here is a quick post on how I’m trying to limit ads and tracking in my life and what it costs me. Is it perfect? Ha no, but this can be a pretty decent starting point for someone and get you a lot closer to diminishing returns on additional effort.
This is the approach I use for work/professional related slack channels - essentially environments where I’m paid to be on Slack. These tips are not for everyone or for every situation. They are only tips that have worked for me at a few companies where Slack is used as an infinite landfill for conversations.
Recently, I got into a mountain biking accident and broke myself. Like most really bad server crashes, I had to be surgically repaired. Living in the USA, part of the medical process is getting financially blindsided by a bunch of bills you can not understand or nor likely afford. While on medication, I thought it might be a good idea to try to calculate which day might have the most emotional…
In the modern dev world, kubernetes and kafka have created quite a bit of technical climate change (not to be confused with the real climate change of bitcoin). Needing to better understand this hype-cycle, I thought it would fun to get a little 1u server and play with tech’s Bravest New World of complexity.
Database bloat is something that only the rarest of postgres databases can get away with. As more and more people give us control of their databases for something like AWS RDS (Amazon Web Service’s Recursive Disappointment Service), using extensions like pg_repack can get a little trickier.
I know a lot of readers come here for photography or cooking content, but I’m going to actually talk about something technical: SQL Joins. Now, I know if you’re a modern developer and doing stuff like kafka, boltdb, redis, or whatever, you might be asking yourself “what is a join? is that when you add more latency to a cluster by spinning up more nodes?” and you would be wise to ask yourself that.…
The Technical Interview:
Gentle Intro:
I’ve been looking at some monitoring solutions for my network at home. I’ve used nagios in the past but it has quite a few drawbacks. Most noticably, the whole fact that it doesn’t scale to millions of nodes or use a popular javascript framework for its front end pretty much makes it a no-go for my needs. Thanks to my background in technology, I know that the next best option is to just write…
When talking to people about data archival strategies, a question that comes up regularly is ‘how do I even get the archived data?’ This is in part because ~modern~ web frameworks like Rack-on-Rails do not always make multiple data sources a straight forward task. True to form, for every problem a web framework can create, postgres can usually fix it.