Yeah, definitely needed to move on after so long but I certainly learnt a lot from it!
Now said contributor works a bit more on the project and adds some great new functionality, but floorp don't agree it fits their plans. So the contributor decides to make their own fork called ceilingp and build from that. Nope, they don't have the license to do so. They can take the mpl parts. They can take their own parts (they didn't sign an exclusive release of their code). They can add their own new code. They can't use the rest of the floorp code though.
So floorp gets the benefits but no one else can build off it without permission (save for private use without releasing it and potentially having others do the same).
I was pretty much thrown in and learnt on the job. I shadowed another technician for a bit that showed the basic maintenance servicing steps for the major machines, but then went out on my own. I'm in Australia and we had instruments in all major cities as well as New Zealand, so it involved a lot of flying around and fitting in as many customers as possible. So I had to be able to troubleshoot fast and ideally fix things on the spot.
Often it involved figuring out a temporary workaround whilst a part would need to be ordered from the US or similar issues. My main skillset was being able to think quickly like this and improvise. Being able to understand exactly what a machine is doing (not just the theory the lab techs were thinking about, actual things like gas fill reservoir A, valve 3 open to reservoir B with vacuum guage etc) was more important than anything else I feel. Especially considering we were a small company so couldn't afford to carry around every conceivable spare part, not much of the machinery was based on off-the-shelf parts so we mostly carried the most likely parts to be needed in general.
My IT background was mostly useful for dealing with the inevitable issues with their terrible 16-bit era (!!) software and trying to get it running on Windows 10. Of course the manufacturer wanted them to just replace the system with the new model, but they were exactly the same internals with just newer controller cards running (very very slightly) updated software. This would cost up to a quarter of a million dollars, so you can imagine that not many customers were excited to jump on that!
I would say the automotive technician skillset likely overlaps a little better, especially if they are from the electrical side. My IT skills were useful as I mentioned (and I could talk-the-talk with the university or corporate IT teams in order to get required permissions etc) but most of the harder problems were physical and electronic in nature. As you mentioned, I was interested in the science part too, and funnily enough a couple of the universities got me in to teach the theory of what the systems were measuring, which I literally just figured out on the job haha
Of course, this all depends on exactly what kind of equipment you are talking about. For reference, I mostly dealt with gas adsorption, mercury porosimetry, laser or vision particle sizing and helium pycnometry. We also worked with a few other bits and pieces here and there, but that was the vast majority.
Oh, in terms of pay, I took a massive pay cut to work there. I'd been in IT for about 12 years and needed a change. I knew the boss of the company from Judo training and he asked if I'd be interested in joining. Not the most normal career path but I figured it sounded interesting.
Sorry for the rambling structure, I'm at work and was jumping back and forth to here as I could.
Mostly on the job learning. Had an IT background and basic electronics skills including crude soldering at the time, but mostly I was just good at troubleshooting and thinking through problems. Every machine was very specialised so it was hard to get much info and a lot of problems were unique to that machine for that user with that sample in that condition...
My old job was servicing niche scientific equipment. Glad to see you saw that opportunity - there are a lot of shitty products out there selling for five or six figures, and often running technology multiple decades out of date.
Hearing your monitor squeal when you got the modelines wrong was fun.
Currently using gbar in Hyprland as I got a bit overwhelmed trying to learn too many things at once (gbar is very limited but simple to configure). I've always been thinking of moving over to a more flexible option like eww though, and this might be a good reason to do so (keeping things consistent).
Which proves the earth is round.
Yes, that's what they would say. I'm not sure if you are disagreeing with me? No one I've ever heard says Legos here in Australia. I'm playing with my Lego. Check out my Lego. I'm missing some of my Lego pieces. Pick up your Lego.
Mostly the second one, yes. Lego. Lego bricks. Lego pieces. Boys of Lego. Never Legos.
I think it is mostly Americans that say that. I've never heard anyone say it outside of reading it on American centric forums.
Old macbooks make great Linux machines!