It’s definitely not all. My current team definitely has respect for all that special tooling / ux stuff I’m doing. Especially since nobody was able to do it before I was hired.
But I also had the experience that older Backend devs don’t take it seriously. My guess would that those stoped learning about frontend tech in the late 90s and it’s a case of not knowing what you don’t know.
It’s true it happens for other areas too. But I think it might be true that frontend is often viewed as “the easy” part by other devs. Especially older backend devs seem to think it’s all super easy. At least in my experience.
And that businesses try to push for all devs be full stack doesn’t help.
But who decides that? If the person who requested it can do this, you only need a friend to abuse the system and give each other a few extra points.
Maybe a open point history could help with this and users moderate themselves with this.
Yeah that’s definitely a possibility. It’s really a tricky topic to build a review community. One could try other approaches like dedicated volunteer reviewers. But if you look at exorcism, that will become hard to manage for languages with huge demand.
A system where everyone also needs to review is definitely better. Especially since everyone also learns reading other peoples code.
True, it’s not a fleshed out idea haha. But starting with a few points would work.
Could actually be a cool in it self, wish I had time for something like that.
deleted by creator
Would love something like this, but it’s very hard to get such a community working. Most of the time there will be way more people wanting a review of their code than people wanting to put in the work and review something.
Maybe some kind of point system could work. Like one needs to review at least two times before you can get your work reviewed.
Can’t recommend Vue 3 enough. It’s so much fun to work with, the ecosystem is also caught up after the slow transition. The official docs are very good.
As for the backend try out go-lang or the newer java frameworks.
Thanks for your answer.
It’s a 30 year old swiss army knife, and it shows.
There is a lot of improvementsn happening in the Java space , so that might change over the next years.
It’s better by every metric and it’s a lot easier to manage your infrastructure (just a single binary file with no file or environmental dependencies; it doesn’t get any more straightforward than that.)
With these new native builds you also get a single binary file as far as I know ( I’m still kinda new to Java) and much better startup times. So today Java might perform a little better in this comparison.
But I take it as a good chance for getting a chance to introduce go as a language.
Mostly intellij ultimate, and sometimes VSCode as jetbrains Vue Support is not as good as the official plugin for VSCode.
It’s really weird they don’t want to show type errors inside the template, but whatever.
Other than that, I try to integrate AI assistants into my workflow. Currently trying out Cody, which works good so far, but I think without the sourcegraph integration it can’t show it’s full potential. But 50k$ seems a little expensive for my company haha
Probably typescript, it makes me rather productive and nowadays you can use it for pretty much anything. Even if it’s more often than not the optimal solution, it gets the job done
Other than that I’m interested in checking out go and rust, but unfortunately family life + trying to bootstrap isn’t giving me much time outside my day job to toy with those.
Curious about the tests you made with java and go. Did you test classic JVM or the new native builds?
We are currently using mainly java with some node sprinkled in there, but I try to move some thinks we have from K8 pods into lambdas as it doesn’t make sense having it running 24/7. One of my coworkers often looked for a reason /place to introduce go. So might be helpful info for him haha.
Does anyone know what they are doing with context data send to their system? Could only find that the saas version had some audit, but didn’t know that term.
It sounds interesting enough to try it in day to day work, but we can’t use most AI tools so far as it violates our company rules when we send parts of the code base as context.
Really need to speak to our lawyer again about this…