4 ms·
I've spent 5 weeks working with our offshore sysadmins to get Python3 installed on a dev box. Its a 30 second job, does anyone in a startup have these problems?
by rb808 10y ago
I've spent 5 weeks working with our offshore sysadmins to get Python3 installed on a dev box. Its a 30 second job, does anyone in a startup have these problems? Big banks suck right now.
- vog 10y ago> Big banks suck right now. But the really sad thing is: Startups in the financial sector suck even more. Mt. Gox is just one of the many screw-ups there.
- CoolGuySteve 10y agoHere was my experience at GS, I didn't last too long: - I was never able to get email search in outlook enabled on my computer. It was a "security risk". - Every Monday, my Visual Studio install broke and I'd have to call support in Bangalore to reinstall it. - Our "make" system's subtasks would segfault every 1/3 times so I always ran it 3 times, sometimes 4. - The only way to commit code (after using an out of date CVS) was to use this second in-house utility manually on every commit revision on every file. The asshole who wrote that thing made MD. - Our 32bit system would run out of memory and take hours to compile because Java talked to C# talked to C++ talked to Slang talked to javascript all in the same address space.
- onion2k 10y agoIts a 30 second job, does anyone in a startup have these problems? I did some work for a startup that required me to integrate with an external API. The API had a bug that the service provider didn't fix despite many requests over a period of about 6 months. We had to switch to a different provider and reimplement a lot of code using a their API instead. So, yes.
- tonyedgecombe 10y agoWhen I was contracting it would take some customers weeks just to get me a user account, I'd just sit there twiddling my thumbs and billing them.
- squeaky-clean 10y agoI'm at a startup that works with big enterprisey customers, maybe 50% of the time I have a ton of freedom and "agility", and the other half of the time it's like what you describe. Just insanely frustrating and painful. And because our customers know us as being agile, there's a huge double standard to all of it. We can request changes, or even write all the code for them and send it, but won't see it live for 3-12 months. Even for critical bugs. However, when they request anything for our services, features require like a 1 month deadline from conception to deployment, and critical bugs is something like 72 hours. A little ranty because 2016 for me was more like 90% "dealing with enterprise", 10% freedom. Thankfully next month I'm being switched to a team dealing more with internal services, so there's a lot less BS (because my boss says he's noticed how stressed it has made me, so that's nice).