I'm not sure I'd recommend DrySchema or DryValidation.
I've had real problems upgrading client's projects built using DryValidation prior to v1 in the past.
They changed the syntax of the validations just enough to break stuff and completely removed features like shared predicates. The upgrade process was very poorly documented with suggestions to go read random blog posts.
I think the replacement for shared predicates was supported be macros but even that is marked as likely to be removed in v2.
Just looking through some of the Dry changelogs the work BREAKING still features far more than I'm happy with. I'd be much happier to use Sorbet or an RBS based typing solution than work with Dry again.
It might have advantages over ActiveModel but ActiveModel is far better supported.
The path to getting into these founder / c-suite roles is those founding engineer roles in which you can learn how to scale and operate these ventures.
The founding engineer role at 0.5% is not meant to be a role to retire on, but a stepping stone to those bigger roles.
Not really, it's better to just start your own startup instead, there is not much need to spend years as a founding engineer before becoming a founder, you might learn some skills but it's nothing you can't learn yourself, as evidenced by the people who are first time founders who did not previously work at a startup. If you get to some scale and get acquired (or even shut down), you can leverage that for future higher positions that a founding employee would not get you.
It just depends on if you have the background and talent to warrant that role. I think that is an exceptional case for someone to get funding and support to build a venture without any operating experience.
Most companies that YC and other VCs fund are by first-time founders, mostly those who have not been in other startups. Like the other commenter said, the path to being a founder is actually founding.
It seems common enough that early engineers are purged for "higher quality talent" from the big companies at some point. Most of the high quality engineers won't join early on because they don't work for startup equity. Once the business is established and salaries are higher those FANG engineers are happy to join.
The folks designing the compensation plan and explaining the plan to the potential employee. I can't speak to unethical cases in which things are misrepresented.
People pay money for productivity software/tools. Look at how many tiny ISVs are making fairly large amounts of money selling Git clients. I think 1Password has like 60 employees now. There are companies much larger than 1 person doing screen capture software and large companies selling remote desktop solutions.
"You may not use the Magento trademark or any other mark associated with the Magento offering from our company in your domain name or URL. (For example, "www.magentohosting.com" is not allowed)."
We basically run type checking on major hand-offs between modules using DrySchema/DryValidation, a gem that makes it easy to set that up.
Without doing this, the integrity of the codebase erodes with scale.