[ploggingdev]

> Currently working on toy projects to sharpen my web development skills

Could you talk about what those projects are about and what languages/frameworks you are using?

What's next? Are you looking to start another business or taking some time to just learn and work on projects that you find interesting?

Just wanted to say that I really enjoyed reading your blog posts and forum posts on IH. Good luck!

[mtlynch]

>Could you talk about what those projects are about and what languages/frameworks you are using?

Sure, I'm working with Angular now. I might switch to Vue.js because I'm not crazy about Angular and I've heard very good things about Vue, but I'm also wondering if I'd like Angular more once I reached proficiency in it.

>What's next? Are you looking to start another business or taking some time to just learn and work on projects that you find interesting?

The project I want to get back to is a keto recipe search engine (https://ketohub.io/). I put it on hold for other projects, but I have more ideas for it and it's a good project for me to stretch my web development skills.

I may also consider projects targeting customers in Western Mass that nobody else is really going after. When I tell people here I'm a developer, many tell me that the software they're forced to use at work is terrible and old but there's no replacement, so maybe I'll find one I can tackle.

>Just wanted to say that I really enjoyed reading your blog posts and forum posts on IH. Good luck!

Thanks!

[rhymenoceros]

> Sure, I'm working with Angular now. I might switch to Vue.js because I'm not crazy about Angular and I've heard very good things about Vue, but I'm also wondering if I'd like Angular more once I reached proficiency in it.

I am probably preaching to the choir here, but if you are looking to sharpen your skills, it's almost always better to stick with a single tech and learn it really, really well. That doesn't mean it's harmful to step through some Vue tutorials to get a feel for how it is different, however, if you're not careful you can end up losing a ton of time learning about the JS framework du jour and not actually making progress on anything. Especially if you are not in any hurry to build something useful.

Just about the only constant in JS frameworks is that any decision you make now on which one to use will probably be wrong in a year.

That's not to say optimizing for development speed isn't a good thing, especially if you are looking to bang out POCs as quickly as possible to vet startup ideas. But if you're not careful this can devolve into "funtime with tech" that could be a major distraction which might not even look or feel like one.

Speaking from experience :-)