hiring criteria is not uniform, it varies widely across all companies. Keyword driven hiring + contrived interviews that are disconnected from the actual work being performed (but easy to evaluate - this is substitution bias) has damaged engineering culture everywhere. The easy money period of 2018-2022 exacerbated these trends by removing accountability and causing rushed, loose hiring.
real answer - have generational wealth, attach the documents to your trust. This should last either until your nation’s currency collapses or the trust value does.
Trust documents are usually held privately, and not publicly recorded (as their entire point is to shield this estate planning and asset holding from the public). If you put it in someone's will, upon their death the will would be recorded and it would persist as long as the jurisdiction does maintaining the will on file.
For high reliability, I think I would suggest engraving it into a low reactivity nonvaluable metal, perhaps titanium sheet would be a good choice. Couple that with a backup on printed archival paper using carbon toner or an art-grade ink or dye. Between the two of them they will probably resist damage for 100 years or so.
Brass or bronze would also be a decent option, but you'd have to make the text larger for it to be readable with corrosion. Perhaps braille would be an interesting choice there.
And ceramics are a great choice - clay tablets, when fired, can last millenia.
I think between the three of a metal sheet, clay tablet, and paper book, one of the three is almost certain to survive a century.
join after the A if you care about money. Join before the A if you are uniquely mission aligned or technology aligned, e.g. it’s 2016 and you want to work in VR, and aren’t optimizing for money right now. Early stage is fun and you’ll learn a lot and that’s about it.
Many people very much cannot cook because they have poor kitchen skills (or even none at all).
"Anyone should be able to follow a recipe" is far from reality, especially since the vast majority of recipes are not written for the kitchen illiterate.
Nobody is born with "kitchen skills" whatever that means. You have to spend some time learning it, and everybody can do that. Trying to explain chopping onions as "kitchen skills" is just running away from the challenge.
Jumping to conclusions about what "kitchen skills" means aside, the fact that nobody is born with them is precisely the point. Congratulations, you understood it!
Slightly less facetiously, "anyone can follow a recipe" makes about as much sense as "anyone can follow a README". Is it some arcane black magic that only a select few can decipher? No, but at the same time if you don't recognise that there is a baseline level of technical literacy needed to actually follow your average README then you might have your head stuck too far in a bubble.
Following a readme on a github project is obviously a very technical skill and conflating it with following a cooking recipe where the complexity level is around "chop onions" is a strawman, I haven't claimed such.
Cooking is very much a technical skill, much more so than following a readme to install and set up some end-user-targeting project or other. I've seen too many flat-out horrendous meals from people who self-describe as "knowing how to cook" to be convinced otherwise.
Have you looked at a typical recipe recently? Here's an example (https://www.bbcgoodfood.com/recipes/oriental-egg-fried-rice) from the "quick and easy" section of BBC Good Food, a site that's regularly in the first page of search results for various recipes. Never mind that it expects you to have procured cooked chicken breasts from somewhere (and oh boy are those easy to turn into a bland, dry, rubbery mess if you don't know what you're doing)...do you honestly think there is no room in those instructions for someone who does not already know how to cook to screw it up?
Here's a recipe (https://urbanfarmie.com/instant-pot-jollof/) for a more complex dish that I am intimately familiar with, which is how I can tell you for absolutely free that if you just "follow the recipe" as described you will very easily end up with a soggy mess at best and burnt rice at worst.
Or - since you seem to like patting yourself on the back about onions - the next time you're following a recipe and it tells you to "sweat" or to "caramelise" onions or "sauté until golden", maybe spare a thought for how likely it is that someone who is actually new to the kitchen will get the correct result.
Cooking is so easy, everyone who has hands, can read a book and a clock can do it. Start with eggs or pancakes, work your way up from there.
My kids learned to cook from age 9. Now everyone can cook in this household.
I can’t take any adult who says it’s hard seriously, especially since I grew up in a culture where I heard a myriad of excuses from ‘manly man’ who think of it as a woman’s job.
Refactoring UI is a well known book for learning about design as a developer [0]. It's co-written by Adam Wathan of Tailwind even before he made Tailwind. Steve Schoger, the other author, refactors UIs on YouTube [1] which you can take a look at too, lots of good tips there and he talks through each one and visually shows you what changes and why.
Timing imo. I think the tech labor market bottom is in the past, venture capital is flowing again, companies that over hired have corrected it, interest rates are on their way back down, and a bunch of huge IPOs are lining up for 2026 - Stripe, OpenAI, Anthropic, SpaceX, Databricks, Canva, Discord - which is going to inject a bunch of liquidity into tech capital markets. And the jury is still out on AI, very much at the top of a hype cycle, CEOs and boards have prematurely declared to their customers and the world that AI is working (because saying that makes their stock price go up) but the enterprise outcomes don't seem to be there.
My advice to your daughter: to try to make software into a fun hobby, watch a ton of coding youtube, AI and youtube are tearing down hurdles to learning, make a twitter, talk about your hobby, farm those likes. What were her favorite courses at MIT? it's true that software is increasingly competitive and yet the barriers to becoming competitive are ever lower (FOR those in a supportive environment who can make space to take advantage)
reply