Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I generally don't mind answering angular questions, if that helps. Or any questions that don't fall under lmgtfy, really.
Root6692751dI hate the trend of objectifying devs, calling us “resources” and assigning arbitrary levels. It’s insulting.
- let’s put more level 3 resources here so we can get this shit done by the end of year
- ok, since this shit is cleared what’s for lunch ?
@Root I find it disturbing as well, but I can’t ask for much since I’m only a bit more than a year out of school on paper. The goal was to get someone more experienced than me with the whole stack, but somehow management decided that “Level 3” is enough of a description. Guess that’s why “levels” exist
@ekat Don’t worry just say what needs to be done and what is stack if they’re ok people you’re be fine otherwise no matter what you do it won’t work.
Learning stack if some work is already done and follows some decent code guidelines is not a big problem.
Problem is find right people who don’t complain and just do the shit.
@ekat take it slow are very good symptoms. What I could be worried is UI if it’s external application for clients and you don’t have guidelines or design screens. I suppose aws and typescript it’s fine. There is nothing new in cloud that wasn’t there before, it’s just renamed. Typescript looks more or less like java.
What they need to know is probably async/await / event listener or reactive programming concept and that’s it.
There are no threads so programming looks a little different.
Good luck !
Angular, definitely reactive paradigm. I get so very unhappy when I see someone commit code that bails out of the observable sequence and defers to async await. 😆
I couldn't really imagine writing Js of any kind without it, being you're stuck with non-lazy, non-monadic iterable processing.