about ~30 years experience. devops/architect now at a major university.
dropped out after almost 7 years w/4 degrees (math, cs, photography, archaeology). yes, i have adhd lol.
i've been programming/building computers since the early 80s, and worked at my unis computer lab help desk starting in the early 90s. after dropping out, got a lame sysadmin job and then somehow got a job at nasa ames in the late 90s (and moved to the bay area). after a short stint there, i was super lucky and hit the job marked right as the dot-com bubble 1.0 ramped up!
it was tough for the first few years as my lack of degree (and general jack-of-all-trades skillset) was definitely a barrier.
but with lots of luck, perseverance and track record of learning quick on the job, i was able to get a solid career rolling. i quit tech about 12 years ago, and have been working in higher ed tech since. now i get to sit in meetings and explain to CS/data science profs how the cloud actually works. :)
hard no for me WRT positron... i managed a university's jupyterhub deployments for a while and we had faculty CLAMORING for this vs. Rstudio.
the problem? the fact that you need a license to use. it's not OSS. you are not allowed to deploy this on a hosted/managed system:
```
Limitations
You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.
You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.
You may not alter, remove, or obscure any licensing, copyright, or other notices
of the licensor in the software. Any use of the licensor's trademarks is subject
to applicable law.
```
Hey, my university is setting up a JupyterHub deployment right now, and my coworker is in charge of it. Do you mind elaborating more on how you went about it, best practices, etc.?
this is great when working in a repo w/a main "prod" branch that you don't commit to directly, but instead commit to "staging" or "dev". alog shows you the entire repo's history for all branches, and hlog is just the graph of the non-pushable branches (plus all feature branches).
i know i'm sounding like a broken record here, but urban ore is definitely a place that if you're ever in the bay area, you need to check it out.
i go at least 3-4 times a year for "something", with "something" being things like:
- a new bin for my inside recycling
- an old street sign to use to plug the old sunroof on my 24 hours of lemons car
- a door to use as a workbench
- just to gawk at the massive selection of antique electronics
reply