Cloud-cutting is an interesting journey, even if temporarily done.
Some offline alts:
1. Penpot for ui design
2. Llama for stackoverflow (from this thread, yet to try myself)
3. Python had devpi to cache packages. You might find something similar for npm.
I also found vscode plugins are mostly offline. A nuc-style box with docker + glinet router may help if you are not alone on this journey.
It might not align with current trend, but I would like to make cloud-cutting a norm, instead of exception.
Similar to supervised and unsupervised learning, one can see dual paths on this journey. One path answers the questions which have been in user's mind. The other explores unasked ones to finds new insights.
From the text, feels like user agent should be capable, it should let site request sensor data and randomly reject certain requests after X (random) seconds, while providing fake data in other cases.
I tried to change config.py to use ggml setting, but I did not see any request going to local llama-cpp.server. It keeps on asking for openai key. The local llama-cpp.server is up and I was able to make swagger calls for completion.
Assuming that may be I missed something, I deleted ~/.continue and trying to start from scratch (vs code message: Starting Continue Server ...). I do see FastAPI is up on http://localhost:65432/ still vscode dialog shows same message. Where I can see the logs what its trying to do? What am I missing?
I followed this teaching path: scratch > python > sqlite > javascript (web).
I am missing algorithms and OOP, and will look for gradual learning resources in these area.
One recent area I tried was observability. With prometheus and grafana, they got into collecting more data points and creating visualizations for them. Bangle.js is another one.
It all depends on the culture that your organizational leaders support.
If they support your team's culture, then you are in a wrong org.
Options: 1) Exit, 2) Invest your time to change them, 3) Challenge yourself to fit with them without losing your motivation, 4) Become like them.
Life is short, and this team is not a good benchmark/reference point for your career in job market, so easy route is #1.
If your leaders do not like such culture, then you have an opportunity to become a change leader. Assuming you are an IC, this path will likely require you to transition into a people leader. Make sure your leaders in sync with your change plans. (see HBR paper: power failure in management circuits).
I see what you are saying regarding artboard view.
But is it necessary? Can't the artboard be visualized in a better way?
If such high-level view is desired, won't rasterized details be sufficient till one zooms in?