vrek

Back then they were "west Francia fries" as France wasn't found yet, otherwise a hostorically accurate comic.

Can you just have the board made as a square and then just cut it out with a jig saw?

Lucky you didn't have to get a new home with the grease + high heat = fire situation...

Was it an older person? I remember when a big selling point of chrome was you could search Google from the address bar rather than going to Google.com. On a related note, have you seen my walker?

They are real but rare. Situations that change society as a whole. For example creation of printing press which spread both religion and literacy. Or creation of the combustion engine which lead to cars and trains resulting in the society spawl we now live in. Or the discovery of germ theory which revolutionized medicine. Or the the west India shipping company started selling rights to some of the profits of a shop if people gave them money early so they could afford the ship and the trip, effectively creating stock markets(especially the futures market). Or creation of the transistor instead of vacuum tubes.

People claim things are paradigm shifts so others will give them money but most typically aren't. Like 3d tvs were supposed to be a paradigm shift about 15 years ago, now when did you last even see a 3d movie or see a 3d TV for sale in a store? Vr was supposed to be a paradigm shift for games but it's still incredibly niche due to price, downsides of current tech and lack of software (software isn't developed because there's not a consumer base and there's not a consumer base because there's no software)

If your company was anything like mine find a group of people who you work well with in your normal departments and try to use them whenever possible. For example basically every document released needed a signature from manufacturing, R&D, regulatory, quality. Technically I would contact the manager of each department with quick overview and ask them to assign someone, but I would also include a quick note like "I would appreciate if John could be assigned to this if he has availability". Typically I would also typically of already contacted John and checked if he had availability and if it was within his ability, typically they were willing but sometimes was told stuff like "I would love to but I'm on vacation for 2 weeks starting Monday" or "I could but I haven't work on fault tolerance stack up analysis since college, I recommend Tim as he can give a more thorough review of your analysis". All good things to know before starting out on a project.

Also if you need something done quickly prepare ahead and alert everyone and typically people will comply but don't use this too often. For example one time we had an improvement project, we were told we could use a Friday but report had to be completed and released before Friday morning or people's surgeries would need to be delayed(long story how we got in that situation). I wrote the whole report the week before assuming everything went smoothly, only thing missing was the specific numbers from the test. I sent it out the week before and asked for a pre-review so everyone agreed on the verbiage. I wrote a macro script to do all the analysis and verified it work with previous data sets compared to manual analysis. Test took 6 hours to run, finishing of report took 10 minutes, sent out for review to all signatories and cc'd my boss, the director and the dvp emphasizing urgency. Dvp replied all throwing his weight behind it. Everything was approved and released with an hour to spare before eod. I only did that sort of thing 5 times over 8 years in that role so people respected my request. I know people who said everything was urgent and no matter what the real priority was it got put into the normal queue for most people. Typically I budgeted a week just for reviews in my timeline, we got that one done in about 35 minutes.

I used to be in medical device, be aware everything takes forever. Minor changes were atleast 6 months. I added in a step to have an operator look at some component under a microscope for damage to increase yield. Basically if the component was damaged it wasn't detectable till much later and cost went from about 5 dollars to about 800. It took 9 months to implement and we didn't even have to buy anything or hire anyone.

It's probably too expensive for a joke but you should make a circuit board in the shape of a chicken, one side a bunch of leds on the other a control circuit to randomly light them so the chicken circuit hoard looks like it's sparkling.

Also every person I worked with typically made a serious mistake within 3 months. Initially they start and are being trained and closely monitored. Then eventually they are determined to be good enough they don't need more training. They want to do a good job, impress their boss and Co-workers so the pay close attention to everything they do. They have daily to-do lists everyday to ensure they don't miss anything. They double and triple check everything. Then around the 2 month mark they start to believe they know what they are doing, they got this, it's easy, all that stuff was a waste and they could do this while talking with a friend about their weekend plans. Then they make a stupid mistake, click a wrong button, forget to do a step, put something upside down etc. As a result they mess something important up, company losses money, co-workers are mad because they have to do extra work to make up for the mistake, boss is mad. Hopefully that's all that happens, in certain roles or certain industries it could cause death or massive loss of money or legal consequences. A good employee then starts recalibrating how much attention they need to pay and develop new habits to prevent repeating the mistake. Somewhere around the fifth month they get the right idea and are benefiting the team. Then you quit at 6 months and all that time and money spent on you is now wasted.

I don't know about you specifically but for anything complex or technical it takes atleast about 2 months to be similar to a long term employee. Between learning the computer systems, getting any permissions they need, learning the general work flow, learning what is not normal, what to do when something goes wrong, who to contact if you have issues or need something outside your role for example at my last job part of my job was looking at a process and determining how to improve it, let's say I thought a different fixture would increase throughput. First I had to contact the cad team to transform my thought into an official drawing. Next to see if I was right, I had to contact the 3d printing team to get the new fixture printed. Next contact the production scheduling team to get a test run done, while also working with production supervisor to ensure they were aware, then run the test and analyze the data assuming data looked good, now contact the machine shop to get it made out of metal or traditional milled plastic, now back to original scheduler to schedule final test. That's all assuming no software changes or quality concerns or bio material contact concerns or regulatory submissions or purchasing components from a vendor. Learning who all those people and when you do and don't need to contact them takes time. Previously I also repaired industrial equipment, where are the extra parts? What is the common issues and how to fix them? What can you just quickly do and what becomes a big issue? What is caused by user and what is caused by machine fatigue/issue? Where are the keys for things that are locked up? Who are the vendors if I need to order spare parts? These are only a few examples and are different for every company and every position. You can't learn it from college and the knowledge is useless when you leave that company. Generally if you only stay for 6 months you are a burden to your boss/trainer etc for about 1/3 of your time there. This is why I always hated interns, they may be smart but by the time they get the company specific information they had like 2-3 weeks left. Management would be like "I'll give you an intern to speed this project up" but no, most likely it will only slow it down. I typically took the intern though because it's important to train the next generation but it almost always resulted in additional work for me.

As long as you don't work with cows it shouldn't matter, Now if it a job on a dairy farm...

https://www.cs.umass.edu/~emery/classes/cmpsci691st/readings/Sec/Reflections-on-Trusting-Trust.pdf

The lower you go the harder it is to be able to identify security risks