Tehhund

https://knowyourmeme.com/memes/makankosappo-hadokening

Bold answer. I respect that.

Would you rather fight one horse-sized duck or 100 duck-sized horses?

That is poop from a butt

Cum

https://us.macmillan.com/books/9781250767615/sciencecomicstheperiodictableofelements/ - this series of Science Comics is pretty good depending on their age.

http://www.andreabeaty.com/rosie-revere-engineer.html - for you get kids, I like Rosie Revere, engineer. It doesn't teach any science or engineering, but it teaches kids that science and engineering require mistakes and iterations, and it's okay if some of your attempts don't work the first time. Maybe it's my perfectionism talking but I think that's an important message.

I ain't reading all that. I'm happy for u tho. Or sorry that happened.

This is awful. Thanks for sharing.

You eat roads? Ew.

3.14159265359 (ok the last 9 is actually an 8 but it's followed by a 9 so I round up).

Not exactly obsolete, but there's no reason for anyone to memorize that many digits of Pi except for trivia. Number of times it has come up in trivia: 0.

This post is a little too vague to give real advice. You don't tell us what industry you're in. You don't tell us if the engineers are the end users of the software or processes you're working on, or if they will implement the software or processes you're working on.

If they're the end users, they might be concerned that the changes you're designing are going to make their jobs harder. A lot of changes in the past couple decades aimed at "efficiency" have involved making people take on more work for no additional pay, then firing the administrative staff or other engineers who used to do that work. Even if that isn't the sort of project you're working on they are reasonably wary based on past experience. Or maybe it's not clear to you how this will make their life harder but management will find a way.

If the engineers are writing the software that you are helping design, how are you helping to make their jobs easier and more fulfilling? It's an unfortunate fact that software engineers are sometimes treated like misbehaving vending machines that will produce software if you force them to. If they are writing the code, there's a very good chance that they know more about this process than anyone else in the room, but are they treated like they know more than anyone else in the room? Is their expertise valued or are they treated like roadblocks when they give their expert opinions?