5 ms·
I think to define what is "fun" I'd take the reverse approach: What's NOT a fun stack to work with? For me personal hell is a giant stack that I barely underst
by montenegrohugo 5y ago
I think to define what is "fun" I'd take the reverse approach: What's NOT a fun stack to work with?
For me personal hell is a giant stack that I barely understand, a stack that I'm very slow to iterate on, a stack that has 9999 exceptions and custom rules and "quirks" that I need to remember and work around. This is infuriating, and definitely not fun.
So then what's fun? For me it's something small, fast, something that's no hassle and that lets me put my ideas into practice. Something that makes sense, something that I can have a complete mental model in my head and modify it in practice as fast as I modify that model in my head.
For me, the closest thing is:
BACKEND:
- Python for the backend. Just a great, batteries included language that lets me do what I want fast and doesn't get in my way.
- Flask: a web framework for Python. There's Django too, but Django is no fun. Flask is small and exactly what I want.
- Pytorch: My DL framework of choice. Again, understandable, makes sense, and fastly iterable. No archaic nonsense (looking at you Tensorflow). Also of course pandas, numpy, scikit etc...
FRONTEND:
I'm not a frontend guy, but it's a necessity, so I go with the simplest.
- Bootstrap: Lots of templates, easy to understand. I'm not entirely happy with it though; I wanted to try Tailwind.css for my next project
- Simple, custom Javascript. No complex frameworks. I barely understand JS; I don't want to use a framework until I feel comfortable with bare JS.
DEPLOYMENT & OTHERS:
- Heroku: a bit expensive but so simple. Removes all the hassle. I don't think deployment is fun, so Heroku is my friend.
- Google Analytics: I don't want a lot of analytics, and GA just works. I do want to move to a more privacy friendly choice.
- Uptimerobot for detecting problems. Simple, works, free.
With this tech stack I feel really comfortable, I can iterate on all layers, and I really do have fun developing on it. I can shoot out an MVP for most projects in a week.
Here's a few things I've built/am building with this:
https://www.namy.ai https://www.namy.ai https://www.hugomontenegro.com https://www.hugomontenegro.com https://www.remindy.me https://www.remindy.me
My biggest gripe in this tech stack is bootstrap, but I think despite of that and me not being a frontend engineer I still managed to give the sites a bit of a non-generic flair.
P.S.: This got too long, but I got over excited with the topic :)
- CRConrad 5y agoKind of derailing the discussion looking from the specific context of web-dev stacks, but... > For me personal hell is a giant stack that I barely understand, a stack that I'm very slow to iterate on, a stack that has 9999 exceptions and custom rules and "quirks" that I need to remember and work around. This is infuriating, and definitely not fun. ...but hopefully putting it in a larger context: This is exactly what I find infuriating and not fun about every ETL/ELT tool I've ever used or seen, and which makes these my personal hell. At a guess, this is probably what infuriates developers in any specific area -- only, in most areas, there are at least some good tools to choose from. > So then what's fun? For me it's something small, fast, something that's no hassle and that lets me put my ideas into practice. Something that makes sense, something that I can have a complete mental model in my head and modify it in practice as fast as I modify that model in my head. This is why I'm thinking about building my own. I have some ideas already, but... Sigh.
- mraza007 5y agoOkay things you listed here is what I do when building web applications. Your comment gives me hope that people like me do exist I’m not the only one