wow, impressive. Colors could be better, but overall, it's pretty informative and cool.
HN user
veucast
Do you turn coffee into code, and eat bugs for breakfast? Do you enjoy building great products, from scratch, that users love? Do startups excite you? Are you passionate about building the next big global tech company that brings the world closer together? And...can you move fast, ship features on a weekly basis, love challenges, dream in code, and pride yourself at being the best at what you do? If yes...the Aeone (a Seattle-based software startup) is hiring 3 roles, to work on our SaaS business management tool for the creator economy.
Senior Software Engineer (full stack): https://www.veucastapp.com/careers#full-stack-engineer
Software Engineer II (full stack): https://www.veucastapp.com/careers#full-stack-engineer
Machine Learning Engineer II (full stack): https://www.veucastapp.com/careers/#machine-learning-enginee...
It's interesting to see someone putting a positive spin to technical debt. The level of technical debt you can afford taking on (technical risk) is heavily dependent on how you define technical debt at your company. You must understand how taking on a technical risk will have an impact in the current and future operation of the entire business/product/team. Not all technical debts are created equal, so to encourage people to see it as a positive thing or risk worth taking, without giving them this disclaimer is irresponsible.
I just use chess.com I started in 4 months ago. But to be fair, I still think having a real person teach you is better.
This is an interesting debate. What are your thoughts?