11

I fucking told them that yes, i can do frontend but im in no way expert, so dont expect much.

"Yeah, cool, use angular"

I was full of questions and tried to reason with them that angular is literally just an unnecessary load and would slow the development down (its a really simple site).

"No, use angular"

Ok fine whatever. So i built the site, it was ugly as fuck, half the functionality was hacked in with jquery because i have no idea how these fucked up frameworks work (or apparently dont work) when i realized that i get jackshit from the backend.

Turns out most of the json responses were totally disregarding the json standard, like {1: tag0},{2: tag1}, where a json arrat should have been used. The other half was xml. Yeah. Also of course they used spring so the backend took like 3 months where it could have been done in like 2 weeks.

Comments
  • 2
    (Ended up rewriting the whole thing in w3js)
  • 2
    ((I cant pick ONE coworker from them, so just imagine that the whole team is one person or something))
  • 0
    What I usually do is I have my method of fixing the problem figured out in my own spare time (if possible) then I do whatever they want me to do. If it works cool but if it don’t guess who has a soluuuttiioooonnnnnnn. Lol and they still shoot my projects done sometimes.... eh the way I see it. This will always happen lol
  • 1
    @oo92 same, i usually use spark instead
Add Comment