4 ms·

Typical consultant mindset. They cant fathom how big IT got into the situation they are in due to legacy software, mergers, and periods of no investment. They o

by wil421 4y ago

Typical consultant mindset. They cant fathom how big IT got into the situation they are in due to legacy software, mergers, and periods of no investment. They only do greenfield projects and have complete disregard for IT’s processes. What’s funny is the big consultancies are usually to blame for stupid IT or they make bean counter decisions to not invest in IT. Thus the reason we need chop shops to come in and and help. Oh, and god forbid we add an FTE with domain experience who can help us.

mgkimsal 4y ago
I didn’t sense all of that from the comment, but you’re definitely anti-consultant. Sometimes consultants are brought in specifically to bypass whatever internal processes are in place. Those internal processes are sometimes the very reason not enough is getting done and external resources are brought in.
- mynameisvlad 4y ago
  I would say that GP comment definitely has a “normal teams are useless until consultants come in” view, which the parent comment also seemed to pick up on. Specifically, this part bugged me: > They would call us in when their devs couldn’t/wouldn’t do the work. We were pretty expensive by comparison, but at least we got the job done. This makes it seem like the developers just didn’t want to do the work or it was harder than their skill level, which, realistically, isn’t the case. FWIW I agree that consultants have their place, especially as a way to work outside of the typical system, but I’m not about to ignore that GP practically made it sound like consultants are better than regular developers.
  - mry2048 4y ago
munchler 4y ago
Wow. We were a small, private company. I’m sorry for whatever hurt you.
triggercut 4y ago
As someone who works in big consulting I understand the frustration but have to disagree. A lot of the time we have great people doing great work but we can only take it so far. Clients have to both be willing (want to) and able (have people with the appropriate skills required) to change. If we aren't guiding implementation and leave it to the client often times it will just fall in a heap, out be forgotten about

by wil421 4y ago

mgkimsal 4y ago

I didn’t sense all of that from the comment, but you’re definitely anti-consultant. Sometimes consultants are brought in specifically to bypass whatever internal processes are in place. Those internal processes are sometimes the very reason not enough is getting done and external resources are brought in.

mynameisvlad 4y ago
I would say that GP comment definitely has a “normal teams are useless until consultants come in” view, which the parent comment also seemed to pick up on. Specifically, this part bugged me: > They would call us in when their devs couldn’t/wouldn’t do the work. We were pretty expensive by comparison, but at least we got the job done. This makes it seem like the developers just didn’t want to do the work or it was harder than their skill level, which, realistically, isn’t the case. FWIW I agree that consultants have their place, especially as a way to work outside of the typical system, but I’m not about to ignore that GP practically made it sound like consultants are better than regular developers.
- mry2048 4y ago

munchler 4y ago

Wow. We were a small, private company. I’m sorry for whatever hurt you.

triggercut 4y ago

As someone who works in big consulting I understand the frustration but have to disagree. A lot of the time we have great people doing great work but we can only take it so far. Clients have to both be willing (want to) and able (have people with the appropriate skills required) to change. If we aren't guiding implementation and leave it to the client often times it will just fall in a heap, out be forgotten about