10
onkarj
82d

Being a front end developer and working in a team of motivated "full stack" developers sucks big time.
So, recently joined this new company with a very small project which just started, basically a cloud version of a really old desktop app. Few people from the team completely from the asp dotnet background decided the architecture few months before I joined in.
So, they did it something like this -

- mono repo dotnet project with VueJs app served within it (because that would be maintainable πŸ˜‘)
- vue app served by pointing the built files through dotnet index file (simply because they didn't care about the gift to the front end world which is webpack or even had any knowledge about it πŸ˜‘)
- added typescript because, u know it's cool πŸ˜‘, without even knowing that they don't possess that team which know how to write the types (f***ers write classes for every payload object coz they don't know what interfaces are)
- no loader to load typescript, they are running tsc in watch mode and we have .js and .js.map for every .ts file in our project which some teammates are even pushing to repo

Recently, I added eslint with git hooks to the project so that everyone will at least stick to the coding standards. Now, to avoid the errors they are bypassing the git hooks by uninstalling the library and then installing it after the commitπŸ˜‚πŸ˜‚
Then we have a girl who uses document.getElementById to programmatically change styles in a Vue projectπŸ˜‘πŸ˜‘πŸ˜‘πŸ˜‚
Then we have dotnet people using dotnet coding conventions all over the front end app.

People, how do I deal with these so called "full stack" people?

Comments
  • 4
    Do your work then troll the fuck out of them, come back here and post high quality rants
  • 3
    @molaram high quality rants? what is that?!
  • 0
    @onkarj dunno it just came out that way
  • 2
    Seems like they're full stack dotnet corporate drones. Good dotnet devs are becoming harder and harder to find.

    Given that you're in Pune though, I'm surprised they can write hello world.
  • 2
    > I added eslint with git hooks to the project so that everyone will at least stick to the coding standards

    I like how you're not afraid of improving the current situation. Keep going! Though this might have been the wrong approach here, because:

    > Now, to avoid the errors they are bypassing the git hooks by uninstalling the library and then installing it after the commit

    I've seen similar things. That's a life lesson: You can't solve "people problems" by throwing technology at them. And furthermore, you can't force people to do "the right thing".

    They'll only stop making a mess when they understand they're making a mess and they agree on a better way. Otherwise they'll find excuses and workarounds, just like this one.
  • 2
    I've done a project with exactly the same setup as front-ender with an excellent dotnet developer and it absolutely rocked!

    2 observations about Java & .NET devs working with JS (w/o judgment):
    - they feel vulnerable without types
    - they always use classes

    monorepo & direct DOM access are not bad practice per se though (eg valid use case: changing the html element's lang attribute)
  • 2
    @webketje
    Just to level, I'm a ".net" developer. Most of my javascript is purely functional.

    I do like types though. Mainly because I like my applications to be mathematically provable.
  • 1
    @SortOfTested weeell maybe I did overgeneralize based on anecdotal evidence or maybe you're the exception :)
  • 2
    @webketje
    I am the exception, most .net humans want to render everything on the server πŸ˜‹
  • 1
    @SortOfTested don't know about .net developers, but yea Pune surely has got decent web developers and data engineers is what I can tell u!
  • 1
    @webketje how can you say that this architecture absolutely rocked??! I can't use hot reloading here!? I don't have my front end server running. And over the top, my vue is running through an index.cshtml which means vue does not have any control over its own index!
    And about typescript, it's surely an overkill here! Because, in the fast sprints nobody has got time to write those types! Otherwise typing the whole project as u go on developing is a different project in itself πŸ˜‚πŸ˜‚
  • 2
    @onkarj
    I'll have to take your word on it. I've worked with thousands of people from Pune from Infy, wipro, IBM, etc. They're giving you a seriously bad name.
  • 0
    @SortOfTested people from infy, ibm, wipro are not the devs I ll ever count onπŸ˜‚. Those are the good students from good universities who somehow got placed in those giant companies through some mass employment opportunity and then trained to do something which they never felt interest in.
    In India, mostly back benchers and dropouts make good devsπŸ˜‰
  • 0
    @onkarj the project I was talking about did use webpack with live rebuild but no auto browser-reload (I'm fine with hitting F5). It did use cshtml too with an <app> root, so you have all control you need there and Typescript wasn't used to the extent of what you'd find in popular node packages. Anyhow the point of my comment was that if you have awesome colleagues the tech doesn't matter that much ;)
Add Comment