Yeah, I thought that was Intel's MO. Intel quit making RealSense only after a competitor (OAK-D from Luxonis) became viable. They just want to make chips. It's my impression that they only build "lower" devices as a proof-of-concept for how their chips can be used.
An interesting, useful real-world example of this is Gitolite [0]. Gitolite requires no background daemons or anything -- just a normal unix/ssh environment.
I'm curious what your new bike is. I currently have a 12 year old (but well maintained) Trek 1000. I'd like to get some better derailleurs (I'm constantly having to adjust and clean mine). But maybe I'll just get a better bike, I don't know.
I actually really liked my Trek 1000. I was very tempted at the time to just get a new groupset and wheels for the thing, but I had a really good deal on the Merida.
It's a very well built frame, it doesn't look the prettiest, but it gets the job done.
I would definitely put it under my own name, if I were you. Like another commentor mentioned: if you leave the company, you still control your own repo.
Also, whenever I interview programmers, I always browse their Github (or BitBucket or whatever). Not having a Github isn't such a bad thing, but if you have a cool (or popular) project of your own there, it can help you get noticed.
(Of course, you need to be careful that your employer isn't going to freak out about you posting code openly. I have a habit of starting side-projects in-between jobs, then only do updates on the weekends after I've started a new job.)
Another option, perhaps: put it on your own repo, but track it from the company's repo on the company's webpage. (If they'll let you do it, that is.) That gives you some free visibility.
There are good office jobs and there are bad office jobs. There are good employers and bad employers. The best jobs I've had usually have some basic deadlines (measurable goals and results), and some basic rules (show up every day), but other than that, not much structure or micro-management or anything. If you're a full-time programmer on a team, then you might have a lot of little tasks assigned to you (eg: "add feature X to user profile page", "fix bug Y on the logout screen", etc.), but not constant surveillance or anything. If you're constantly checking in code to Github, then your boss knows that you're working.
That area is prime real-estate in Tokyo. Developers have been itching to build shopping malls, etc, there for ages. It might be a parking lot during the Olympics, but afterwords it's going to be turned into something much more expensive.
The fish market, OTOH, doesn't have to be in any particular place. It needs good access to the ocean (boats) and good access to the roads (trucks). Moving it by a few miles isn't going to change their economics by much (if any).
I third this. I've installed/maintained and used gitolite, gitlab and gitea.
- gitolite: easiest to install and manage. But there's no web interface. Your entire workflow is with git itself (and maybe some SSH/Unix tricks/scripts).
- gitlab: huge, bloated beast. Many, many different components. Difficult to understand all the pieces. Uses a ton of ram and CPU cycles. UI and workflow is different from Github.
- gitea: single, stand-alone package. UI and work-flow is identical to Github. Given all that it does, it seems about as simple and light-weight as it could be. (My only pain point is that it's written in Go, with Go packages, and I don't really know anything about Go...)
In my entire life, I've never encountered the Trolley Problem, and I've never met anyone who has.
Most safety problems in driving can be solved by slowing down.
The problem with AI is all those weird, little edge cases that humans can reason through -- for example: if there's a deer next to the road, then I'll slow down, even if it's not on the road yet. I've known many people who have hit a deer when it spontaneously jumps into traffic. Or something like: someone's not quite staying in their own lane, so I have to be careful when I pass them.
I wanted to say something similar to this. But I think you articulated it much better than I could have.
I think that now, today, Linus could afford to be less of an asshole. But I honestly wonder if the project would've have succeeded so well without him being so strict and demanding in the beginning.
EDIT: Yes, I think that it is possible to be strict and demanding without doing ad-hominem attacks and without swearing. It's just that it's very rare.
