107 karma · joined March 25, 2022
Maybe I'm unkind, but I've never been a fan of the Wake. It's always seemed to me to be the sort of thing academics in English literature departments and lovers of abstract art really go for, but few other people can appreciate. (Nothing against literature academics or abstract artists -- it's just that their tastes are informed by things that don't inform most people's!)
If you want to appreciate Joyce as a more approachable author, 'Dubliners' is a great collection of short stories and not experimental.
Reduce the advice to something short and memorable. A rhyme, pun, or clever garden-path sentence are all good techniques - different people like different kinds of wordplay, so have a bunch of these at hand and know your audience.
Make sure the message is the same across time. People trust consistency on the one hand, and on the other people can become worn down by hearing the same advice for a decade and decide to adopt your thinking.
Charge a lot of money for your advice. People are more likely to accept advice they paid ten thousand dollars for over advice they paid nothing for.
Spell out everything that your hypothetical friend would have to go and learn for you to feel comfortable giving him even the most junior-level coding responsibilities or vouching for him as a "yeah, this guy can do the job" to a professional contact of yours. Write it all down, show it to your dad, and spell out the effort involved. That's what he's looking at learning in order to be taken seriously in the marketplace.
(I'd venture that some kind of consulting/contracting is what he'd wind up doing, both because I don't think many companies would take a resume like his seriously for a junior developer position and also because I don't think someone who's been at the top of the org chart would tolerate going to the bottom of the org chart for very long.)