Throw tmux in and this is my exact setup as well. I'm looking into finding ways to orchestrate entire workflows across multiple agents in a harness-agnostic way (locally at first).
Wannabe powerlifter here of about 20 years as well. This sounds like an awesome project! Is bar-path the main metric for safety and "better" lifting? A project I had in mind, once upon a time, was an automatic "Form Check Friday" for myself using a Pi + Webcam.
As someone who has been very deep down this rabbit hole and hacked together multiple path and velocity trackers over the years (specifically for olympic weightlifting), there is no extra information that tracking bar path will give you that simply looking at the video won't, and often just adds more clutter. You don't need to graph bar path to see that the bar is looping too far forward after hip contact in the snatch.
Velocity on the other hand is a great metric to track and is used as a proxy for RPE. Mike Tuchscherer was the first one to systematize it for powerlifting a while back, if you've been lifting for 20 years you're probably aware of the name.
Thanks! I think for "canonical" lifts (squat, deadlift, row, to some extent military press) the vertical bar path is mathematically optimal, and for all kinds of lateral or sagittal movements you do more work with weak stabilizing muscles and load joints laterally too. Is it productive work that strengthens your core? Possibly, but it's hard to quantify. It it something that can lead to injury? Absolutely yes.
For more complicated lifts like bench press (J-shaped) or snatch (S-shaped), for example, I would rather set a "golden sample" path with a coach and compare to that.
It's unlikely to be the sole metric, especially given the inverse kinematics of different body types (long/short femur, etc), but together with bar speed, over time, it can provide a lot of good feedback.
It is not "absolutely" something that can lead to injury. Injury itself is difficult to define, and often the reason one experiences pain sensation is multifactorial. Within lifting contexts, generally the factor which has the strongest evidence for injury prediction is how sharply an athlete increases intensity compared to what they have previously adapted to.
No offense, but this post does come across as you only having a surface level understanding of the field. Especially surrounding injury/pain perception, I would be more careful of what you assume is true, there's far more nuance.
This. With so much of my work being done with Claude Code via terminal, I’ve used vim and tmux more than I have in the 20 years since I was first introduced.
With all the buzz about orchestrating in the age of CLI agents there doesn't seem to be much talk about vim + tmux with send-keys (a blessing). You can run as many windows and panes doing so many different things across multiple projects.
The way I see it using tmux to orchestrate multiple agents is an intermediate step until we get a UI that can be a product offering. Assuming we get orchestration to the level it has been touted, there is a world where tmux is unnecessary for the user. You would just type something to one panel in which the "overlord" agent is running (the "mayor" if we talking gas town lingo) and that agent will handle all the rest. I doubt jumping between panes is going to stick around as the product offering evolves.
Nearly this, but using ghostty instead of tmux. You don’t get the remote connection aspect of tmux, but for splitting/zooming/preserving windows it is fantastic. The best part is you can configure natural shortcuts rather than using a leader for everything.
Don't know about high-level discussion, but the only other active forum I frequent other than Reddit is https://www.tacomaworld.com/. Really active user base and a ton of good info about different generations of the Toyota Tacoma.
This developer only has about 6 years of experience working at Amazon. It seems surprisingly naive how little this person understands about what a decent PM shields them from as an engineer, but I've heard working at Amazon sucks altogether. So, par for the course?
The MyFitnessPal desktop application sucks big time. In my attempt to create a better alternative, I found that their value doesn't come in the form of good UX or performance, but their food database. And it's huge.
I didn't want to pay for PostgreSQL on Heroku, so I just dropped the database, but the application is still deployed.
I don't know, I like keeping up with what my old co-workers are up to without actually hitting them up. It's also my go-to place for job hunting. It seems like the most popular.
