1
We are thinking of creating an audit trail of everything that happens on entries. We want to know "who did what to which entry and when". It seems like the most intuitive way to do this is to create new tables to store such actions and this also means quite a significant amount of code changes need to be made.
Are there other ways to do audit trail? And what if we want to store the old data on top of the actions? It seems like creating tables to store historical data will take up a lot of space.
For those that took effort to answer those questions, 1. How did you find the experience? 2. Would you do the same for other job portals i.e. not limited to YC-companies? 3. What motivates you to fill in your profile diligently?
For YC companies that use WaaS to find candidates, 1. Is it really that good? 2. What incentivizes you to keep using it? Is it the features (if so, what features?)? Is it the pool of candidates? 3. Is it really better than other ways of finding candidates (e.g. TripleByte, Hired.com, etc)?
I'm not referring to administrative onboarding tasks such as setting up a Slack account, setting up an email, ensuring all terms and conditions are read and signed, etc. I'm referring to things like: - familiarising new engineers with the codebase, - doing their first coding assignment in the company, - the software architecture & design, - development workflow (e.g. if the team uses master-develop branch model or feature branches to commit straight to master), - and if there are internal tools, how do you onboard new engineers/analysts on how to use them?
Perhaps big companies like FAANG build their own tools to do this but I'm equally curious what smaller companies do. The company I'm at uses READMEs and wikis, which are basically data dump and a checklist of things the new engineers should complete. Are these really the best solution out there?
As for database usage, how do you monitor how much storage the account is using considering the data is spread across multiple tables?
Is there a tool that does all these?
I'm considering between building a landing page to collect emails and building an open-source project on Github to see its traction.
A landing page will take probably 1-2 days. Building a project will take a longer time - might take 3, 4 weeks to build something that is presentable - but I think it is easier for people to see how the product works and understand what it is trying to solve.
What do you think is a better approach?
On top of that, supposed I have talked to a few friends and they understand the pain point but are vague on whether they will pay for a solution, which approach (landing page or open-source project) should I use?