pzk1

This is good, a real objective evaluation. I think most of the critics of HTMX stems from pure front-end devs who are not really concerned of the back-end side.

While HTMX is tailor made/simple, for those who needs to build full-stack, while also having the great experience of SPAs.

Granted, it will never be able to compete with powerful JS frameworks on an apple-to-apple comparison, but that's not what it's designed for, It's an upgrade of HTML, not JS.

Isn't NATO a military alliance while BRICS an economic one?

Not sure if this is an apple and orange comparison.

Netlify CMS?

When is GAE & Cloud SQL coming to Southeast region?

How does this compare with Directus CMS?

Well, it turns out my idea was too farfetched, and someone already did the groundwork. But I do have an action plan now, just stick to the basics which I did not do previously, for a number of reasons, namely: 1) being too overwhelmed and forgetting to merge, 2) forgetting to fix the PR which has been reviewed, 3) taking tasks which are way above my head and not designing things beforehand which makes the code subpar and introducing regressions, 4) not attacking problems as hard as I can which makes tasks longer, 5) not asking questions a lot sooner

I guess it all boils down to completing the tasks I was assigned, improving the quality of the code and then finishing on time.

Thanks for these actionable tips. Appreciate them. Yes I'm definitely not giving up yet.

This has crossed my mind. But I'm certain a short stint is not gonna be good in my resume, plus being a subpar performer at your previous company looks awful whatever the reason is. I'm just gonna try my best and if things still don't work out, I'll just be glad that at least I worked my heart out. Thanks anyway for your advice.

Yup been doing that already but planning to read up the codebase as much as i can for this last chance to prove myself.

I do want to stay here actually. But definitely a good point about not expecting them to give me any favours. Thanks!

Thanks. Excellent point on the "reading other dev's code even though it's not best practice". Yup you are definitely right, most of the regressions are because of manual testing. But the team are very comfortable making changes and doing things "on-the-fly" + manual testing here and there, but they get away with it by being talented coders in the first place, which is the point of this post anyway. We are doing PR regularly though.

Yup. One of things I am planning to do much much more. Sometimes feel a bit lost when couldn't even "start" to solve a particular problem.

Spot on i would say. I guess it's just due to "ego" or lazy to spend a few minutes understanding.