@irvingreid @SwiftOnSecurity How good would you be at your job if you only ever minmaxed trendy fads and never made a mistake? Nobody's hiring for senior NFT engineers.

If you haven't spent two weeks working on something that was instantly rendered obsolete by using a "-G" argument somewhere, are you even doing real engineering?

@irvingreid @SwiftOnSecurity there's some nuance to this; you need to let some things fail, but you also need to unblock and clear the paths preemptively in many situations so they build confidence.

Showing them what good looks like is something they can model on for decades to come.

@irvingreid @SwiftOnSecurity

Sometimes you need to approach a problem from an impossible direction to see it clearly.

@irvingreid @SwiftOnSecurity Same here. I found there's a lifecycle to this mentoring. It takes a decade or more to get good at something. Then you have another decade or two where the younglings will listen to you. "Yep. We tried that on project X. It had this list of problems, and failed to meet this list of requirements. We ended up going with Y."

Then, at some point, they stop listening. Because, "You're old, you don't understand, and you want it the old way." Then they repeat mistakes.

@irvingreid @SwiftOnSecurity The first time I had a junior, he would come every two minutes with a question. So I told him: “When you’re stuck on something, try to solve it by yourself first. If after fifteen minutes you didn’t succeed, come and ask for help.”

When it was his turn to have a junior, he did the same. That worked out surprisingly well both times.