Events/meetups are either paid or recurring at a per month or above frequency. These are not enough to develop the same camaraderie you’d with a coworker that sits next to you.
In any type of coworking space, anecdotally, people rarely ever ask others about work BUT if somehow (charger, wifi password etc) conversation initiates, people enjoy talking about it. This is unfortunately rare and you will never really see the same person again.
The app does these things (at least) - It lets you meet other remote workers publicly in a work setting and gives you an opportunity to connect professionally (or personally) over and over - Three people max makes it much more intimate than meetups where conversations usually center around people that are very expressive.
Only in Bangalore for now and completely free!
Remote: Yes
Willing to relocate: No
Technologies: Go, Node.js, JavaScript, TypeScript, Python, React, AWS, Postgres, Mongo, Kafka
Résumé/CV: https://achie27.github.io/resume/
Email: [email protected]
- Backend-leaning full-stack SWE with 3+ years of industry experience
- Built applications in fintech, defi, real-estate, and advertising
- Relevant profiles along with resume here - https://achie27.github.io
- Toptal profile - https://www.toptal.com/resume/archit-mathurRemote: Yes
Willing to relocate: Yes
Technologies: Node.js, JavaScript, TypeScript, Go, Python, React, AWS, Postgres, Mongo, Kafka
Résumé/CV: https://achie27.github.io/resume/
Email: [email protected]
- Backend-leaning full-stack SWE with 3+ years of industry experience
- Built applications in fintech, defi, real-estate, and advertising
- Relevant profiles along with resume here - https://achie27.github.io - Backend-leaning full-stack SWE with 3+ years of industry experience
- Worked with Node.js (JS and TS), Go, Python, React, AWS, Postgres, Mongo, and Kafka
- Built applications in fintech, defi, real-estate, and advertising
- Relevant profiles along with resume here - https://achie27.github.ioI am fairly new at a startup, and as such know little about business logic, and a lot of times I tend to misanalyze the scope (as in the files and/or repos that will be changed) of a new feature when starting to code.What steps do you guys take to ensure that whatever you have thought up is largely correct when you don't have proper specs?
I work in a startup that is in the scaling-up zone and every now and then there's some adhoc feature request or unforeseen circumstance that forces me to tweak my codebase in a way I don't want to - like putting a 'temporary' hotfix and just injecting a new logic without creating a separate/proper pipeline for it. There is no systematic testing flow or code coverage either. Its almost too sad...
Something that would not intervene while coding but still engrossing enough to be interesting.
Remote: No
Willing to relocate: Yes
Technologies: Python, C++, JavaScript, HTML/CSS, Express.js, React.js, MySQL, MongoDB, Pytorch, OpenCV, PyQt5, Scikit-learn
Résumé/CV: https://achie27.github.io/resume
Email: architmathur2011[ at ]gmail.com
- CS senior with 3 internships
- Github - https://github.com/achie27
- Projects based on web dev, ML, CV, GPU programming