Depends on the day. Mostly playing with the applications I'm developing to try and find gaps or rough edges, or reading over code and developing further AI tooling when I find disgusting code (to try to detect/fix/prevent disgusting code of that nature). Also, talking to coworkers to learn about the products we build and the business we're in.
Ah, well... I can't say that there's any real hope.
I dove in in ~2023, and I'm about as deep in it as one can be. The better I get at it, and the better the agents get, the less time I spend even doing what I do - one prompt will often take 3+ hours. I often keep 8+ agents churning for the whole workday (and leave them running when I leave, too, and it's very often that they'll work from 4pm to midnight or later). I was responsible for 499 commits last week (very little new functionality, though), and I felt pretty useless at the end of it. I keep thinking I should code something, because coding feels productive in comparison, but going by results, it's pretty far from economical to write code by hand, and quickly approaching as bad as shipping goods by foot.
It lets you see the position of the motor's shaft. That's used in some motor control algorithms, even if the motor's position isn't exactly the joint's position.
Tabnine has an IDEA plugin. It's not quite as good as Cursor, in my opinion, but it's better to have Tabnine and IDEA than Cursor and VSCode.
It started out as just predictive text, but now it has a chatbot window that you can access GPT, Claude, etc. from, as well as their own model which has better assurances about code privacy.
It seems like you might be able to enable some optimizations with EXTRA_CLING_ARGS. Since it's based on cling, it's probably subject to whatever limitations cling has.
To be honest, I don't know much about the speed, as my use-case isn't speeding up slow code.
Sure! I tried pybind11, and some other things. cppyy was the first I tried that didn't give me any trouble. I've been using it pretty heavily for about a year, and still no trouble.
I expected that dropping down to C/C++ would be a large jump in difficulty and quantity of code, but I've found it isn't, and the dev experience isn't entirely worse, as, for example, in-editor code-intelligence is rock solid and very fast in every corner of my code and the libraries I'm using.
If anyone could benefit from speeding up some Python code, I'd highly recommend installing cppyy and giving it a try.
When you get a workflow down and need quantity, though, resin is cool. Since it exposes the whole bed at once, I can, for example, pull 24 small prints off of a small printer every 1 hour. 2 days of production, and I have hundreds, using just one printer. With FDM, this particular part, FDM couldn't even make, but if it could, it'd be more like 15 minutes per part - would need a small print farm to keep up with literally one $150 printer.
I don't even have a space for the resin printer right now, though. It really needs a dedicated and well-thought-out station to keep the toxic stuff from ruining your day.