6,774 karma · joined July 2, 2009
[ my public key: https://keybase.io/tibbon; my proof: https://keybase.io/tibbon/sigs/ATQbF8yqkEUNf6JLuNxyZbNvmQzq1jlUJFAxDp4VOrk ]
I moved from Boston to Providence in 2019. The thought of doing 4-5 hours of daily commute to get into Boston, pay for parking, deal with taking food there or daily expense of eating out, wear and tear on a vehicle… fuck no. Tech barely exists in providence though, so most in office jobs would be in Boston
I did this to myself yes, but having a house that wasn’t tiny and expensive was important to me
Ideally K8s w/Flux is pretty great for this, as I can just make a change in SCM and then let it rip. Hardware dies? Drop in a new one and keep going. Backups handled by the larger system, instead of individual computers.
Additionally, my VPN/DNS and other networking setups with CloudFlare zero trust and MetalLB make it really easy to securely access it from anywhere for whatever service I need, with minimal fuss.
But... getting the USB parts working with K8s is so annoying, as their assumptions around using Docker or Containderd are pretty fixed. Obviously I need to set an affinity/requirement of the node having the USB device, but even after that it just doesn't seem happy. I can see the device in HA, but it never connects.
I'm normally pretty good at getting anything running in k8s quickly, but this is difficult!
I'm going to say "screw it" and just run it bare on a Pi soon instead.
Also, far too much simply typing out code that was unexplained or had no basis in prior text to the learner.
> This book is for anyone remotely interested in game programming, from the arcade junkie wanting to test his programming skills to current game program- mers looking for new ways to market their games. This book uses a unique day-by-day approach to teach major concepts, industry terms, and little-known secrets about game programming.
I said more about it in this comment:
I spent a few years teaching at General Assembly, and in that time I learned so much about pedology, how I often learn, how others learn, and that I can't always assume the way I learn will be appropriate for others, particularly in text format.
I had Teach Yourself Game Programming in 21 Days, by Andre LaMothe when I was an early teen. I made repeated attempts at learning game programming with it, finding only failure each time. Maybe I wasn't cut out for programming? I put it away, and went to school for music instead.
Years later, no thanks to this book, I'm a pretty good programmer. I've looked over it again, and I'm aghast at what I see. It bills itself as needing no real experience. It jumps from "this is a mouse" in chapter 1, to some pretty advanced VGA screen manipulation between chapters 2 and 3. Loops, functions, OOP, data types? Nah - it just throws code at you without concepts. It is shocking if anyone learned from this. I was worse off having read it, and nearly 30 years later kinda salty about it!
I'm good at learning from books too! I taught myself Ruby after reading _why's poigiant guide, Agile Development with Ruby on Rails, the Pickaxe book, POODR, and the Ruby internals book. If a book structures information well, and I can sit and work on practice problems, I can get the concept.
Maybe we learned a lot about how to write programming books around this era? I've generally found books on O'Reilly, Addison-Wesley, No Starch Press, etc to be rather good. They generally consider how to structure learning and information in a way that is progressive and don't make too many leaps. These "Learn in X days" style books in the 90's were basically info dumps, and without Google it was nearly impossible as a kid in the 90's to get help. No adults around me had any idea, and if it didn't work - it didn't work.
I'm curious what the breakthrough was, or what changed. The first decent programming book I ever read was Programming Perl by Larry Wall. I came to it much later, but the ANSI C book made a ton of sense upon first read too.
A good modern intro to game development (and Rust) can be found with Hands-on Rust: Effective Learning through 2D Game Development and Play. It doesn't dive deep into the more difficult parts of Rust, but it also doesn't make you feel like an idiot.
For a look back at 90's games, the Game Engine Black Book: DOOM by Fabien Sanglard really helped me understand the systems and logic of Doom and other similar games.
So often it might be worth quite a bit it someone in another location, but especially after someone dies, there often isn’t the energy to deal with it. So on the street it goes.
You can find some people asking $6000 for a Hammond B3, but then someone can’t give away a D-152 outside of an urban area because folks don’t know what it is on a search. It better than a B3, essentially the deluxe model. But they weight nearly 500lbs and people don’t know how to turn them on to test even (it is a 2 step process)
Would they prefer people avoid them, cancel services, and avoid buying tickets for the moment as a form of picket line? I don't cross picket lines, and would be more than happy to stop my consumption of these things if it helps send a message.
The choice of what union to affiliate with, and selecting their rules is something that should have been done carefully, and with the needs of the membership in mind.
(I’m a proud technology union member myself, and we are currently in bargaining.)