Advertisement
bitbytenybble110

Untitled

Jun 26th, 2014
229
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.69 KB | None | 0 0
  1. [Nybble] and [coworker] can weigh in on their own, but no, they’re not valid. Excuse the tone of this email, but this guy is a jerk.
  2.  
  3. His comments are reactionary. If it’s taking a significantly longer amount of time for work to get done, why don’t they let us know? Do they want to spend all day on arbitrary tasks?
  4.  
  5. Did they inform you that you were having network problems at that point in time? If they were doing it for free, wouldn’t they prefer to get it done faster? If they were charging you, do you want to be charged for 2 hours for something that should have taken 5 minutes? What servers? What time? When? Report the damn issue if it exists, not under questioning about their own issues.
  6.  
  7.  
  8. We have no problems with your network. You have no problems with your network. We only have problems within [ERP company]’s little environment. Every step along the way has been a nightmare with these idiots.
  9.  
  10. • Installation – They didn’t tell you that it was going to be using a terminal server and you’d need licensing and additional resources.
  11. • Installation – Their minimum specs were fucked out of the box. We had to rebuild a new server to increase RAM to 16+ Gb and migrate to a different version of Server OS.
  12. • Resource utilization – What in God’s name needs as much RAM as their two boxes? [Nybble] can speak to specifics, but you have more than 1GB of ram PER EMPLOYEE dedicated to the database server. Compare that with Microsoft recommendation of 30mb per Mailbox (of any damn size!)
  13. • Resource utilization – Progress is a 32-bit server. 32 bit applications can’t utilize more than 2GB (3-4GB with some garbage hackery you wouldn’t put in a release product.) What the hell is using the RAM? Windows overhead? How would you scale this to a larger company of 100 users? 128 GB of ram for a 32 bit application that can’t use it? Insane.
  14. • Email Sending – Chillkat years out of date. They did nothing to resolve the problem or investigate the issue. We debugged their logs, reached out to their vendors, and brought back actionable information.
  15. • Email Sending – They attempt to send an email and if it fails, it errors out instantly. The specification for SMTP calls for queuing of messages. They don’t follow the damn specifications email was built on.
  16. • Website – They sold a website they couldn’t build, they couldn’t fix, they couldn’t finish, they didn’t understand what level of support it was supposed to have, they said they don’t have a QA department, they said they only had a single dev to work on it at all (and he was hard to manage), he couldn’t tell me who was responsible for the UX design, he couldn’t tell us anything.
  17.  
  18. Above and beyond this is Larry Ward at the center of it. [Company CEO] can’t return a call in less than 3 days, can’t make it his business to schedule a time to talk (but he’s damn proud he left a voicemail), [Company CEO] can’t be bothered to hire a developer who can multitask, he can’t be bothered to document his API (which essentially makes it worthless.), he couldn’t answer a single question about who was in charge of really anything with the website, or who worked on anything more than a single developer.
  19.  
  20. Every step of the way, we’ve worked above and beyond to debug their product.
  21.  
  22. It’s a shit product and it’s a shit company. That is my professional opinion.
  23.  
  24. We go out of our way, every time there is a problem, to investigate what could be causing the problem and soak a lot of time into to ensure that Bay and you have clarity in what is happening and are assured that, at the very least, SOMEONE is attempting to better your situation. We shall continue to do just that.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement