Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

(post is archived)

[–] • 3 pts

There needs to be at least three pajeets in that picture. One of them needs to be asking "what is a baton?".

[–] • 1 pt

Be Pajeet Sound like a mouthful of spunk when talking “What is baton?” Put off deeply offensive stench Shit on carpet Con old lady out of pension using gift cards

[–] • 1 pt

"Where is the documentation on the baton handoff?"

[–] • 3 pts

Today it’s usually up some faggot’s ass.

[–] • 2 pts

The first one could almost be the Honeywell "Throw it over the wall" model.

[–] • 1 pt
[–] • 1 pt

I spent years building detailed Microsoft Project schedules, then the follow-thru managing and executing them. Holes were self evident and quickly plugged with tasks and assigned owners.

Maybe todays engineers are acting less formally? Anyone with a good solid overview of the steps and tasks required to complete a particular project and knowledge of MS Project could create an incredibly solid project plan. Usually the only issues I ever saw were sliding timelines due to delays in completion of predecessor tasks.

[–] • 0 pt

I bet you also had BAs assigned to babysit the projects to ensure follow through.

[–] • 1 pt (edited )

I wish! Nope, just me, my manager and the New Product Introduction group following along on project status. My last 7 years as a Semiconductor Engineer primary responsibility involved new product intro and ownership of the portion of the new product portfolio for the complex parts I had recently introduced. Secondarily, I had many in-house projects to boost throughput, enhance automation, introduce Flash memories/help the fab gurus dial in their new process, cross discipline problem solving and more (I far preferred special projects over the mundane routine stuff). We were lean before lean was a thing. All new product intros were guided by an MS Project plan written by myself or others. I wrote project plans for most of the site specific special projects I owned. Updating the plan was the responsibility of those who were assigned the individual tasks within the plan.

Back in the 1980s was more like you describe. As I was designing data structures, editors, operating system, calibration routines, decomposers, test solutions for an in house rack and stack "Auto-Fmax Tester" that we called the AFT (performed Fmax, Tset, Thold, MinPW, Trec testing), there was a BA anxiously looking over our shoulders running back and forth to management reporting every shred of our progress. Two other guys were working on the hardware side of that system, I owned the software development side. THAT was a fun project.