This guy carried me over 500 miles of blue highways to Lake Placid and back over the weekend without a single hiccup. I think it's earned some TLC this week that I've been putting off for too long: re-timing, new points, little tach work, bigger break work.
I'm really curious what a generalist, functional ROS setup looks like. Because I certainly have never had one.
I'm imagining a collection of something like 15 images, one for each ROS distro, each with their own extremely vanilla ubuntu install, an enormous set of dependency packages frozen in time from 2014 or whenever that distro was released, and every single tool in the ros-extra-extra-extra ecosystem. Also, whatever general environment & python crap was in-vouge at that particular time.
it's a million degrees in #Boston today and I'm considering hopping on a bluebike -- I'd say that there's a 20% chance that both me and the bike wind up in the Charles.
mean rant to flesh that thought out
when I read shitty code I try pretty hard to give the benefit of the doubt to whoever wrote it; it's rarely their fault that is sucks, and there were probably a bunch of weird circumstances at the time that I'm not aware of.
But every codebase seems to have its own "usual suspect," where you stumble upon some new terrible thing, go to straighten it out, and when you look at the history to get some context for why it's there, there's that fucking name again!
It is so nice when projects outline instructions for building & installing from source right in the damn readme or wiki or w/e -- and while it's rarely fair to be annoyed with the maintainers of a project for not doing more for you, it's also such an easy thing to just list out the dependencies and tooling you need to compile this stuff!
generally tooting about: projects/hobbies, software stuff, boston, running, motorcycles, and pictures of my mediocre cooking.
small, relaxed instance for friends