Bob Bass

I've been feeling the same way and it was almost too simple for me. First, strongly typed languages are objectively better for catching errors during development instead of during production so a small amount of work upfront pays huge dividends later. But the easy part is how actionable it is.

Find a codebase that you want to convert. For me, it was a server that I wanted to convert to Firebase cloud functions to go serverless. I took my server.js file and copied it as server.ts. I created a simple tsconfig.json file in the root with some standard settings online and then I let the VS Code IntelliSense guide the migration. It was so much easier than I expected and I learned TypeScript as I was converting my codebase.

It was almost too easy and now I have all of the benefits of feature-rich and built-in assistance in my code-editor. Documentation on hover, clear and clean errors. This was only about 2 weeks ago and I am not sure I'd ever go back to Vanilla JS now. It was love at first use with me.

I started out with C# and .NET and I loved it. In my opinion, it was the perfect way to start learning the fundamentals of software development however I always felt like I was at a disadvantage when I was doing .NET development. Granted, .NET Core is now open-source and cross-platform, but I moved to Node.js simply because it is incredibly popular. I never thought I'd learn to love JavaScript it the way I did with C#, but I learned to love it pretty quickly, especially once I started using TypeScript. You get all of the benefits of C# and JavaScript all in one. If you've built a REST API with Python/Flask/Django, you'll be able to learn Node.js/Express/TypeScript well enough to migrate your API very fast and it's incredibly easy to host for free on any number of services.

I'm new to Go, I've got very little experience but the 'feel' of Go, isn't like Python in my opinion. Go has a pretty steep learning curve, much steeper than C# in my opinion. So if you are willing to consider Node/Express/TypeScript, I think you may really like it. If you're picking between Go and C#, I'd go for C# as of today, but once I am more comfortable with Go (which I anticipate being a slow process) I may change my mind.

At this moment in time, in late 2020- Node/Express/TypeScript feels like the obvious choice to me as a former C# developer.

This is largely a matter of opinion. I see that someone else responded and recommended MongoDB but since you are doing data analytics, I highly recommend you go with SQL. You're going to have a really hard time normalizing the data when you can't manipulate relationships and bulk edit with a nice update query.

I'm much more experienced with MySQL than any other database and I am having a hard time getting on board with noSQL entirely because it's really hard to query complex data with relationships using noSQL. I'm using Firestore with one of my apps and MongoDB with another app but they both use MySQL for the heavy lifting and then a document database for things like permissions, caching, etc.

It sounds like the type of problem you need to reverse engineer. I'm sure you can imagine what the data sets would look like if you use MongoDB or Postgres. I suspect that putting in a little bit more work up front will pay high dividends and productivity once the data is normalized.

Again - it's largely a matter of preference but I prefer SQL almost every time.

Tray.io is expensive and only makes sense in a few rare occasions where you need 2-way constant data binding in a 'loop' where Zapier is more like an automation swiss army knife. Tray.io is aimed exclusively at enterprise while Zapier supports businesses of any size. Tray.io is very expensive and Zapier is much more reasonable especially early on before you have massive amounts of zaps.

You may also want to look at Integromat but Zapier would be my choice in this case. I almost don't see Tray.io as being something worth considering for your particular use case unless there's a massive scale behind your product that I'm unaware of (absurd amounts of tasks in the hundreds of thousands).

Zapier also has a great community and an "experts" program in the event that you want to outsource your automation.

I use Vuetify everyday and there's only one thing I truly don't like about it. It's really hard to have double nested values inside of data tables. sort of a specific complaint that most people will never have to deal with but other than that it's excellent.

I haven't personally tried ionic yet but I absolutely intend to the next time I have any mobile project. I remember hearing a lot of frustration around ionic early on but lately, I've heard nothing but good things and I'm excited to try it.

If you are considering Vuetify and you're on the fence, just know that I find it to be a pleasure to work with.