Live data from Hacker News

What the IBM Acquisition of StrongLoop Means for the Node.js Community

strongloop.com

81–90 of 136 posts

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#81
post #41

Earlier quoted context omitted.

I hope it works out for StrongLoop. When a company I worked for was purchased by IBM, about 3/4 of the engineering staff left once we heard about "Work Life Integration (tm)". It's really hard to work inside Big Blue when you are used to the freedom provided by a small company.

Huh. When Blekko got acquired by IBM Watson, all of the employees thought that IBM's policies about flexible working hours and locations were great. So far I'm the only techie who's departed.

But you were the CTO .. that likely said something to the remaining folks.

Also - Hi Greg!

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#83

Earlier quoted context omitted.

Care to elaborate on IBM "Work Life Integration (tm)" and why it caused the mass exodus?

A quick google search seems to indicate that IBM wanted to allow their employees more flexibility with their schedules and ability to take leaves. I don't understand how this is a bad thing.

The problem was their justification. It went something along the lines of "Employees are often thinking about their personal lives while at work, so they should also be thinking about their work life while at home."

I'm sure the intentions were good, but the presentation was terrible. Also, it was only one of many factors, but its a catchy line so I chose to call that one out.

Other include:

  * Far worse benefits package and no attempt/willingness to make us whole in that regard

  * About half the team was told they would no longer be eligible for raises because their salaries were above the top of their IBM pay band

  * Several people lost large amounts of 401k matching because they missed their partial vesting date for that year (some by a few weeks) because the transition was done as being fired and then hired again

  * Likewise we were not eligible to start contributing to the IBM 401k for some amount of time

  * The IP agreement was Draconian (and we aren't in a state with nice moonlighting laws)

  * They took away our office's coffee budget, which seems small and petty but it was a damned nice thing to have

  * Two of the worst performers were promoted to be engineering managers because they didn't know what else to do with them....
I was only there for a few months after the merger. Talking to some who lasted longer made me very happy to have left. In all about 3/4 of the engineering team was gone within 9 months.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#84
post #41

Earlier quoted context omitted.

I hope it works out for StrongLoop. When a company I worked for was purchased by IBM, about 3/4 of the engineering staff left once we heard about "Work Life Integration (tm)". It's really hard to work inside Big Blue when you are used to the freedom provided by a small company.

Huh. When Blekko got acquired by IBM Watson, all of the employees thought that IBM's policies about flexible working hours and locations were great. So far I'm the only techie who's departed.

We were in their software services vertical (I forget the name)...the one that had never turned a profit and wasn't sexy. I've known one person who had a great experience on the Watson team. So maybe its a different experience?

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#85
post #41

Earlier quoted context omitted.

I hope it works out for StrongLoop. When a company I worked for was purchased by IBM, about 3/4 of the engineering staff left once we heard about "Work Life Integration (tm)". It's really hard to work inside Big Blue when you are used to the freedom provided by a small company.

Huh. When Blekko got acquired by IBM Watson, all of the employees thought that IBM's policies about flexible working hours and locations were great. So far I'm the only techie who's departed.

[deleted]

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#86
post #70
post #56

Earlier quoted context omitted.

About your point about Lotus Notes: I interned at IBM 3 times, and was never forced to use Lotus Notes. No one whom I worked with at IBM used Lotus Notes either. We used either Open Office or MS Office. The most popular IBM software we used was SameTime for instance messaging and it was actually not bad at all.

You might be thinking about the Office-like companion to Notes, Symphony. AFAIK (going from some Name/Location/BU-looking email addresses) IBM still uses Lotus Notes for email. Lotus Notes is actually quite good when used properly and in moderation, but it really does not set a positive tone culturally.

Notes is _terrible_ from a UI perspective. The server side (domino) though was light-years ahead of anything in terms of ideas at least. Combining a CA, distributed, document-oriented database(think mongodb, couchdb), LDAP server, web server and mail server that supports IMAP, POP, SMTP as well as the proprietary encrypted notes protocol.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#87
What node.js needs is a better way to manage packages. Right now, upgrading can fail with no way to roll back. Also, reproducibility is missing. E.g, it is not easy to download sources, and deploy those exact same sources on different machines.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#88
post #87

What node.js needs is a better way to manage packages. Right now, upgrading can fail with no way to roll back. Also, reproducibility is missing. E.g, it is not easy to download sources, and deploy those exact same sources on different machines.

npm is now its own company, so I think there is hope that serious work is being done to fix those issues.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#89
post #83

Earlier quoted context omitted.

A quick google search seems to indicate that IBM wanted to allow their employees more flexibility with their schedules and ability to take leaves. I don't understand how this is a bad thing.

The problem was their justification. It went something along the lines of "Employees are often thinking about their personal lives while at work, so they should also be thinking about their work life while at home." I'm sure the intentions were good, but the presentation was terrible. Also, it was only one of many factors, but its a catchy line so I chose to call that one out. Other include: * Far worse benefits pack…

I find it strange that large companies envy the things smaller shops are able to do, and they'll spend the money to buy them up, but they won't spend the time to understand the culture that let them build what they built. Put employees first and you'll find they can do some pretty amazing things.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#90
post #17

> And it’s not just Node.js. Maybe you haven’t looked at what IBM is doing with open source lately. I was surprised when I dug in. For example, did you know they are leading contributors to: Linux OpenStack Cloud Foundry Docker plus many Apache projects like Spark, Cordova and Hadoop and of course, Node They are? (keyword => "leading") https://github.com/docker/docker/graphs/contributors https://github.com/apache/spa…

IBM are working on the runtimes for things like Node, Spark, Python, Docker, and augmenting them to perform well on IBM platforms and integrate with IBMs enterprise monitoring and diagnostic tools.

Some of these augmentations have been contributed back to the main projects.

Post reply on HN