I have now decided to use the following Stack for web developement.

Backend
- Kotlin with Ktor.io as REST application
- RethinkDB

Frontend
- NuxtJS Universal Application
- Typescript
- Buefy (Bulma for Vue)

What do you think ?

I feel I need to write some side project summary somewhere.

So here it is about 3 months later:

- deleted 90% of code I created during last 3 months
- rewrote backed 5 times
- 200 lines POC still waiting to put in any meaningful architecture on frontend
- frontend part after aurelia, next, gatsby, react I think it would be vue powered by nuxtjs
- forced myself to buy food for whole week and don’t go out (except go running ) before I finish at least what I wrote on whiteboard

Now some positive news:

- there is not much left to be fucked up, removed or unnecessary added
- I think I got a plan
- this is probably first side project that makes me happy for such long time
- there is some probability it would help people and this is what I want to do in my life

Most important is that I know it would take at least half a year to do basic version of it and I don’t care.

Wish me luck so I can put some sneak peak after next 3 months.

Important thing I learned is not to listen to devs who suggest to learn a framework because its pointless

If i ask should i learn react or angular, some will say angular some react, and both have valid arguments why

When i branch to react and ask if i should learn nextjs or nuxtjs the same thing will happen

No matter if the arguments are valid or not people will prefer a framework they have been biased towards

All frameworks have cons and pros there is no such thing as "the one" perfect framework

No matter how framework is good people will always find a reason to take a shit on it

So from now i wont ask IF i should learn framework X, I'll ask for the order in which to learn it

For example i Know i want to learn A for whatever reason, should i first learn framework B or C?

I dont need your subjective opinion to tell me how B or C sucks and i should do D instead of A

How I wish my job interviews would end like this:

HR: "So, we're looking for a developer with experience in Nuxt.js. Can you tell us about your experience with that framework?"

Developer: "Honestly, I'm not very familiar with Nuxt.js. But I have a lot of experience with Vue.js, which Nuxt.js is built on top of."

HR: "Oh, well that's just fantastic. So you're telling me that we're supposed to hire someone who doesn't know the most important part of our stack? How hilarious!"

Developer: "Look, I understand that Nuxt.js is important to your team. But I'm a quick learner, and I'm confident that I can pick it up quickly."

HR: "Oh, I'm sure you are. I mean, it's not like Nuxt.js is a completely different framework or anything. You can just magically learn it overnight, right?"

Developer: "I never said it would be easy, but I'm willing to put in the work to learn it. My experience with Vue.js and JavaScript is still valuable, and I think I could make a positive contribution to your team."

HR: "Oh, I'm sure you could. I mean, it's not like there's a million other developers out there who already know Nuxt.js. We might as well just hire someone who doesn't know anything and hope for the best, right?"

Developer: "Okay, that's enough. I get it, you're not interested in my skills. But maybe you should consider the fact that your job description didn't even mention Nuxt.js as a requirement. If it was so important, you should have made that clear from the beginning."

HR: "Oh, don't get angry. We're just trying to find the best candidate for the job. And clearly, that's not you."

Developer: "Fine. I don't need this kind of attitude from someone who doesn't even know the difference between Vue.js and Nuxt.js. Good luck finding someone who meets your impossible standards."

HR: "Yeah, good luck to you too. I'm sure you'll find a job where you don't have to learn anything new or challenging."

Developer: "At least I'll be working with people who appreciate my skills and experience."

HR: "Sorry, what was that? I couldn't hear you over the sound of your arrogance."

Developer: "You know what? I don't need this. I'm out of here."

HR: "Wait, wait, wait. Don't be like that. We were just having a little bit of fun. You know, trying to lighten the mood."

Developer: "I don't think it's funny to belittle someone for not knowing everything. And I don't appreciate being treated like I'm not good enough just because I haven't used Nuxt.js before."

HR: "Okay, okay. You're right. We shouldn't have been so hard on you. But the truth is, we really do need someone who knows Nuxt.js. We can't afford to waste time on training someone who doesn't know the technology."

Developer: "I understand that, but I'm willing to learn. And I think my experience with Vue.js and JavaScript could still be valuable to your team."

HR: "You know what? You're right. We've been looking for someone with Nuxt.js experience for so long that we forgot to consider other skills and experience. We'd like to offer you the job."

Developer: "Really? Are you serious?"

HR: "Yes, really. We think you'd be a great fit for our team, and we're willing to provide you with the training you need to get up to speed on Nuxt.js. So, what do you say? Are you interested?"

Developer: "Yes, I'm definitely interested. Thank you for giving me a chance."

HR: "No problem. We're excited to have you on board. Welcome to the team!"

I'm creating getPocket alternative - using Golang, Nuxtjs and psql.

Doing a presentation about nuxt.js tomorrow. Any pointers ideas about stuff I should mention (excluding the obvious ones)

Today, I started meddling with nuxtjs, quite fun...any nuxtjs meddlers out here?

Any recommendations and tips for monorepo setups to share stuff between multiple typescript nuxtjs projects for the frontend and some nestjs backend ones? And all applications are deployed in docker containers.

I feel like I'm going crazy, everything I try is broken, or not fully implemented, or has a shitton of gotchas and customization that must be done on a case by case basis.

This is the most unfun shit I've done in a while.