Originally posted by superted
View Post
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Project is a poisoned chalice - when to walk away?"
Collapse
-
As others have said, do not call anything out as a mess. It just isn't worth it. How do you think it'll go down?
"Thanks for telling us that this product we've sunk a tulip load of money into is bollocks. Here's an extension" .
You can either stay on board and LOOK like you're adding value, or go.
On my last contract the back end was a right royal mess, and they employed 3 well paid perm dbas. It was clear as day that their section was a mess, was slowing development down, and was causing production issues, but there would have been no benefit to me calling then out. Just build relationships with people and do what you can. The good thing about working in a tulip code base is that you can't make it much worse.
Leave a comment:
-
Originally posted by Freaki Li Cuatre View PostAt what point do you take it upon yourself to go to the management and tell them what a pile of cack their application is & that it has no chance of succeeding unless they allow us to step back and do a serious bit of redesign of what we already have - especially the data layer? I would be pointing fingers here - and i feel a little bad about it - but I'm working weekends & long days & have had enough of the crap other people are checking in screwing everything up and making us all look like chumps.
Or do I just walk?
Once that's done - reevaluate! If you're happy with the direction things are going, fine. If not - decide if you're going to do it just for the money or the mental pain of staying in that mess is too big. But, especially in the latter option, long days and weekends can be spent at work if are paid generously.
Leave a comment:
-
Originally posted by Freaki Li Cuatre View PostDid you used to work here?
Handing IQueryable stuff back to a business layer is bad enough IMO but to the controller?
They'd obviously tried copying some repository/unit of work pattern example from Google but got its implementation totally wrong. So, wherever you want to save something you get a call to repository.SaveEntity(), or whatever, which is immediately followed by a call to unitOfWork.Save() to persist it to the database. Then you have the lifetime management of all these repository & unitofwork instances. Some of them are passed around all over the place, some of them are injected. It's a nightmare.
Write a proper implementation of the unit of work pattern and show em how it should be done.
Leave a comment:
-
Originally posted by woohoo View PostI'm not minimising the pain but are things so bad they can't be fixed relatively easy - I'm not in your shoes but just wondering?
It's been a while since I've used EF, moved to using PetaPoco or Dapper a while back but can't you enforce referential integrity using EF?
Why is it so hard to fix the cascading delete issue?
What's so wrong with using the repository in the controller? Get the data, stuff it into a viewmodel and pass to the view, doesn't seem that bad. Though I tend to go through a service layer first.
I've not used angularJs but funnily enough was going to start looking into it.
Handing IQueryable stuff back to a business layer is bad enough IMO but to the controller?
They'd obviously tried copying some repository/unit of work pattern example from Google but got its implementation totally wrong. So, wherever you want to save something you get a call to repository.SaveEntity(), or whatever, which is immediately followed by a call to unitOfWork.Save() to persist it to the database. Then you have the lifetime management of all these repository & unitofwork instances. Some of them are passed around all over the place, some of them are injected. It's a nightmare.
Leave a comment:
-
Originally posted by woohoo View PostI'm not minimising the pain but are things so bad they can't be fixed relatively easy - I'm not in your shoes but just wondering?
It's been a while since I've used EF, moved to using PetaPoco or Dapper a while back but can't you enforce referential integrity using EF?
Why is it so hard to fix the cascading delete issue?
What's so wrong with using the repository in the controller? Get the data, stuff it into a viewmodel and pass to the view, doesn't seem that bad. Though I tend to go through a service layer first.
I've not used angularJs but funnily enough was going to start looking into it.
Leave a comment:
-
Originally posted by Freaki Li Cuatre View Post4 weeks into a project that has just gone live by the seat of its pants & it's falling over right left & centre. So they want us to fix everything, support and test it while developing more functionality.
I've only just got fully acquainted with the system in the mad panic to roll it out.
Basically, I've walked into a right royal Indian mess .
Code first EF implementation using independent associations resulting in a back end with no referential integrity, unpredictable cascading deletes going on and other such undesirable things. A poorly implemented unit of work pattern, probably copied from Code Project - with repository instances knocking around in the controller classes (this is MVC). Boolean flags everywere - it seems that every new bit of complexity added to the use case has resulted in the crowbar-ing in of these flags right left and centre & it's already a load of spaghetti with just the most basic functionality in place.
And don't get me started on the Javascript It uses angularJS - and I can see its strengths - but the validation for every single control is a separate function called something along the lines of shouldButtonBeDisabled() and there are hundreds of them. I could go on but it's too depressing...
I'm not a lead dev on this project - I'm the last one to join the team & the other 2 seem happy plodding away adding to this spaghetti. We're not really going anywhere - in fact every fix that is made just seems to break more things. Unless it's one of my fixes of course....
At what point do you take it upon yourself to go to the management and tell them what a pile of cack their application is & that it has no chance of succeeding unless they allow us to step back and do a serious bit of redesign of what we already have - especially the data layer? I would be pointing fingers here - and i feel a little bad about it - but I'm working weekends & long days & have had enough of the crap other people are checking in screwing everything up and making us all look like chumps.
Or do I just walk?
It's been a while since I've used EF, moved to using PetaPoco or Dapper a while back but can't you enforce referential integrity using EF?
Why is it so hard to fix the cascading delete issue?
What's so wrong with using the repository in the controller? Get the data, stuff it into a viewmodel and pass to the view, doesn't seem that bad. Though I tend to go through a service layer first.
I've not used angularJs but funnily enough was going to start looking into it.
Leave a comment:
-
Everything is negotiable but if they want me working when i should be drinking stella its going to cost them loads!!!!
Leave a comment:
-
My mantra is keep smiling keep invoicing. Oh and i don't do weekends or lates is another one
Leave a comment:
-
Originally posted by SueEllen View PostThere is one of you and more of them. Plus they have been working there longer.
I would find a new contract and walk leaving them in the tulip.
The contractor devs in question were fired. People further up the chain are under the impression that the new guys have rewritten everything but the reality is that they've been reusing a lot of the old cr@p.
Any further development on any new functionality built on such a flakey foundation is doomed to failure. This will involve me working late nights, weekends etc before I am sent packing.
I'd rather preempt all this right now. I'd walk - but its getting to that time of year & I've already had the summer off
Originally posted by FatLazyContractor View PostWhere's the Indian connection then? Bobs who "settled" and set up their Ltd Cos?
Leave a comment:
-
Originally posted by Freaki Li Cuatre View PostProject wasn't outsourced.
These boys were operating through their own Ltds
As opposed to using internal dev resources who are paid and judged on their ability to deliver.
Leave a comment:
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: