charlie0077
Joined 6 years ago
Joined 6 years ago
All the things you mentioned totally make sense. I do have a landing page. This is to quickly see the other people's thoughts and validate the idea.
Eventually it would be topic based and/or algorithm driven. But for now, it would be manual, it just takes time and effort to build everything. I am doing this for free and for fun.
I have not thought about the abuse issue, looks like a pretty big and valid concern.
If you feel bad about all the boilerplate code you need to write in server side. There are many node libs/blackbox services that can help you, such as prisma, hasura. You can also take a look at a lightweight library that makes your life easier when building GraphQL server: https://github.com/charlie0077/graphql-server-crud/
I am the author of that library.
2. don't worry about test. the most popular open source project(linux kernel) do not have test code. it is overrated. When you interview for a job, nobody will ask you how good you are in writing tests. If I were you, I would prefer no test code required, so that I can focus on learning more important stuffs to grow myself: design pattern, infrastructure consideration.
3. about ML: you don't need degree. if you can be top 10 in kaggle, nobody cares your degree. If you truly like ML, you probably don't care about the job. How do you learn ML: google, online courses, and the most important: projects. The best case is that you can work for a company that is willing to hire you as a software engineer but then they allow you to work on ML projects. But this is kind of luck and you have to do google search to find that type of company. But, getting a degree and naturally getting hired as a ML engineer would be safer plan if you have decided ML is what you like. But there is cost: time and money.