ittttttt's starting RTO mother fuuuuuuuuuckers ... the comments are hilarious, cry babies the whole lot, get rid of them they are dead weight holding all others back.
bring us bbbbbbback bbbbbback
19 replies (most recent on top)
I don't think TOs need to be in the Fab all the time or turning wrenches at all (I'd rather you not). But they should be available (during normal business hours) for issues that are caused by the endless software patches and CIPs that allegedly make the tool more robust but instead introduce more bugs (TD environment). If a tech has already exhausted all of their t/s options and YOU are the escalation path with a rocket lot in the tool, there's a level of expectation that you will be involved in the resolution and not just blow it off until the next day. At this point in my career I know enough about the personal lives of my TOs to know that they are not burning the candle at both ends. Maybe your situation is different.
@en+1jked6t7j nice post. True you can’t do your actual job if you are always fixing problems on the floor. Maybe the issue is lack of training for the techs? Aren’t some of them cheap contractors now? How do they ever get trained?
lots of techs posting here obviously talking about how TD engineers need to be in the fab.
Just remember this: Intel makes chips, not Semiconductor manufacturing equipment.
If we are all in the fab turning wrenches with the techs, we would all just be equipment engineers with no scope outside solving sporadic particle issues or fixing a chiller or worse still, some cr-ppy abatement issues.
How do you think any of those skills translates to higher yields on 18A nodes ? or upcoming 14A nodes for that matter?
do you guys even know the dimensions of what we are talking about here? If we are going to target a tool to bring it back in CL, do any of these shift technicians who don't give a sh-t about INTC once they walk out the fab, going to hop on a phone call to resolve it ?
We spend most of our days looking at data from the tools and microscopic images from characterization labs. And coming up with ways to mitigate defect issues, improve run rates, stabilize monitors, target tools etc.
The entire paragraph above will not get done if engineers are being wrenchmonkeys in the fab. Even mechanical troubleshooting like partitioning issues on a tool requires you to be well versed in making recipes and sequences, not turning wrenches.
The inability to appreciate what other people do for a living and operate as an independent BU without bugging engineers at all times (especially at nights and weekends) is what pi---s me off the most about these ungrateful techs posting here. Oncall ? What a joke. None of those mfers will give a hoot about INTC once their shift and immediately demand overtime as opposed to engineering working overtime and weekends with just a fixed salary.
Buzz off losers.
100% correct. For example, Fab TOs (ESPECIALLY in a TD environment) need to be physically available for tool issues, big bugs, and weird findings that are beyond the equipment technicians' daily scope. Techs aren't communicating these findings to the Suppliers, the TOs are, so having a full understanding of the circumstances leading to these issues is important.
"I'm WFH, send me the logs" isn't going to cut it.
Not true. Ignore this post.
We have PMs disguised as g10 PEs. Go figure
The big issue is a lot of key people do not respond to teams messages, you need to ping them at their desk or go a level or 2 above them to get their participation. These speed bumps add days to weeks to simple projects.
Whether they are at office or home, the main issue is the lack of urgency and how many of these people will steal 10 minutes out of a meeting to say nothing of import but advertise their own false expertise. Too many clueless experts at Intel that fail to admit how little they know or understand.
I will RTO when they pry the tv remote from my cold hands.
Also, I must be allowed to work in my underwear - Al Bundy style. 😁
@af, it’s clear you have no idea how the fab and process development works. Yes, issues pop up that need to be resolved on a very short timeframe (hours, a shift, etc)
This company is a chip manufacturer, Ty’s fab is where the money comes.
Maybe in your software role, or whatever low impact job you do, the issues can wait. But Intel as a company needs the fab people in the office and on-site to have any chance at turning the company around.
Use your brain to understand why it’s actually important
Intel doesn’t pay enough to even take a bus to the office
They are already tracking when (and where) onsite based on the RFID in your badge, and have added AI capabilities to the existing camera monitoring.
Expect performance related actions partially based on that, if you are just badging in once a day then leaving, or in the cafe (or sleeping in your car) during your shift.
It's a side thing but the existing computer usage monitoring is being enhanced, similar to what other tech companies have done.
Not a smart time to be stupid at work.
Hopefully they installed speakers in the bathrooms so we can’t hear our friends’ butt trumpets as we try to expeditiously do our business.
Every TD guy who is not on site should be fired. It's just not a job that can be done remotely.
All those folks that need to take off at 3pm to pick up the kids or take a day off because kids are sick. That's the problem. Run a business and trim the non achievers
@a8+1jked6t7j I don't know what kind of job you have that requires sudden unplanned urgency that having access to people in-person, but not online, can only resolve. I'm sure there's someone out there that applies to, but that just sounds like the typical lazy employee everyone hates that doesn't plan their work and just expects to walk over and dump things on people.
Do a better job at planning and keeping open communication lines between your necessary teams? Bring in higher reports if you rightfully have urgency and your team is uncooperative? IM them? Throw a meeting on their calendar without asking? Set a meeting in person and include others?
2 years post pandemic yet still WFH? DEI ki-led this company
@a6+... you are describing the whole problem. Your method has you meeting to resolve an issue days in the future. If everyone is in the office it get resolved that day. There is no sense of urgency in your style of work. Intel's situation is dire and needs things to be done correctly and fast.
Also, if there's someone you think would be helpful to meet face to face, tell them that you'll be in the office [this day] and you'd love to meet in person to discuss. It's really that easy - I don't think anyone would shut it down completly.
Not sure what you watched or are reading, but none of the messaging has changed from the past 2+ years. The guidelines across Intel have been to try to be in-person when it makes sense. Some teams more than others. Some locations more than others.
It is the rare employee that believes they never have to be in-person. Go into the office if you want to be there or think it's helpful. That one random person isn't going to make your expierence any better.