ooooak
Joined 14 years ago
Karma
216
Submissions
122
Member since
Mar 14
[email protected]
View on Hacker NewsRecent submissions
Comment · 4 years ago
i would say "3. Working in real projects at industry" when i was 19 i had the opportunity to build real world systems. Durning that year i delivered a full stack e-commerce using MVC pattern for a client. Someone who is just starting its a lots of hard work to deliver a MVC full stack app and i learned a great deal.
Later i joined a USA based startup really large project. This is where i learned how to manage large SaaS apps and how to manage complexity.
Since then i have been only building SaaS products and i love it. Currently i am leading the development of microservices based system based on GraphQL and everything is running k8. i have worked on every part of that system.
I think starting early helped me a lot :)
Comment · 4 years ago
no
Comment · 6 years ago
I keep a todo list in a text file and it worked really well. been doing it for last 4 years.
Comment · 6 years ago
I mostly have a list of todos in simple text file.
Comment · 6 years ago
1. learn .net core
2. doing youtube
3. push MVP into production
Comment · 6 years ago
> I basically want to get as far away from Node and React and CSS as possible. What's a good path out?
.net core or spring boot?
Comment · 6 years ago
Location: Punjab, India
Remote: Yes
Willing to relocate: No
Technologies: PHP, Laravel, Node, Express, React, Go, Clojure
Résumé/CV: ooooak.github.io/cv
Email: [email protected]Comment · 6 years ago
1. In India, there are only ~100 jobs for a Clojure developer. That includes people just throwing in Clojure just to hire Java/Scala developer.
2. The learning curve for the Clojure. Clojure is simple but it's not easy by any means.
3. JVM interop if you are not a java developer it adds in more learning time. Most of the Clojure libraries use java heavily. It's a good thing but it adds in an extra layer of learning java's ecosystem.
4. Error messages. Even after years of Clojure. I still find it hard.
5. Documentation. Most of the packages I use don't have dedicated websites or good documentation.
Even after all the issues. It's still worth the investment. I started working on a crawler for a freelance gig. we first built it using Golang. But due to its complexity and lots of bugs due to mutation. We ported it to Clojure and we are not looking back.
Comment · 6 years ago
> How to get good at designing big and complex applications?
Write small and simple programs.