12

My first rant for ages

I'm working on a new project at a new company. We ha e a bunch of front end clients talking to an api.

I suggested that the api only communicate in terms of view models in order to bring some kind of standardisation to the project since at the time the gets and posts were either dB entities, view models, or just whatever the dev at the time decided.

I got a no, but that we could do posts and gets just with database entities. OK better than nothing..

I'm the front end angular app I implemented a generic form component and a generic data table component. The models given to these to build the components need to implement a view model interface.

Now we have a problem of the api giving us not view models and the front end needing view models so I put together a way to handle this in the front end.

My colleague with 8 years experience asks for my help and I'm happy to oblige. It turns out a model should have multiple child models in the database but the database entity models don't reflect this and therefore there is no way to build the view models. The data just isn't there from the api... Still I show him what the front end model should look like and write all the front end code for him to handle that.

2 days later he asks for my help again. It's exactly the same problem. Instead of fixing the backend and setting up the one to many relationship he has ignore the problem, retrieved a one to one relationship model and is just trying to force it to work - even though the data isn't there. He has also commented or removed all the code I helped him write and overwritten a file of typescript models that get autogenerated for us to be in sync with the backend...

I actually felt bad afterwards but I got frustrated as hell and he could tell...

Comments
Your Job Suck?
Get a Better Job
Add Comment