3 ms·
Not alone in the least. I'll give both the pros and cons of this to my eyes. pro: I keep my side project work _aggressively simple._ I want tech stacks that
by existencebox 8y ago
Not alone in the least. I'll give both the pros and cons of this to my eyes.
pro: I keep my side project work _aggressively simple._ I want tech stacks that don't have complex/hard to maintain build systems, dev environments, or toolchains. I want to be able to spin up a new dev env in a matter of minutes and without needing to remember what nonsense I put together and at what versions and etc etc. My goal in my side work is to get right to the point of Building Things with minimal overhead; and it's a constant balance of avoiding adding additional complexity without being too resistant to new tools/techniques.
Con: "I miss typescript." I use it at work, and I find it makes coding in JS _significantly_ more effective and less error prone. I think for my next big project I'd definitely utilize it. (This is actually the only really glaring thing I find myself wanting for, even on old-style angular there aren't "significant friction points" enough to motivate me to upgrade yet.)
- oneweekwonder 8y ago> I want tech stacks that don't have complex/hard to maintain build systems, dev environments, or toolchains. I need to confess it is 90% of the fun. > Con: "I miss typescript." I use it at work, I like the idea of typescript, but I'm adamant on no transpiling.