Season 7 of the podcast is all about the first times of the web.
>Is an extra $10k per year worth learning a new org, a new skillset, a new set of expectations, a new set of coworkers, and a new boss?
For many engineers, the answer is: “No.”
Yes I could quit and get a ~20k raise by shopping my resume around, but I don't need the money. I have enough for a down payment on a house, I meet my expenses for the month with 1/2 of one paycheck, I can buy a new car on a credit card if I wanted to. More money would be _nice_, and I imagine I'd be singing a slightly different song if I had kids, but it's much less important than knowing the work that I do has meaning and an immediate impact on the world, and about as important as working with new/interesting technology. I imagine there are a lot of early career (26-30 year old) software engineers who are in a similar boat. If money was a motivator I'd be serially founding companies and striving to be The Next Big Thing. I'm just not. I'm happy being hire number 13, or 99, and working with people I like doing work I find value in.
Edited for spelling
IMO the same caveat applies to Clean Architecture: it is study material to architects, rather than something you can copy-paste into a new project. The reason it's dauting, IMO, is because there are some unnecessary concepts there that are unrelated to the "grand idea", and those small things might make sense for Bob Martin but might not make sense to you.
If you want to understand it, I really like this article. I think it explains very well the "grand idea" of architectural templates like Clean/Hexagonal/Onion... and links it to Gary Berhnardt's Imperative-shell-functional-core: https://danuker.go.ro/the-grand-unified-theory-of-software-a...
Of course I also recommend Imperative-shell-functional-core itself: https://www.destroyallsoftware.com/talks/boundaries
30 days so that I can have enough time to delete it. Trash & Spam is excluded, and every successful downloaded email is labeled to prevent it getting downloaded again in next run.
Originally 4 years ago when I started this script, it was timing out because of about 15 years of emails. I ran it for 6 minutes only, every hour. Now once it caught up, it needs only few seconds, and there are only like 5 to 20 emails caught in its daily net.