As others have said, every other request is a 504 at the moment.
But for the platform itself-- pretty cool that you have file separations and visual renderings, going beyond simple code execution. I like it. I tried build something similar on algodaily.com a while back, but found that my audience wasn't that interested in creating tutorials.
Some feedback:
1) I wasn't immediately sure there were multiple steps at first.
2) Execution time is a bit slow.
3) I was monitoring the network calls and saw no requests when code executed -- are you doing this in the client? Just a heads up that there's some security vulnerabilities to be aware of.
4) The UI could use some polishing. Maybe look for a color palette that blends colors together better.
I'm not as cynical as notretarded, but I do wonder how you'll eventually make money. It can't be cheap to manually edit 1,000+ resumes weekly, so it does make me wonder what the end goal is and what the paid services will look like. Maybe some AI/data play?
Your blueprint to good technical resumes is super useful though-- I run a technical interview course and mentor quite a number of software engineers, will definitely share out.
I used to use the ladders all the time when looking for jobs, so thanks for creating that service too.
Thanks so much sciencewolf! Cycnicism is OK - there have been a lot of crappy products in this space and devs are sick and tired of LinkedIn spam.
The plan is to become a trusted partner to engineers and technologists - helping to update their resume yearly, produce better resumes by having a deeper insight into their performance. That trust and that relationship will be super valuable and I'm sure we'll find the business model.
As mentioned in FAQs -- "In the future, we will offer additional upgraded services for purchase such as resume distribution, hosting, tracking, salary negotiation, vetted job opportunities, recruiter outreach and cover letter writing." -- but at this moment we don't really know.
The core product today is writing resumes and building that trust. I think if we do that very well, we'll have a lot of opportunities to make a successful business out of it. If we do that poorly, we'll have nothing.
Yea it's a good concern. Right now I only have very simple checks, like captcha, detecting similar messages and also protecting a single email account from getting multiple emails. Feel free to suggest any ideas you might have :)
Hard disagree. Building, shipping, and learning from my mistakes is the only I was able to actually apply anything I learned from books. IMO the best method is to do both - start building now, and read books relevant to whatever part of the journey you're stuck on or need help with.
Spoken like a true prodigy! Entrepreneurship is not a spectator sport. You have to participate and not cheer from side lines. You have to get onto the base plate and start swinging. The more you bat, the more you maximize your chance of hitting the ball and making that home run. You can keep reading books all day long(and there is no shortage of shovels these gold rush days) but unless you make something and put it out there you won’t learn. Launch and learn. This will be my deathbed advice to my son.
That's a good idea. what I've learnt was startup failures has lot in common, similarly success is not an anomaly, it should has its own pattern. Most mistakes are already someone else mistake, I believe that reading some books will help to avoid 80% of the mistakes. the acquired knowledge will store a mental model within me. otherwise I need a lot of luck.
> Having a problem to solve in front of us can make us tinker on it's available solution and that's where those tutorial come handy.
This is huge. Start with the problem and read/watch enough to gather a solution, rather than learn for the sake of learning. Reminds of me just-in-time advice vs. just-in-case advice.
Technical interview course that focuses on being accessible to beginners through visuals - https://algodaily.com - Imagine leetcode with a lot of hand holding.
